Oct 28 07:02:56 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8392" x-info="http://www.rsyslog.com"] start
Oct 28 07:02:56 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 28 07:02:56 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct 28 07:02:56 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct 28 07:02:56 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 28 07:02:56 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 28 07:02:56 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 28 07:02:56 node-1 kernel: [    0.000000] Linux version 3.13.0-100-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #147-Ubuntu SMP Tue Oct 18 16:48:51 UTC 2016 (Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39)
Oct 28 07:02:56 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=9086efc0-686a-4dc4-b540-a8a93f78106a nomdmonddf nomdmonisw
Oct 28 07:02:56 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct 28 07:02:56 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct 28 07:02:56 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct 28 07:02:56 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct 28 07:02:56 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 28 07:02:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 28 07:02:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 28 07:02:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 28 07:02:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct 28 07:02:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct 28 07:02:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct 28 07:02:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct 28 07:02:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct 28 07:02:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 28 07:02:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 28 07:02:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 28 07:02:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 28 07:02:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 28 07:02:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 28 07:02:56 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 28 07:02:56 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 28 07:02:56 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 28 07:02:56 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
Oct 28 07:02:56 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 28 07:02:56 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 28 07:02:56 node-1 kernel: [    0.000000] No AGP bridge found
Oct 28 07:02:56 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 28 07:02:56 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct 28 07:02:56 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 28 07:02:56 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct 28 07:02:56 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 28 07:02:56 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 28 07:02:56 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 28 07:02:56 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 28 07:02:56 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 28 07:02:56 node-1 kernel: [    0.000000]   2 disabled
Oct 28 07:02:56 node-1 kernel: [    0.000000]   3 disabled
Oct 28 07:02:56 node-1 kernel: [    0.000000]   4 disabled
Oct 28 07:02:56 node-1 kernel: [    0.000000]   5 disabled
Oct 28 07:02:56 node-1 kernel: [    0.000000]   6 disabled
Oct 28 07:02:56 node-1 kernel: [    0.000000]   7 disabled
Oct 28 07:02:56 node-1 kernel: [    0.000000]   8 disabled
Oct 28 07:02:56 node-1 kernel: [    0.000000]   9 disabled
Oct 28 07:02:56 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 28 07:02:56 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 28 07:02:56 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 28 07:02:56 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 28 07:02:56 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 28 07:02:56 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct 28 07:02:56 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 28 07:02:56 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 28 07:02:56 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 28 07:02:56 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 28 07:02:56 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 28 07:02:56 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 28 07:02:56 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 28 07:02:56 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 28 07:02:56 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 28 07:02:56 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct 28 07:02:56 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 28 07:02:56 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 28 07:02:56 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 28 07:02:56 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 28 07:02:56 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 28 07:02:56 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 28 07:02:56 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 28 07:02:56 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 28 07:02:56 node-1 kernel: [    0.000000] Zone ranges:
Oct 28 07:02:56 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] Movable zone start for each node
Oct 28 07:02:56 node-1 kernel: [    0.000000] Early memory node ranges
Oct 28 07:02:56 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct 28 07:02:56 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 28 07:02:56 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 28 07:02:56 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 28 07:02:56 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct 28 07:02:56 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct 28 07:02:56 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 28 07:02:56 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 28 07:02:56 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 28 07:02:56 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 28 07:02:56 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 28 07:02:56 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 28 07:02:56 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 28 07:02:56 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 28 07:02:56 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 28 07:02:56 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 28 07:02:56 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 28 07:02:56 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 28 07:02:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 28 07:02:56 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 28 07:02:56 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 28 07:02:56 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 28 07:02:56 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 28 07:02:56 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 28 07:02:56 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 
Oct 28 07:02:56 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct 28 07:02:56 node-1 kernel: [    0.000000] Policy zone: Normal
Oct 28 07:02:56 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=9086efc0-686a-4dc4-b540-a8a93f78106a nomdmonddf nomdmonisw
Oct 28 07:02:56 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 28 07:02:56 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 28 07:02:56 node-1 kernel: [    0.000000] Checking aperture...
Oct 28 07:02:56 node-1 kernel: [    0.000000] No AGP bridge found
Oct 28 07:02:56 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 28 07:02:56 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 28 07:02:56 node-1 kernel: [    0.000000] Memory: 32653320K/33280496K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627176K reserved)
Oct 28 07:02:56 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 28 07:02:56 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 28 07:02:56 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 28 07:02:56 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 28 07:02:56 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 28 07:02:56 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 28 07:02:56 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 28 07:02:56 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 28 07:02:56 node-1 kernel: [    0.000000] console [tty0] enabled
Oct 28 07:02:56 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 28 07:02:56 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 28 07:02:56 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 28 07:02:56 node-1 kernel: [    0.000000] hpet clockevent registered
Oct 28 07:02:56 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 28 07:02:56 node-1 kernel: [    0.004000] tsc: Detected 3491.901 MHz processor
Oct 28 07:02:56 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.80 BogoMIPS (lpj=13967604)
Oct 28 07:02:56 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Oct 28 07:02:56 node-1 kernel: [    0.000043] Security Framework initialized
Oct 28 07:02:56 node-1 kernel: [    0.000062] AppArmor: AppArmor initialized
Oct 28 07:02:56 node-1 kernel: [    0.000063] Yama: becoming mindful.
Oct 28 07:02:56 node-1 kernel: [    0.001473] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 28 07:02:56 node-1 kernel: [    0.006427] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 28 07:02:56 node-1 kernel: [    0.008356] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 28 07:02:56 node-1 kernel: [    0.008384] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 28 07:02:56 node-1 kernel: [    0.008662] Initializing cgroup subsys memory
Oct 28 07:02:56 node-1 kernel: [    0.008670] Initializing cgroup subsys devices
Oct 28 07:02:56 node-1 kernel: [    0.008672] Initializing cgroup subsys freezer
Oct 28 07:02:56 node-1 kernel: [    0.008673] Initializing cgroup subsys blkio
Oct 28 07:02:56 node-1 kernel: [    0.008675] Initializing cgroup subsys perf_event
Oct 28 07:02:56 node-1 kernel: [    0.008677] Initializing cgroup subsys hugetlb
Oct 28 07:02:56 node-1 kernel: [    0.008696] CPU: Physical Processor ID: 0
Oct 28 07:02:56 node-1 kernel: [    0.008697] CPU: Processor Core ID: 0
Oct 28 07:02:56 node-1 kernel: [    0.008701] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 28 07:02:56 node-1 kernel: [    0.008701] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 28 07:02:56 node-1 kernel: [    0.009395] mce: CPU supports 22 MCE banks
Oct 28 07:02:56 node-1 kernel: [    0.009422] CPU0: Thermal monitoring enabled (TM1)
Oct 28 07:02:56 node-1 kernel: [    0.009443] process: using mwait in idle threads
Oct 28 07:02:56 node-1 kernel: [    0.009446] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 28 07:02:56 node-1 kernel: [    0.009446] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 28 07:02:56 node-1 kernel: [    0.009446] tlb_flushall_shift: 6
Oct 28 07:02:56 node-1 kernel: [    0.009534] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 28 07:02:56 node-1 kernel: [    0.010256] ACPI: Core revision 20131115
Oct 28 07:02:56 node-1 kernel: [    0.023059] ACPI: All ACPI Tables successfully acquired
Oct 28 07:02:56 node-1 kernel: [    0.023220] ftrace: allocating 28622 entries in 112 pages
Oct 28 07:02:56 node-1 kernel: [    0.031985] dmar: Host address width 46
Oct 28 07:02:56 node-1 kernel: [    0.031987] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 28 07:02:56 node-1 kernel: [    0.031993] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 28 07:02:56 node-1 kernel: [    0.031995] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 28 07:02:56 node-1 kernel: [    0.031999] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 28 07:02:56 node-1 kernel: [    0.032001] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 28 07:02:56 node-1 kernel: [    0.032002] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 28 07:02:56 node-1 kernel: [    0.032003] dmar: ATSR flags: 0x0
Oct 28 07:02:56 node-1 kernel: [    0.032004] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 28 07:02:56 node-1 kernel: [    0.032005] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 28 07:02:56 node-1 kernel: [    0.032121] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 28 07:02:56 node-1 kernel: [    0.032122] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 28 07:02:56 node-1 kernel: [    0.032123] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 28 07:02:56 node-1 kernel: [    0.032124] HPET id 0 under DRHD base 0xc7ffc000
Oct 28 07:02:56 node-1 kernel: [    0.032125] Your BIOS is broken and requested that x2apic be disabled.
Oct 28 07:02:56 node-1 kernel: [    0.032125] This will slightly decrease performance.
Oct 28 07:02:56 node-1 kernel: [    0.032125] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 28 07:02:56 node-1 kernel: [    0.032557] Enabled IRQ remapping in xapic mode
Oct 28 07:02:56 node-1 kernel: [    0.032558] x2apic not enabled, IRQ remapping is in xapic mode
Oct 28 07:02:56 node-1 kernel: [    0.032562] Switched APIC routing to physical flat.
Oct 28 07:02:56 node-1 kernel: [    0.033181] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 28 07:02:56 node-1 kernel: [    0.072830] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 28 07:02:56 node-1 kernel: [    0.072836] TSC deadline timer enabled
Oct 28 07:02:56 node-1 kernel: [    0.072843] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 28 07:02:56 node-1 kernel: [    0.072849] ... version:                3
Oct 28 07:02:56 node-1 kernel: [    0.072850] ... bit width:              48
Oct 28 07:02:56 node-1 kernel: [    0.072851] ... generic registers:      4
Oct 28 07:02:56 node-1 kernel: [    0.072852] ... value mask:             0000ffffffffffff
Oct 28 07:02:56 node-1 kernel: [    0.072853] ... max period:             0000ffffffffffff
Oct 28 07:02:56 node-1 kernel: [    0.072854] ... fixed-purpose events:   3
Oct 28 07:02:56 node-1 kernel: [    0.072855] ... event mask:             000000070000000f
Oct 28 07:02:56 node-1 kernel: [    0.074252] x86: Booting SMP configuration:
Oct 28 07:02:56 node-1 kernel: [    0.088356] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 28 07:02:56 node-1 kernel: [    0.074254] .... node  #0, CPUs:        #1  #2  #3
Oct 28 07:02:56 node-1 kernel: [    0.116262] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 28 07:02:56 node-1 kernel: [    0.270100] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 28 07:02:56 node-1 kernel: [    0.325708] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 28 07:02:56 node-1 kernel: [    0.382560] x86: Booted up 2 nodes, 16 CPUs
Oct 28 07:02:56 node-1 kernel: [    0.382564] smpboot: Total of 16 processors activated (111752.54 BogoMIPS)
Oct 28 07:02:56 node-1 kernel: [    0.406843] devtmpfs: initialized
Oct 28 07:02:56 node-1 kernel: [    0.409308] EVM: security.selinux
Oct 28 07:02:56 node-1 kernel: [    0.409310] EVM: security.SMACK64
Oct 28 07:02:56 node-1 kernel: [    0.409311] EVM: security.ima
Oct 28 07:02:56 node-1 kernel: [    0.409312] EVM: security.capability
Oct 28 07:02:56 node-1 kernel: [    0.409362] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct 28 07:02:56 node-1 kernel: [    0.410020] pinctrl core: initialized pinctrl subsystem
Oct 28 07:02:56 node-1 kernel: [    0.410078] regulator-dummy: no parameters
Oct 28 07:02:56 node-1 kernel: [    0.410109] RTC time:  7:02:20, date: 10/28/16
Oct 28 07:02:56 node-1 kernel: [    0.410141] NET: Registered protocol family 16
Oct 28 07:02:56 node-1 kernel: [    0.410225] cpuidle: using governor ladder
Oct 28 07:02:56 node-1 kernel: [    0.410226] cpuidle: using governor menu
Oct 28 07:02:56 node-1 kernel: [    0.410260] ACPI: bus type PCI registered
Oct 28 07:02:56 node-1 kernel: [    0.410262] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 28 07:02:56 node-1 kernel: [    0.410306] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 28 07:02:56 node-1 kernel: [    0.410308] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 28 07:02:56 node-1 kernel: [    0.424050] PCI: Using configuration type 1 for base access
Oct 28 07:02:56 node-1 kernel: [    0.425035] bio: create slab <bio-0> at 0
Oct 28 07:02:56 node-1 kernel: [    0.425303] ACPI: Added _OSI(Module Device)
Oct 28 07:02:56 node-1 kernel: [    0.425305] ACPI: Added _OSI(Processor Device)
Oct 28 07:02:56 node-1 kernel: [    0.425306] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 28 07:02:56 node-1 kernel: [    0.425307] ACPI: Added _OSI(Processor Aggregator Device)
Oct 28 07:02:56 node-1 kernel: [    0.437960] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 28 07:02:56 node-1 kernel: [    0.448553] ACPI: Interpreter enabled
Oct 28 07:02:56 node-1 kernel: [    0.448559] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 28 07:02:56 node-1 kernel: [    0.448563] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 28 07:02:56 node-1 kernel: [    0.448565] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 28 07:02:56 node-1 kernel: [    0.448572] ACPI: (supports S0 S4 S5)
Oct 28 07:02:56 node-1 kernel: [    0.448574] ACPI: Using IOAPIC for interrupt routing
Oct 28 07:02:56 node-1 kernel: [    0.448615] HEST: Table parsing has been initialized.
Oct 28 07:02:56 node-1 kernel: [    0.448618] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 28 07:02:56 node-1 kernel: [    0.449172] ACPI: No dock devices found.
Oct 28 07:02:56 node-1 kernel: [    0.460665] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 28 07:02:56 node-1 kernel: [    0.460670] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 07:02:56 node-1 kernel: [    0.460674] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 28 07:02:56 node-1 kernel: [    0.460703] PCI host bridge to bus 0000:ff
Oct 28 07:02:56 node-1 kernel: [    0.460705] pci_bus 0000:ff: root bus resource [bus ff]
Oct 28 07:02:56 node-1 kernel: [    0.460713] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.460751] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 28 07:02:56 node-1 kernel: [    0.460781] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.460816] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.460846] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 28 07:02:56 node-1 kernel: [    0.460875] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 28 07:02:56 node-1 kernel: [    0.460906] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.460934] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.460966] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.460994] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461020] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461046] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461074] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461099] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461125] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461152] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461180] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461206] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461233] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 28 07:02:56 node-1 kernel: [    0.461260] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461286] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 28 07:02:56 node-1 kernel: [    0.461311] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461338] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461369] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 28 07:02:56 node-1 kernel: [    0.461404] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461435] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461464] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461494] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461524] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461555] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461584] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461616] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461645] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461678] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461709] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461741] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461777] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461806] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461833] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461864] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461896] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461932] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461966] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.461998] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462028] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462057] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462088] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462118] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462150] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462180] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462211] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462239] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462268] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462296] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462325] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462356] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462386] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462443] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 28 07:02:56 node-1 kernel: [    0.462446] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 07:02:56 node-1 kernel: [    0.462448] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 28 07:02:56 node-1 kernel: [    0.462466] PCI host bridge to bus 0000:7f
Oct 28 07:02:56 node-1 kernel: [    0.462468] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 28 07:02:56 node-1 kernel: [    0.462473] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462500] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 28 07:02:56 node-1 kernel: [    0.462528] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462557] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462578] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 28 07:02:56 node-1 kernel: [    0.462602] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 28 07:02:56 node-1 kernel: [    0.462628] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462653] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462677] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462701] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462725] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462752] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462779] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462804] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462829] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462859] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462880] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462903] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462926] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 28 07:02:56 node-1 kernel: [    0.462950] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.462972] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 28 07:02:56 node-1 kernel: [    0.462993] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463016] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463043] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 28 07:02:56 node-1 kernel: [    0.463075] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463103] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463131] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463158] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463183] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463209] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463234] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463261] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463286] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463312] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463339] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463367] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463395] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463421] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463445] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463472] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463497] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463523] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463551] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463577] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463601] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463626] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463651] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463678] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463704] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463733] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463763] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463789] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463811] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463837] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463863] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463892] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.463917] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.465158] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 28 07:02:56 node-1 kernel: [    0.465162] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 07:02:56 node-1 kernel: [    0.466288] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 28 07:02:56 node-1 kernel: [    0.466802] PCI host bridge to bus 0000:00
Oct 28 07:02:56 node-1 kernel: [    0.466805] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 28 07:02:56 node-1 kernel: [    0.466806] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 28 07:02:56 node-1 kernel: [    0.466808] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 28 07:02:56 node-1 kernel: [    0.466809] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 28 07:02:56 node-1 kernel: [    0.466810] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 28 07:02:56 node-1 kernel: [    0.466812] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 28 07:02:56 node-1 kernel: [    0.466813] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 28 07:02:56 node-1 kernel: [    0.466819] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 28 07:02:56 node-1 kernel: [    0.466901] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 28 07:02:56 node-1 kernel: [    0.466932] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 28 07:02:56 node-1 kernel: [    0.466973] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 28 07:02:56 node-1 kernel: [    0.466993] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 28 07:02:56 node-1 kernel: [    0.467023] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 28 07:02:56 node-1 kernel: [    0.467063] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 28 07:02:56 node-1 kernel: [    0.467081] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 28 07:02:56 node-1 kernel: [    0.467111] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 28 07:02:56 node-1 kernel: [    0.467151] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 28 07:02:56 node-1 kernel: [    0.467168] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.467237] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.467314] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.467389] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 28 07:02:56 node-1 kernel: [    0.467394] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 28 07:02:56 node-1 kernel: [    0.467478] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 28 07:02:56 node-1 kernel: [    0.467625] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 28 07:02:56 node-1 kernel: [    0.467642] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 28 07:02:56 node-1 kernel: [    0.467720] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 28 07:02:56 node-1 kernel: [    0.467774] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 28 07:02:56 node-1 kernel: [    0.467795] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 28 07:02:56 node-1 kernel: [    0.467851] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 28 07:02:56 node-1 kernel: [    0.467894] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 28 07:02:56 node-1 kernel: [    0.467921] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 28 07:02:56 node-1 kernel: [    0.467977] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 28 07:02:56 node-1 kernel: [    0.468020] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 28 07:02:56 node-1 kernel: [    0.468044] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 28 07:02:56 node-1 kernel: [    0.468061] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 28 07:02:56 node-1 kernel: [    0.468139] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 28 07:02:56 node-1 kernel: [    0.468189] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 28 07:02:56 node-1 kernel: [    0.468215] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 28 07:02:56 node-1 kernel: [    0.468461] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 28 07:02:56 node-1 kernel: [    0.468466] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 28 07:02:56 node-1 kernel: [    0.468472] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 28 07:02:56 node-1 kernel: [    0.468478] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 28 07:02:56 node-1 kernel: [    0.468486] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 28 07:02:56 node-1 kernel: [    0.468516] pci 0000:01:00.0: supports D1 D2
Oct 28 07:02:56 node-1 kernel: [    0.474764] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 28 07:02:56 node-1 kernel: [    0.474771] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 28 07:02:56 node-1 kernel: [    0.474775] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 28 07:02:56 node-1 kernel: [    0.474942] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 28 07:02:56 node-1 kernel: [    0.474975] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 28 07:02:56 node-1 kernel: [    0.482760] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 28 07:02:56 node-1 kernel: [    0.482767] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 28 07:02:56 node-1 kernel: [    0.482771] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 07:02:56 node-1 kernel: [    0.482855] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 28 07:02:56 node-1 kernel: [    0.482937] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 28 07:02:56 node-1 kernel: [    0.483013] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 28 07:02:56 node-1 kernel: [    0.483058] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 28 07:02:56 node-1 kernel: [    0.483061] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 07:02:56 node-1 kernel: [    0.483063] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 07:02:56 node-1 kernel: [    0.483115] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 28 07:02:56 node-1 kernel: [    0.483241] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 28 07:02:56 node-1 kernel: [    0.483294] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 28 07:02:56 node-1 kernel: [    0.483297] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 07:02:56 node-1 kernel: [    0.483299] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 07:02:56 node-1 kernel: [    0.483348] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 28 07:02:56 node-1 kernel: [    0.483482] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 28 07:02:56 node-1 kernel: [    0.483520] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 28 07:02:56 node-1 kernel: [    0.483643] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 28 07:02:56 node-1 kernel: [    0.483679] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 28 07:02:56 node-1 kernel: [    0.483798] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 28 07:02:56 node-1 kernel: [    0.483833] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 28 07:02:56 node-1 kernel: [    0.483952] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 28 07:02:56 node-1 kernel: [    0.483992] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 28 07:02:56 node-1 kernel: [    0.483995] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 07:02:56 node-1 kernel: [    0.483997] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 07:02:56 node-1 kernel: [    0.484057] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 28 07:02:56 node-1 kernel: [    0.484119] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 28 07:02:56 node-1 kernel: [    0.484171] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 28 07:02:56 node-1 kernel: [    0.484213] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 28 07:02:56 node-1 kernel: [    0.484294] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 28 07:02:56 node-1 kernel: [    0.484402] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 28 07:02:56 node-1 kernel: [    0.484404] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 07:02:56 node-1 kernel: [    0.484406] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 28 07:02:56 node-1 kernel: [    0.484481] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 28 07:02:56 node-1 kernel: [    0.484539] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 28 07:02:56 node-1 kernel: [    0.484591] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 28 07:02:56 node-1 kernel: [    0.484804] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 28 07:02:56 node-1 kernel: [    0.484807] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 28 07:02:56 node-1 kernel: [    0.484870] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 28 07:02:56 node-1 kernel: [    0.484923] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 28 07:02:56 node-1 kernel: [    0.484972] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 28 07:02:56 node-1 kernel: [    0.485182] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 28 07:02:56 node-1 kernel: [    0.485186] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 28 07:02:56 node-1 kernel: [    0.485244] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 28 07:02:56 node-1 kernel: [    0.485304] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 28 07:02:56 node-1 kernel: [    0.485356] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 28 07:02:56 node-1 kernel: [    0.485604] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 28 07:02:56 node-1 kernel: [    0.485607] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 28 07:02:56 node-1 kernel: [    0.485784] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 28 07:02:56 node-1 kernel: [    0.485822] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 28 07:02:56 node-1 kernel: [    0.485899] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 28 07:02:56 node-1 kernel: [    0.485917] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 28 07:02:56 node-1 kernel: [    0.485930] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 28 07:02:56 node-1 kernel: [    0.485944] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 28 07:02:56 node-1 kernel: [    0.485993] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 28 07:02:56 node-1 kernel: [    0.490767] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 28 07:02:56 node-1 kernel: [    0.490776] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 28 07:02:56 node-1 kernel: [    0.490828] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 28 07:02:56 node-1 kernel: [    0.491578] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 28 07:02:56 node-1 kernel: [    0.491581] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 07:02:56 node-1 kernel: [    0.491701] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 28 07:02:56 node-1 kernel: [    0.491807] PCI host bridge to bus 0000:80
Oct 28 07:02:56 node-1 kernel: [    0.491809] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 28 07:02:56 node-1 kernel: [    0.491811] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 28 07:02:56 node-1 kernel: [    0.491812] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 28 07:02:56 node-1 kernel: [    0.491821] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.491883] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.491950] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 28 07:02:56 node-1 kernel: [    0.492011] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 28 07:02:56 node-1 kernel: [    0.492016] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 28 07:02:56 node-1 kernel: [    0.492088] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 28 07:02:56 node-1 kernel: [    0.492384] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 28 07:02:56 node-1 kernel: [    0.492415] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 28 07:02:56 node-1 kernel: [    0.492445] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 28 07:02:56 node-1 kernel: [    0.492474] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 28 07:02:56 node-1 kernel: [    0.492504] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 07:02:56 node-1 kernel: [    0.492534] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 07:02:56 node-1 kernel: [    0.492563] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 07:02:56 node-1 kernel: [    0.492593] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 07:02:56 node-1 kernel: [    0.492677] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 28 07:02:56 node-1 kernel: [    0.492682] ACPI: \_SB_.UNC1: notify handler is installed
Oct 28 07:02:56 node-1 kernel: [    0.492683] ACPI: \_SB_.UNC0: notify handler is installed
Oct 28 07:02:56 node-1 kernel: [    0.492698] ACPI: \_SB_.PCI0: notify handler is installed
Oct 28 07:02:56 node-1 kernel: [    0.492750] ACPI: \_SB_.PCI1: notify handler is installed
Oct 28 07:02:56 node-1 kernel: [    0.492829] Found 4 acpi root devices
Oct 28 07:02:56 node-1 kernel: [    0.492934] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 28 07:02:56 node-1 kernel: [    0.492936] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 28 07:02:56 node-1 kernel: [    0.492938] vgaarb: loaded
Oct 28 07:02:56 node-1 kernel: [    0.492939] vgaarb: bridge control possible 0000:0c:00.0
Oct 28 07:02:56 node-1 kernel: [    0.493056] SCSI subsystem initialized
Oct 28 07:02:56 node-1 kernel: [    0.493121] libata version 3.00 loaded.
Oct 28 07:02:56 node-1 kernel: [    0.493136] ACPI: bus type USB registered
Oct 28 07:02:56 node-1 kernel: [    0.493147] usbcore: registered new interface driver usbfs
Oct 28 07:02:56 node-1 kernel: [    0.493152] usbcore: registered new interface driver hub
Oct 28 07:02:56 node-1 kernel: [    0.493176] usbcore: registered new device driver usb
Oct 28 07:02:56 node-1 kernel: [    0.493346] PCI: Using ACPI for IRQ routing
Oct 28 07:02:56 node-1 kernel: [    0.496955] PCI: pci_cache_line_size set to 64 bytes
Oct 28 07:02:56 node-1 kernel: [    0.497161] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 28 07:02:56 node-1 kernel: [    0.497162] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct 28 07:02:56 node-1 kernel: [    0.497163] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 28 07:02:56 node-1 kernel: [    0.497228] NetLabel: Initializing
Oct 28 07:02:56 node-1 kernel: [    0.497229] NetLabel:  domain hash size = 128
Oct 28 07:02:56 node-1 kernel: [    0.497230] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 28 07:02:56 node-1 kernel: [    0.497240] NetLabel:  unlabeled traffic allowed by default
Oct 28 07:02:56 node-1 kernel: [    0.497296] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 28 07:02:56 node-1 kernel: [    0.497300] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 28 07:02:56 node-1 kernel: [    0.499357] Switched to clocksource hpet
Oct 28 07:02:56 node-1 kernel: [    0.503192] AppArmor: AppArmor Filesystem Enabled
Oct 28 07:02:56 node-1 kernel: [    0.503207] pnp: PnP ACPI init
Oct 28 07:02:56 node-1 kernel: [    0.503214] ACPI: bus type PNP registered
Oct 28 07:02:56 node-1 kernel: [    0.503331] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 28 07:02:56 node-1 kernel: [    0.503339] pnp 00:01: [dma 4]
Oct 28 07:02:56 node-1 kernel: [    0.503355] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 28 07:02:56 node-1 kernel: [    0.503382] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 28 07:02:56 node-1 kernel: [    0.503402] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 28 07:02:56 node-1 kernel: [    0.503420] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 28 07:02:56 node-1 kernel: [    0.503453] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 28 07:02:56 node-1 kernel: [    0.503506] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 28 07:02:56 node-1 kernel: [    0.503508] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 28 07:02:56 node-1 kernel: [    0.503510] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 28 07:02:56 node-1 kernel: [    0.503511] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 28 07:02:56 node-1 kernel: [    0.503513] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 28 07:02:56 node-1 kernel: [    0.503517] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 28 07:02:56 node-1 kernel: [    0.503520] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 28 07:02:56 node-1 kernel: [    0.503521] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 28 07:02:56 node-1 kernel: [    0.503523] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 28 07:02:56 node-1 kernel: [    0.503524] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 28 07:02:56 node-1 kernel: [    0.503526] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 28 07:02:56 node-1 kernel: [    0.503527] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 28 07:02:56 node-1 kernel: [    0.503529] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 28 07:02:56 node-1 kernel: [    0.503531] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 28 07:02:56 node-1 kernel: [    0.503613] pnp 00:07: [dma 0 disabled]
Oct 28 07:02:56 node-1 kernel: [    0.503641] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 28 07:02:56 node-1 kernel: [    0.503716] pnp 00:08: [dma 0 disabled]
Oct 28 07:02:56 node-1 kernel: [    0.503751] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 28 07:02:56 node-1 kernel: [    0.503802] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 28 07:02:56 node-1 kernel: [    0.504146] pnp: PnP ACPI: found 10 devices
Oct 28 07:02:56 node-1 kernel: [    0.504147] ACPI: bus type PNP unregistered
Oct 28 07:02:56 node-1 kernel: [    0.510512] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 28 07:02:56 node-1 kernel: [    0.510515] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 28 07:02:56 node-1 kernel: [    0.510517] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 28 07:02:56 node-1 kernel: [    0.510522] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 28 07:02:56 node-1 kernel: [    0.510523] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 07:02:56 node-1 kernel: [    0.510538] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 28 07:02:56 node-1 kernel: [    0.510567] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 28 07:02:56 node-1 kernel: [    0.510582] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 28 07:02:56 node-1 kernel: [    0.510611] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 28 07:02:56 node-1 kernel: [    0.510625] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 28 07:02:56 node-1 kernel: [    0.510654] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 28 07:02:56 node-1 kernel: [    0.510669] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 28 07:02:56 node-1 kernel: [    0.510697] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 28 07:02:56 node-1 kernel: [    0.510699] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 07:02:56 node-1 kernel: [    0.510714] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 07:02:56 node-1 kernel: [    0.510743] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 28 07:02:56 node-1 kernel: [    0.510745] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 07:02:56 node-1 kernel: [    0.510759] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 07:02:56 node-1 kernel: [    0.510788] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 28 07:02:56 node-1 kernel: [    0.510790] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 07:02:56 node-1 kernel: [    0.510793] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 07:02:56 node-1 kernel: [    0.510797] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 28 07:02:56 node-1 kernel: [    0.510798] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 28 07:02:56 node-1 kernel: [    0.510801] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 07:02:56 node-1 kernel: [    0.510804] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 28 07:02:56 node-1 kernel: [    0.510809] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 28 07:02:56 node-1 kernel: [    0.510817] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 28 07:02:56 node-1 kernel: [    0.510821] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 28 07:02:56 node-1 kernel: [    0.510827] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 28 07:02:56 node-1 kernel: [    0.510828] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 28 07:02:56 node-1 kernel: [    0.510829] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 28 07:02:56 node-1 kernel: [    0.510830] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 28 07:02:56 node-1 kernel: [    0.510830] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 28 07:02:56 node-1 kernel: [    0.510831] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 28 07:02:56 node-1 kernel: [    0.510832] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 28 07:02:56 node-1 kernel: [    0.510833] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 28 07:02:56 node-1 kernel: [    0.510834] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 28 07:02:56 node-1 kernel: [    0.510835] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 28 07:02:56 node-1 kernel: [    0.510836] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 28 07:02:56 node-1 kernel: [    0.510837] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 28 07:02:56 node-1 kernel: [    0.510838] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 28 07:02:56 node-1 kernel: [    0.510838] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 28 07:02:56 node-1 kernel: [    0.510839] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 28 07:02:56 node-1 kernel: [    0.510840] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 28 07:02:56 node-1 kernel: [    0.510841] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 28 07:02:56 node-1 kernel: [    0.510842] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 28 07:02:56 node-1 kernel: [    0.510843] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 28 07:02:56 node-1 kernel: [    0.510844] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 28 07:02:56 node-1 kernel: [    0.510845] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 28 07:02:56 node-1 kernel: [    0.510846] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 28 07:02:56 node-1 kernel: [    0.510848] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 28 07:02:56 node-1 kernel: [    0.510849] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 28 07:02:56 node-1 kernel: [    0.510886] NET: Registered protocol family 2
Oct 28 07:02:56 node-1 kernel: [    0.511146] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 28 07:02:56 node-1 kernel: [    0.511484] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 28 07:02:56 node-1 kernel: [    0.511628] TCP: Hash tables configured (established 262144 bind 65536)
Oct 28 07:02:56 node-1 kernel: [    0.511664] TCP: reno registered
Oct 28 07:02:56 node-1 kernel: [    0.511693] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 28 07:02:56 node-1 kernel: [    0.511790] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 28 07:02:56 node-1 kernel: [    0.511933] NET: Registered protocol family 1
Oct 28 07:02:56 node-1 kernel: [    0.551452] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 28 07:02:56 node-1 kernel: [    0.551465] PCI: CLS 64 bytes, default 64
Oct 28 07:02:56 node-1 kernel: [    0.551541] Trying to unpack rootfs image as initramfs...
Oct 28 07:02:56 node-1 kernel: [    0.770923] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Oct 28 07:02:56 node-1 kernel: [    0.770984] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 28 07:02:56 node-1 kernel: [    0.770987] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct 28 07:02:56 node-1 kernel: [    0.771409] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 07:02:56 node-1 kernel: [    0.771416] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 07:02:56 node-1 kernel: [    0.771420] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 07:02:56 node-1 kernel: [    0.771426] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 07:02:56 node-1 kernel: [    0.771438] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 07:02:56 node-1 kernel: [    0.771455] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 07:02:56 node-1 kernel: [    0.771470] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 07:02:56 node-1 kernel: [    0.771486] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 07:02:56 node-1 kernel: [    0.771498] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 07:02:56 node-1 kernel: [    0.771508] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 07:02:56 node-1 kernel: [    0.771514] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 07:02:56 node-1 kernel: [    0.771520] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 07:02:56 node-1 kernel: [    0.771529] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 07:02:56 node-1 kernel: [    0.771542] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 07:02:56 node-1 kernel: [    0.771555] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 07:02:56 node-1 kernel: [    0.771567] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 07:02:56 node-1 kernel: [    0.771672] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 28 07:02:56 node-1 kernel: [    0.771678] Scanning for low memory corruption every 60 seconds
Oct 28 07:02:56 node-1 kernel: [    0.772106] Initialise system trusted keyring
Oct 28 07:02:56 node-1 kernel: [    0.772158] audit: initializing netlink socket (disabled)
Oct 28 07:02:56 node-1 kernel: [    0.772173] type=2000 audit(1477638139.720:1): initialized
Oct 28 07:02:56 node-1 kernel: [    0.789905] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 28 07:02:56 node-1 kernel: [    0.791423] zbud: loaded
Oct 28 07:02:56 node-1 kernel: [    0.791549] VFS: Disk quotas dquot_6.5.2
Oct 28 07:02:56 node-1 kernel: [    0.791583] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 28 07:02:56 node-1 kernel: [    0.791958] fuse init (API version 7.22)
Oct 28 07:02:56 node-1 kernel: [    0.792017] msgmni has been set to 32768
Oct 28 07:02:56 node-1 kernel: [    0.792064] Key type big_key registered
Oct 28 07:02:56 node-1 kernel: [    0.792552] Key type asymmetric registered
Oct 28 07:02:56 node-1 kernel: [    0.792554] Asymmetric key parser 'x509' registered
Oct 28 07:02:56 node-1 kernel: [    0.792577] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 28 07:02:56 node-1 kernel: [    0.792648] io scheduler noop registered
Oct 28 07:02:56 node-1 kernel: [    0.792650] io scheduler deadline registered (default)
Oct 28 07:02:56 node-1 kernel: [    0.792668] io scheduler cfq registered
Oct 28 07:02:56 node-1 kernel: [    0.793076] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    0.793200] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    0.793316] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    0.793426] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    0.793540] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    0.793640] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    0.794057] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 28 07:02:56 node-1 kernel: [    0.794100] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 28 07:02:56 node-1 kernel: [    0.794116] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 28 07:02:56 node-1 kernel: [    0.794126] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794128] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794131] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 28 07:02:56 node-1 kernel: [    0.794136] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794138] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794139] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794140] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794142] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794143] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794144] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794146] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794147] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794149] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794150] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794152] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794154] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 28 07:02:56 node-1 kernel: [    0.794159] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794161] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 28 07:02:56 node-1 kernel: [    0.794176] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794179] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 28 07:02:56 node-1 kernel: [    0.794190] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794192] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 28 07:02:56 node-1 kernel: [    0.794195] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 28 07:02:56 node-1 kernel: [    0.794234] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 28 07:02:56 node-1 kernel: [    0.794240] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 28 07:02:56 node-1 kernel: [    0.794244] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 28 07:02:56 node-1 kernel: [    0.794253] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 28 07:02:56 node-1 kernel: [    0.794295] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 28 07:02:56 node-1 kernel: [    0.794297] vesafb: scrolling: redraw
Oct 28 07:02:56 node-1 kernel: [    0.794298] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 28 07:02:56 node-1 kernel: [    0.814936] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 28 07:02:56 node-1 kernel: [    0.823505] Console: switching to colour frame buffer device 80x30
Oct 28 07:02:56 node-1 kernel: [    0.832187] fb0: VESA VGA frame buffer device
Oct 28 07:02:56 node-1 kernel: [    0.832384] intel_idle: MWAIT substates: 0x2120
Oct 28 07:02:56 node-1 kernel: [    0.832385] intel_idle: v0.4 model 0x3F
Oct 28 07:02:56 node-1 kernel: [    0.832386] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 28 07:02:56 node-1 kernel: [    0.832632] ipmi message handler version 39.2
Oct 28 07:02:56 node-1 kernel: [    0.832909] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 28 07:02:56 node-1 kernel: [    0.833345] ACPI: AC Adapter [P111] (on-line)
Oct 28 07:02:56 node-1 kernel: [    0.838581] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 28 07:02:56 node-1 kernel: [    0.849572] ACPI: Power Button [PWRB]
Oct 28 07:02:56 node-1 kernel: [    0.855345] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 28 07:02:56 node-1 kernel: [    0.866983] ACPI: Power Button [PWRF]
Oct 28 07:02:56 node-1 kernel: [    0.884812] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 28 07:02:56 node-1 kernel: [    0.896483] pstore: Registered erst as persistent store backend
Oct 28 07:02:56 node-1 kernel: [    0.902662] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 28 07:02:56 node-1 kernel: [    0.914610] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 28 07:02:56 node-1 kernel: [    0.941374] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 28 07:02:56 node-1 kernel: [    0.974791] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 28 07:02:56 node-1 kernel: [    0.988822] Linux agpgart interface v0.103
Oct 28 07:02:56 node-1 kernel: [    0.996490] brd: module loaded
Oct 28 07:02:56 node-1 kernel: [    1.003545] loop: module loaded
Oct 28 07:02:56 node-1 kernel: [    1.010286] libphy: Fixed MDIO Bus: probed
Oct 28 07:02:56 node-1 kernel: [    1.016780] tun: Universal TUN/TAP device driver, 1.6
Oct 28 07:02:56 node-1 kernel: [    1.023254] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 28 07:02:56 node-1 kernel: [    1.029786] PPP generic driver version 2.4.2
Oct 28 07:02:56 node-1 kernel: [    1.036187] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 28 07:02:56 node-1 kernel: [    1.042638] ehci-pci: EHCI PCI platform driver
Oct 28 07:02:56 node-1 kernel: [    1.049247] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 28 07:02:56 node-1 kernel: [    1.055673] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 28 07:02:56 node-1 kernel: [    1.068305] ehci-pci 0000:00:1a.0: debug port 2
Oct 28 07:02:56 node-1 kernel: [    1.078610] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 28 07:02:56 node-1 kernel: [    1.078629] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 28 07:02:56 node-1 kernel: [    1.094856] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 28 07:02:56 node-1 kernel: [    1.101015] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 28 07:02:56 node-1 kernel: [    1.107342] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 28 07:02:56 node-1 kernel: [    1.119440] usb usb1: Product: EHCI Host Controller
Oct 28 07:02:56 node-1 kernel: [    1.125544] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 28 07:02:56 node-1 kernel: [    1.131683] usb usb1: SerialNumber: 0000:00:1a.0
Oct 28 07:02:56 node-1 kernel: [    1.137711] hub 1-0:1.0: USB hub found
Oct 28 07:02:56 node-1 kernel: [    1.143501] hub 1-0:1.0: 2 ports detected
Oct 28 07:02:56 node-1 kernel: [    1.149307] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 28 07:02:56 node-1 kernel: [    1.154899] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 28 07:02:56 node-1 kernel: [    1.165818] ehci-pci 0000:00:1d.0: debug port 2
Oct 28 07:02:56 node-1 kernel: [    1.175113] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 28 07:02:56 node-1 kernel: [    1.175116] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 28 07:02:56 node-1 kernel: [    1.190774] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 28 07:02:56 node-1 kernel: [    1.195988] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 28 07:02:56 node-1 kernel: [    1.201292] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 28 07:02:56 node-1 kernel: [    1.211891] usb usb2: Product: EHCI Host Controller
Oct 28 07:02:56 node-1 kernel: [    1.217361] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 28 07:02:56 node-1 kernel: [    1.222919] usb usb2: SerialNumber: 0000:00:1d.0
Oct 28 07:02:56 node-1 kernel: [    1.228442] hub 2-0:1.0: USB hub found
Oct 28 07:02:56 node-1 kernel: [    1.233795] hub 2-0:1.0: 2 ports detected
Oct 28 07:02:56 node-1 kernel: [    1.239106] ehci-platform: EHCI generic platform driver
Oct 28 07:02:56 node-1 kernel: [    1.244335] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 28 07:02:56 node-1 kernel: [    1.249660] ohci-pci: OHCI PCI platform driver
Oct 28 07:02:56 node-1 kernel: [    1.254965] ohci-platform: OHCI generic platform driver
Oct 28 07:02:56 node-1 kernel: [    1.260173] uhci_hcd: USB Universal Host Controller Interface driver
Oct 28 07:02:56 node-1 kernel: [    1.265522] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 28 07:02:56 node-1 kernel: [    1.458554] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 28 07:02:56 node-1 kernel: [    1.766305] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct 28 07:02:56 node-1 kernel: [    1.782639] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 28 07:02:56 node-1 kernel: [    1.788261] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 28 07:02:56 node-1 kernel: [    1.794031] hub 1-1:1.0: USB hub found
Oct 28 07:02:56 node-1 kernel: [    1.799623] hub 1-1:1.0: 6 ports detected
Oct 28 07:02:56 node-1 kernel: [    1.914159] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 28 07:02:56 node-1 kernel: [    2.304197] i8042: No controller found
Oct 28 07:02:56 node-1 kernel: [    2.309732] mousedev: PS/2 mouse device common for all mice
Oct 28 07:02:56 node-1 kernel: [    2.315454] rtc_cmos 00:02: RTC can wake from S4
Oct 28 07:02:56 node-1 kernel: [    2.321183] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 28 07:02:56 node-1 kernel: [    2.322622] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 28 07:02:56 node-1 kernel: [    2.322623] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 28 07:02:56 node-1 kernel: [    2.323254] hub 2-1:1.0: USB hub found
Oct 28 07:02:56 node-1 kernel: [    2.323495] hub 2-1:1.0: 8 ports detected
Oct 28 07:02:56 node-1 kernel: [    2.349504] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 28 07:02:56 node-1 kernel: [    2.360837] device-mapper: uevent: version 1.0.3
Oct 28 07:02:56 node-1 kernel: [    2.366527] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 28 07:02:56 node-1 kernel: [    2.377879] ledtrig-cpu: registered to indicate activity on CPUs
Oct 28 07:02:56 node-1 kernel: [    2.383832] TCP: cubic registered
Oct 28 07:02:56 node-1 kernel: [    2.389669] NET: Registered protocol family 10
Oct 28 07:02:56 node-1 kernel: [    2.395693] NET: Registered protocol family 17
Oct 28 07:02:56 node-1 kernel: [    2.401443] Key type dns_resolver registered
Oct 28 07:02:56 node-1 kernel: [    2.407480] Loading compiled-in X.509 certificates
Oct 28 07:02:56 node-1 kernel: [    2.413685] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Oct 28 07:02:56 node-1 kernel: [    2.425372] registered taskstats version 1
Oct 28 07:02:56 node-1 kernel: [    2.433467] Key type trusted registered
Oct 28 07:02:56 node-1 kernel: [    2.441132] Key type encrypted registered
Oct 28 07:02:56 node-1 kernel: [    2.446641] AppArmor: AppArmor sha1 policy hashing enabled
Oct 28 07:02:56 node-1 kernel: [    2.452142] IMA: No TPM chip found, activating TPM-bypass!
Oct 28 07:02:56 node-1 kernel: [    2.458262] regulator-dummy: disabling
Oct 28 07:02:56 node-1 kernel: [    2.463734]   Magic number: 4:830:16
Oct 28 07:02:56 node-1 kernel: [    2.469489] rtc_cmos 00:02: setting system clock to 2016-10-28 07:02:22 UTC (1477638142)
Oct 28 07:02:56 node-1 kernel: [    2.482068] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 28 07:02:56 node-1 kernel: [    2.487787] EDD information not available.
Oct 28 07:02:56 node-1 kernel: [    2.493478] PM: Hibernation image not present or could not be loaded.
Oct 28 07:02:56 node-1 kernel: [    2.494340] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 28 07:02:56 node-1 kernel: [    2.505841] Write protecting the kernel read-only data: 12288k
Oct 28 07:02:56 node-1 kernel: [    2.512230] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 28 07:02:56 node-1 kernel: [    2.525128] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 28 07:02:56 node-1 kernel: [    2.557047] device-mapper: multipath: version 1.6.0 loaded
Oct 28 07:02:56 node-1 kernel: [    2.564968] systemd-udevd[214]: starting version 204
Oct 28 07:02:56 node-1 kernel: [    2.589482] md: linear personality registered for level -1
Oct 28 07:02:56 node-1 kernel: [    2.597768] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 28 07:02:56 node-1 kernel: [    2.610203] md: multipath personality registered for level -4
Oct 28 07:02:56 node-1 kernel: [    2.618280] md: raid0 personality registered for level 0
Oct 28 07:02:56 node-1 kernel: [    2.626766] md: raid1 personality registered for level 1
Oct 28 07:02:56 node-1 kernel: [    2.633930] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 28 07:02:56 node-1 kernel: [    2.640314] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 28 07:02:56 node-1 kernel: [    2.646564] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 28 07:02:56 node-1 kernel: [    2.647241] megasas: FW now in Ready state
Oct 28 07:02:56 node-1 kernel: [    2.647315] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.647351] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.647389] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.647434] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.647479] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.647505] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.647543] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.647579] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.647617] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.647659] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.647687] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.647732] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.647777] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.647813] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.647849] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.647884] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.648054] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 28 07:02:56 node-1 kernel: [    2.679235] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Oct 28 07:02:56 node-1 kernel: [    2.692474] 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
Oct 28 07:02:56 node-1 kernel: [    2.706326] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 28 07:02:56 node-1 kernel: [    2.713297] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.713301] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.713305] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.713308] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.713350] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 28 07:02:56 node-1 kernel: [    2.736418] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Oct 28 07:02:56 node-1 kernel: [    2.737510] raid6: sse2x1   11279 MB/s
Oct 28 07:02:56 node-1 kernel: [    2.756525] 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
Oct 28 07:02:56 node-1 kernel: [    2.769961] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 28 07:02:56 node-1 kernel: [    2.805416] raid6: sse2x2   11684 MB/s
Oct 28 07:02:56 node-1 kernel: [    2.877354] raid6: sse2x4   10130 MB/s
Oct 28 07:02:56 node-1 kernel: [    2.949294] raid6: avx2x1   14945 MB/s
Oct 28 07:02:56 node-1 kernel: [    3.021239] raid6: avx2x2   18891 MB/s
Oct 28 07:02:56 node-1 kernel: [    3.093167] raid6: avx2x4   21310 MB/s
Oct 28 07:02:56 node-1 kernel: [    3.099192] raid6: using algorithm avx2x4 (21310 MB/s)
Oct 28 07:02:56 node-1 kernel: [    3.105123] raid6: using avx2x2 recovery algorithm
Oct 28 07:02:56 node-1 kernel: [    3.110944] Switched to clocksource tsc
Oct 28 07:02:56 node-1 kernel: [    3.110946] megasas:IOC Init cmd success
Oct 28 07:02:56 node-1 kernel: [    3.110999] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.111039] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.111077] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.111100] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.111127] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.111164] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.111318] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.112504] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 28 07:02:56 node-1 kernel: [    3.112505] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 28 07:02:56 node-1 kernel: [    3.112506] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 28 07:02:56 node-1 kernel: [    3.112506] usb 2-1.4: Manufacturer: Avocent
Oct 28 07:02:56 node-1 kernel: [    3.112507] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 28 07:02:56 node-1 kernel: [    3.121374] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Oct 28 07:02:56 node-1 kernel: [    3.121375] 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
Oct 28 07:02:56 node-1 kernel: [    3.121376] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 28 07:02:56 node-1 kernel: [    3.121435] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.121464] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.121497] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.121528] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.121608] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.131424] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Oct 28 07:02:56 node-1 kernel: [    3.131425] 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
Oct 28 07:02:56 node-1 kernel: [    3.131426] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 28 07:02:56 node-1 kernel: [    3.131487] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.131521] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.131558] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.131589] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.131671] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 28 07:02:56 node-1 kernel: [    3.133167] megasas: INIT adapter done
Oct 28 07:02:56 node-1 kernel: [    3.205078] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 28 07:02:56 node-1 kernel: [    3.205420] scsi0 : LSI SAS based MegaRAID driver
Oct 28 07:02:56 node-1 kernel: [    3.208785] xor: automatically using best checksumming function:
Oct 28 07:02:56 node-1 kernel: [    3.212538] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 28 07:02:56 node-1 kernel: [    3.223207] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 28 07:02:56 node-1 kernel: [    3.227176] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 28 07:02:56 node-1 kernel: [    3.227339] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 28 07:02:56 node-1 kernel: [    3.227487] sd 0:2:0:0: [sda] Write Protect is off
Oct 28 07:02:56 node-1 kernel: [    3.227488] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 28 07:02:56 node-1 kernel: [    3.227567] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 28 07:02:56 node-1 kernel: [    3.231734] hidraw: raw HID events driver (C) Jiri Kosina
Oct 28 07:02:56 node-1 kernel: [    3.249907]    avx       : 35482.000 MB/sec
Oct 28 07:02:56 node-1 kernel: [    3.256740]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Oct 28 07:02:56 node-1 kernel: [    3.258301] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 28 07:02:56 node-1 kernel: [    3.314396] usbcore: registered new interface driver usbhid
Oct 28 07:02:56 node-1 kernel: [    3.314397] usbhid: USB HID core driver
Oct 28 07:02:56 node-1 kernel: [    3.356947] async_tx: api initialized (async)
Oct 28 07:02:56 node-1 kernel: [    3.382195] 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
Oct 28 07:02:56 node-1 kernel: [    3.395128] 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
Oct 28 07:02:56 node-1 kernel: [    3.408019] 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
Oct 28 07:02:56 node-1 kernel: [    3.420858] 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
Oct 28 07:02:56 node-1 kernel: [    3.434284] 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
Oct 28 07:02:56 node-1 kernel: [    3.448046] md: raid6 personality registered for level 6
Oct 28 07:02:56 node-1 kernel: [    3.448049] 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
Oct 28 07:02:56 node-1 kernel: [    3.468998] md: raid5 personality registered for level 5
Oct 28 07:02:56 node-1 kernel: [    3.476009] md: raid4 personality registered for level 4
Oct 28 07:02:56 node-1 kernel: [    3.485179] random: lvm urandom read with 32 bits of entropy available
Oct 28 07:02:56 node-1 kernel: [    3.493357] md: raid10 personality registered for level 10
Oct 28 07:02:56 node-1 kernel: [    3.549725] multipathd (369): /proc/369/oom_adj is deprecated, please use /proc/369/oom_score_adj instead.
Oct 28 07:02:56 node-1 kernel: [    3.659735] bio: create slab <bio-1> at 1
Oct 28 07:02:56 node-1 kernel: [    4.411555] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 07:02:56 node-1 kernel: [    5.064661] init: plymouth-upstart-bridge main process (552) terminated with status 1
Oct 28 07:02:56 node-1 kernel: [    5.077741] init: plymouth-upstart-bridge main process ended, respawning
Oct 28 07:02:56 node-1 kernel: [    5.087262] init: plymouth-upstart-bridge main process (565) terminated with status 1
Oct 28 07:02:56 node-1 kernel: [    5.100135] init: plymouth-upstart-bridge main process ended, respawning
Oct 28 07:02:56 node-1 kernel: [    5.108904] random: nonblocking pool is initialized
Oct 28 07:02:56 node-1 kernel: [    5.217801] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct 28 07:02:56 node-1 kernel: [    5.245332] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 28 07:02:56 node-1 kernel: [    5.371487] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 28 07:02:56 node-1 kernel: [    5.419384] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 28 07:02:56 node-1 kernel: [    5.531392] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 07:02:56 node-1 kernel: [    5.739529] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 28 07:02:56 node-1 kernel: [    5.779305] XFS (dm-0): Mounting Filesystem
Oct 28 07:02:56 node-1 kernel: [    5.970946] XFS (dm-0): Ending clean mount
Oct 28 07:02:56 node-1 kernel: [    6.056417] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 07:02:56 node-1 kernel: [    6.099472] XFS (dm-1): Mounting Filesystem
Oct 28 07:02:56 node-1 kernel: [    6.162270] XFS (dm-1): Ending clean mount
Oct 28 07:02:56 node-1 kernel: [    8.002559] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 28 07:02:56 node-1 kernel: [    8.029108] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 28 07:02:56 node-1 kernel: [    8.208817] systemd-udevd[781]: starting version 204
Oct 28 07:02:56 node-1 kernel: [    8.459168] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 28 07:02:56 node-1 kernel: [    8.459174] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 28 07:02:56 node-1 kernel: [    8.459176] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 28 07:02:56 node-1 kernel: [    8.459178] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 28 07:02:56 node-1 kernel: [    8.459190] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 28 07:02:56 node-1 kernel: [    8.463815] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 28 07:02:56 node-1 kernel: [    8.494531] IPMI System Interface driver.
Oct 28 07:02:56 node-1 kernel: [    8.494570] ipmi_si: probing via ACPI
Oct 28 07:02:56 node-1 kernel: [    8.494593] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 28 07:02:56 node-1 kernel: [    8.494594] ipmi_si: Adding ACPI-specified kcs state machine
Oct 28 07:02:56 node-1 kernel: [    8.494603] ipmi_si: probing via SMBIOS
Oct 28 07:02:56 node-1 kernel: [    8.494604] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 28 07:02:56 node-1 kernel: [    8.494605] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 28 07:02:56 node-1 kernel: [    8.494607] ipmi_si: probing via SPMI
Oct 28 07:02:56 node-1 kernel: [    8.494609] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 28 07:02:56 node-1 kernel: [    8.494609] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 28 07:02:56 node-1 kernel: [    8.494611] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 28 07:02:56 node-1 kernel: [    8.529026] systemd-udevd[809]: renamed network interface eth0 to enp6s0
Oct 28 07:02:56 node-1 kernel: [    8.537195] power_meter ACPI000D:00: Found ACPI power meter.
Oct 28 07:02:56 node-1 kernel: [    8.537203] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 28 07:02:56 node-1 kernel: [    8.549397] wmi: Mapper loaded
Oct 28 07:02:56 node-1 kernel: [    8.560918] systemd-udevd[803]: renamed network interface eth1 to enp7s0
Oct 28 07:02:56 node-1 kernel: [    8.597010] systemd-udevd[798]: renamed network interface eth2 to enp8s0
Oct 28 07:02:56 node-1 kernel: [    8.630195] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 28 07:02:56 node-1 kernel: [    8.630202] ipmi_si 00:09: IPMI kcs interface initialized
Oct 28 07:02:56 node-1 kernel: [    8.632874] systemd-udevd[800]: renamed network interface eth3 to enp9s0
Oct 28 07:02:56 node-1 kernel: [    8.961356] type=1400 audit(1477638148.993:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1068 comm="apparmor_parser"
Oct 28 07:02:56 node-1 kernel: [    8.961519] type=1400 audit(1477638148.993:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1068 comm="apparmor_parser"
Oct 28 07:02:56 node-1 kernel: [    8.961648] type=1400 audit(1477638148.993:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1068 comm="apparmor_parser"
Oct 28 07:02:56 node-1 kernel: [    8.983635] type=1400 audit(1477638149.013:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1072 comm="apparmor_parser"
Oct 28 07:02:56 node-1 kernel: [    8.983782] type=1400 audit(1477638149.013:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1072 comm="apparmor_parser"
Oct 28 07:02:56 node-1 kernel: [    8.983899] type=1400 audit(1477638149.013:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1072 comm="apparmor_parser"
Oct 28 07:02:56 node-1 kernel: [    8.988127] type=1400 audit(1477638149.017:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1070 comm="apparmor_parser"
Oct 28 07:02:56 node-1 kernel: [    8.988288] type=1400 audit(1477638149.021:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1070 comm="apparmor_parser"
Oct 28 07:02:56 node-1 kernel: [    8.988411] type=1400 audit(1477638149.021:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1070 comm="apparmor_parser"
Oct 28 07:02:56 node-1 kernel: [    8.997595] type=1400 audit(1477638149.029:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1069 comm="apparmor_parser"
Oct 28 07:02:56 node-1 kernel: [    9.481073] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 28 07:02:56 node-1 kernel: [    9.482779] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 28 07:02:56 node-1 kernel: [    9.665886] enic 0000:06:00.0 enp6s0: Link UP
Oct 28 07:02:56 node-1 kernel: [    9.667903] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 28 07:02:56 node-1 kernel: [    9.667911] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 28 07:02:56 node-1 kernel: [   19.048788] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 28 07:02:56 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 28 07:02:57 node-1 failsafe: Failsafe of 120 seconds reached.
Oct 28 07:02:57 node-1 kernel: [   38.002181] init: failsafe main process (8420) killed by TERM signal
Oct 28 07:02:58 node-1 dbus[8485]: [system] AppArmor D-Bus mediation is enabled
Oct 28 07:02:58 node-1 kernel: [   38.173570] audit_printk_skb: 30 callbacks suppressed
Oct 28 07:02:58 node-1 kernel: [   38.173572] type=1400 audit(1477638178.162:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8538 comm="apparmor_parser"
Oct 28 07:02:58 node-1 kernel: [   38.173840] type=1400 audit(1477638178.162:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8537 comm="apparmor_parser"
Oct 28 07:02:58 node-1 kernel: [   38.173845] type=1400 audit(1477638178.162:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8537 comm="apparmor_parser"
Oct 28 07:02:58 node-1 kernel: [   38.173847] type=1400 audit(1477638178.162:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8537 comm="apparmor_parser"
Oct 28 07:02:58 node-1 kernel: [   38.174079] type=1400 audit(1477638178.162:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8537 comm="apparmor_parser"
Oct 28 07:02:58 node-1 kernel: [   38.174081] type=1400 audit(1477638178.162:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8537 comm="apparmor_parser"
Oct 28 07:02:58 node-1 kernel: [   38.174193] type=1400 audit(1477638178.162:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8537 comm="apparmor_parser"
Oct 28 07:02:58 node-1 kernel: [   38.243657] type=1400 audit(1477638178.234:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8540 comm="apparmor_parser"
Oct 28 07:02:58 node-1 cron[8577]: (CRON) INFO (pidfile fd = 3)
Oct 28 07:02:58 node-1 anacron[8613]: Anacron 2.3 started on 2016-10-28
Oct 28 07:02:58 node-1 cron[8616]: (CRON) STARTUP (fork ok)
Oct 28 07:02:58 node-1 anacron[8613]: Will run job `cron.daily' in 5 min.
Oct 28 07:02:58 node-1 anacron[8613]: Will run job `cron.weekly' in 10 min.
Oct 28 07:02:58 node-1 anacron[8613]: Will run job `cron.monthly' in 15 min.
Oct 28 07:02:58 node-1 anacron[8613]: Jobs will be executed sequentially
Oct 28 07:02:58 node-1 multipathd: path checkers start up
Oct 28 07:02:58 node-1 cron[8616]: (CRON) INFO (Running @reboot jobs)
Oct 28 07:02:58 node-1 postfix/master[8757]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 28 07:03:01 node-1 CRON[8933]: (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")
Oct 28 07:03:02 node-1 puppet-agent[8953]: Reopening log files
Oct 28 07:03:02 node-1 puppet-agent[8953]: Could not request certificate: Connection refused - connect(2)
Oct 28 07:03:16 node-1 puppet-user[9161]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 28 07:03:16 node-1 puppet-user[9161]: Compiled catalog for node-1.domain.tld in environment production in 0.04 seconds
Oct 28 07:03:17 node-1 puppet-user[9161]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 28 07:03:17 node-1 puppet-user[9161]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 28 07:03:17 node-1 puppet-user[9161]: Finished catalog run in 0.91 seconds
Oct 28 07:03:18 node-1 multipathd: uevent trigger error
Oct 28 07:03:18 node-1 puppet-user[9761]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 28 07:03:18 node-1 puppet-user[9761]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Oct 28 07:03:18 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 28 07:03:18 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 28 07:03:18 node-1 puppet-user[9761]: (/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"]'
Oct 28 07:03:18 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 28 07:03:18 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 28 07:03:18 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 28 07:03:18 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 28 07:03:18 node-1 puppet-user[9761]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 28 07:03:18 node-1 puppet-user[9761]: Finished catalog run in 0.07 seconds
Oct 28 07:03:19 node-1 puppet-user[10213]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 28 07:03:19 node-1 puppet-user[10213]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct 28 07:03:20 node-1 puppet-user[10213]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 28 07:03:20 node-1 puppet-user[10213]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 28 07:03:20 node-1 puppet-user[10213]: Finished catalog run in 0.03 seconds
Oct 28 07:03:21 node-1 puppet-user[10671]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 28 07:03:21 node-1 puppet-user[10671]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 28 07:03:21 node-1 puppet-user[10671]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 28 07:03:21 node-1 puppet-user[10671]: Finished catalog run in 0.03 seconds
Oct 28 07:03:22 node-1 puppet-user[11113]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 28 07:03:23 node-1 puppet-user[11113]: Compiled catalog for node-1.domain.tld in environment production in 0.18 seconds
Oct 28 07:03:23 node-1 puppet-user[11113]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 28 07:03:25 node-1 puppet-user[11113]: (/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
Oct 28 07:03:25 node-1 puppet-user[11113]: Finished catalog run in 2.41 seconds
Oct 28 07:03:26 node-1 puppet-user[11657]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 28 07:03:27 node-1 puppet-user[11657]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Oct 28 07:03:27 node-1 puppet-user[11657]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 28 07:03:27 node-1 puppet-user[11657]: (/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
Oct 28 07:03:27 node-1 puppet-user[11657]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 28 07:03:27 node-1 puppet-user[11657]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 28 07:03:27 node-1 puppet-user[11657]: Finished catalog run in 0.21 seconds
Oct 28 07:03:28 node-1 kernel: [   68.080016] init: plymouth-upstart-bridge main process ended, respawning
Oct 28 07:03:28 node-1 puppet-agent[8953]: Could not run: SIGTERM
Oct 28 07:03:28 node-1 kernel: [   68.327791] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 28 07:03:28 node-1 ec2: 
Oct 28 07:03:28 node-1 ec2: #############################################################
Oct 28 07:03:28 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 28 07:03:28 node-1 ec2: 1024 b4:51:19:f3:8b:4c:95:51:e2:7f:96:4b:d2:2d:a8:11  root@node-1.domain.tld (DSA)
Oct 28 07:03:28 node-1 ec2: 256 3f:cc:c6:f7:36:be:25:05:cc:b8:c1:0b:b1:c3:c4:7a  root@node-1.domain.tld (ECDSA)
Oct 28 07:03:28 node-1 ec2: 256 51:fa:dd:b5:2a:11:80:d8:cd:97:47:cb:ca:b3:74:4c  root@node-1.domain.tld (ED25519)
Oct 28 07:03:28 node-1 ec2: 2048 7d:a6:d2:4e:23:0e:1e:18:68:74:c2:93:5f:ec:b6:ac  root@node-1.domain.tld (RSA)
Oct 28 07:03:28 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 28 07:03:28 node-1 ec2: #############################################################
Oct 28 07:03:28 node-1 puppet-user[12182]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 28 07:03:29 node-1 puppet-user[12182]: Compiled catalog for node-1.domain.tld in environment production in 0.16 seconds
Oct 28 07:03:29 node-1 puppet-user[12182]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 28 07:03:29 node-1 kernel: [   69.160787] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 28 07:03:29 node-1 kernel: [   69.160836] 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.
Oct 28 07:03:29 node-1 puppet-user[12182]: (/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'
Oct 28 07:03:29 node-1 puppet-user[12182]: Finished catalog run in 0.06 seconds
Oct 28 07:03:30 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 28 07:03:30 node-1 nailgun-agent: D, [2016-10-28T07:03:01.710786 #8936] DEBUG -- : Sleep for 29 seconds before sending request
Oct 28 07:03:30 node-1 nailgun-agent: I, [2016-10-28T07:03:30.724607 #8936]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 28 07:03:30 node-1 puppet-user[12763]: (Scope(Class[main])) MODULAR: sync_time
Oct 28 07:03:30 node-1 puppet-user[12763]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 28 07:03:31 node-1 ntpdate[13287]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 28 07:03:31 node-1 nailgun-agent: D, [2016-10-28T07:03:31.247163 #8936] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct 28 07:03:37 node-1 ntpdate[13287]: adjust time server 10.20.0.2 offset 0.031924 sec
Oct 28 07:03:37 node-1 puppet-user[12763]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 28 07:03:37 node-1 puppet-user[12763]: Finished catalog run in 6.25 seconds
Oct 28 07:03:42 node-1 puppet-user[13501]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 28 07:03:42 node-1 puppet-user[13501]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct 28 07:03:43 node-1 puppet-user[13501]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 28 07:03:43 node-1 puppet-user[13501]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Oct 28 07:03:43 node-1 puppet-user[13501]: Finished catalog run in 0.06 seconds
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.275564 #8936] DEBUG -- : Trying to find block devices
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.275662 #8936] DEBUG -- : Found block device: sda
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.275709 #8936] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.275734 #8936] DEBUG -- : Trying to get list of physical devices
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.275891 #8936] DEBUG -- : Getting udev properties for device: sda
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.277667 #8936] 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
Oct 28 07:03:43 node-1 nailgun-agent: a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"9284", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.277754 #8936] DEBUG -- : Trying to find out if device sda is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.277797 #8936] DEBUG -- : Device sda removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.277813 #8936] DEBUG -- : Device sda seems to be appropriate
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.278244 #8936] DEBUG -- : Getting udev properties for device: dm-0
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.279883 #8936] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-arBAPH1zkE8NGPsDqYVGy5ntP0HIBEG9k5I5yjO3BdTkg2NSj1LszeFP869EHNsN /dev/disk/by-uuid/29d58cbb-06ea-4119-8b53-b8f44dcfa51d /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-arBAPH1zkE8NGPsDqYVGy5ntP0HIBEG9k5I5yjO3BdTkg2NSj1LszeFP869EHNsN", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"29d58cbb-06ea-4119-8b53-b8f44dcfa51d", "ID_FS_UUID_ENC"=>"29d58cbb-06ea-4119-8b53-b8f44dcfa51d", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"11031", "nomdmonddf"=>"1", "nomd
Oct 28 07:03:43 node-1 nailgun-agent: monisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.279910 #8936] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.279966 #8936] DEBUG -- : Device dm-0 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.279981 #8936] DEBUG -- : Device dm-0 seems to be appropriate
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.279996 #8936] DEBUG -- : Getting udev properties for device: dm-1
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.281817 #8936] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-UB8QYiTfBCGkOhHwSR8oc2mxNkFjxHdNYH7Lu9noUJI7Pgza34TjradQVbufYGV7 /dev/disk/by-uuid/9f11ef13-cd86-45ed-a911-234eb475d253 /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-UB8QYiTfBCGkOhHwSR8oc2mxNkFjxHdNYH7Lu9noUJI7Pgza34TjradQVbufYGV7", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9f11ef13-cd86-45ed-a911-234eb475d253", "ID_FS_UUID_ENC"=>"9f11ef13-cd86-45ed-a911-234eb475d253", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49
Oct 28 07:03:43 node-1 nailgun-agent: 751", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.281873 #8936] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.281904 #8936] DEBUG -- : Device dm-1 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.281917 #8936] DEBUG -- : Device dm-1 seems to be appropriate
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.281945 #8936] DEBUG -- : Getting udev properties for device: dm-2
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.283526 #8936] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-CDGsMHCurCIMuHTLd6bQRiYUOcyZAbJK026ejna7p1J5HR0igLDxmby16GyfAHTf /dev/disk/by-uuid/ad87b453-ed88-4776-b1d4-d24e994478fe /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-CDGsMHCurCIMuHTLd6bQRiYUOcyZAbJK026ejna7p1J5HR0igLDxmby16GyfAHTf", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ad87b453-ed88-4776-b1d4-d24e994478fe", "ID_FS_UUID_ENC"=>"ad87b453-ed88-4776-b1d4-d24e994478fe", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49563", "nomdmond
Oct 28 07:03:43 node-1 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.283554 #8936] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.283595 #8936] DEBUG -- : Device dm-2 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.283610 #8936] DEBUG -- : Device dm-2 seems to be appropriate
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.283642 #8936] DEBUG -- : Getting udev properties for device: dm-3
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.285186 #8936] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-lEWjv1aZjEQ0B8ewmukeSebXnbdk7JBIw1KK86BxljFfZ9125mhToQPnXcFmU14h /dev/disk/by-uuid/754bcfae-e522-4abf-80b1-1c39536e7604 /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-lEWjv1aZjEQ0B8ewmukeSebXnbdk7JBIw1KK86BxljFfZ9125mhToQPnXcFmU14h", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"754bcfae-e522-4abf-80b1-1c39536e7604", "ID_FS_UUID_ENC"=>"754bcfae-e522-4abf-80b1-1c39536e7604", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47943", "nomdmonddf"=>"1", 
Oct 28 07:03:43 node-1 nailgun-agent: "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.285238 #8936] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.285279 #8936] DEBUG -- : Device dm-3 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.285292 #8936] DEBUG -- : Device dm-3 seems to be appropriate
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.285307 #8936] DEBUG -- : Getting udev properties for device: dm-4
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.286868 #8936] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-Cq4hyOFdY7QGe0187cURhPFloABBnJTxjFE6hu9hshKcBPetSooz5xhY2g1Mck5t /dev/disk/by-uuid/9086efc0-686a-4dc4-b540-a8a93f78106a /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-Cq4hyOFdY7QGe0187cURhPFloABBnJTxjFE6hu9hshKcBPetSooz5xhY2g1Mck5t", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9086efc0-686a-4dc4-b540-a8a93f78106a", "ID_FS_UUID_ENC"=>"9086efc0-686a-4dc4-b540-a8a93f78106a", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45129", "nomdmonddf"=>"1", "nomd
Oct 28 07:03:43 node-1 nailgun-agent: monisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.286904 #8936] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.286932 #8936] DEBUG -- : Device dm-4 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.286945 #8936] DEBUG -- : Device dm-4 seems to be appropriate
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.286960 #8936] DEBUG -- : Getting udev properties for device: dm-5
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.288977 #8936] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-Cq4hyOFdY7QGe0187cURhPFloABBnJTxECY99apAC3wz5WRHgJpJC0foW2VwXl05 /dev/disk/by-uuid/69e0aeff-a58c-4850-be1b-b42352878cb1 /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-Cq4hyOFdY7QGe0187cURhPFloABBnJTxECY99apAC3wz5WRHgJpJC0foW2VwXl05", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"69e0aeff-a58c-4850-be1b-b42352878cb1", "ID_FS_UUID_ENC"=>"69e0aeff-a58c-4850-be1b-b42352878cb1", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45652", "nomdmonddf"=>"1", "nomdmonisw"
Oct 28 07:03:43 node-1 nailgun-agent: =>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.289004 #8936] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.289047 #8936] DEBUG -- : Device dm-5 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.289062 #8936] DEBUG -- : Device dm-5 seems to be appropriate
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.289109 #8936] DEBUG -- : Getting udev properties for device: ram0
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.290584 #8936] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77981", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.290626 #8936] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.290662 #8936] DEBUG -- : Device ram0 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.290683 #8936] DEBUG -- : Getting udev properties for device: ram1
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.292186 #8936] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77995", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.292211 #8936] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.292250 #8936] DEBUG -- : Device ram1 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.292269 #8936] DEBUG -- : Getting udev properties for device: ram2
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.294022 #8936] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78123", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.294047 #8936] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.294087 #8936] DEBUG -- : Device ram2 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.294107 #8936] DEBUG -- : Getting udev properties for device: ram3
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.295520 #8936] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78137", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.295541 #8936] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.295569 #8936] DEBUG -- : Device ram3 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.295603 #8936] DEBUG -- : Getting udev properties for device: ram4
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.297173 #8936] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78150", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.297197 #8936] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.297232 #8936] DEBUG -- : Device ram4 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.297251 #8936] DEBUG -- : Getting udev properties for device: ram5
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.298673 #8936] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78163", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.298728 #8936] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.298760 #8936] DEBUG -- : Device ram5 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.298779 #8936] DEBUG -- : Getting udev properties for device: ram6
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.300398 #8936] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78175", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.300430 #8936] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.300474 #8936] DEBUG -- : Device ram6 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.300501 #8936] DEBUG -- : Getting udev properties for device: ram7
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.302129 #8936] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78186", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.302169 #8936] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.302206 #8936] DEBUG -- : Device ram7 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.302226 #8936] DEBUG -- : Getting udev properties for device: ram8
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.303610 #8936] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78199", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.303630 #8936] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.303672 #8936] DEBUG -- : Device ram8 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.303690 #8936] DEBUG -- : Getting udev properties for device: ram9
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.305309 #8936] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78211", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.305365 #8936] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.305417 #8936] DEBUG -- : Device ram9 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.305450 #8936] DEBUG -- : Getting udev properties for device: loop0
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.306819 #8936] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77845", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.306862 #8936] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.306894 #8936] DEBUG -- : Device loop0 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.306911 #8936] DEBUG -- : Getting udev properties for device: loop1
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.308352 #8936] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77866", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.308377 #8936] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.308410 #8936] DEBUG -- : Device loop1 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.308428 #8936] DEBUG -- : Getting udev properties for device: loop2
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.310004 #8936] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77882", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.310061 #8936] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.310096 #8936] DEBUG -- : Device loop2 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.310116 #8936] DEBUG -- : Getting udev properties for device: loop3
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.311453 #8936] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77899", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.311475 #8936] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.311504 #8936] DEBUG -- : Device loop3 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.311536 #8936] DEBUG -- : Getting udev properties for device: loop4
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.313158 #8936] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77915", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.313185 #8936] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.313249 #8936] DEBUG -- : Device loop4 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.313268 #8936] DEBUG -- : Getting udev properties for device: loop5
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.314606 #8936] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77931", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.314633 #8936] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.314663 #8936] DEBUG -- : Device loop5 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.314694 #8936] DEBUG -- : Getting udev properties for device: loop6
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.316544 #8936] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77945", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.316597 #8936] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.316668 #8936] DEBUG -- : Device loop6 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.316695 #8936] DEBUG -- : Getting udev properties for device: loop7
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.318506 #8936] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77966", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.318547 #8936] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.318597 #8936] DEBUG -- : Device loop7 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.318620 #8936] DEBUG -- : Getting udev properties for device: ram10
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.320645 #8936] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78014", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.320674 #8936] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.320723 #8936] DEBUG -- : Device ram10 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.320746 #8936] DEBUG -- : Getting udev properties for device: ram11
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.322402 #8936] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78033", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.322431 #8936] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.322468 #8936] DEBUG -- : Device ram11 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.322513 #8936] DEBUG -- : Getting udev properties for device: ram12
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.324277 #8936] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78051", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.324318 #8936] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.324367 #8936] DEBUG -- : Device ram12 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.324398 #8936] DEBUG -- : Getting udev properties for device: ram13
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.326292 #8936] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78068", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.326336 #8936] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.326376 #8936] DEBUG -- : Device ram13 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.326399 #8936] DEBUG -- : Getting udev properties for device: ram14
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.328305 #8936] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78083", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.328335 #8936] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.328394 #8936] DEBUG -- : Device ram14 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.328418 #8936] DEBUG -- : Getting udev properties for device: ram15
Oct 28 07:03:43 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.330292 #8936] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78104", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.330324 #8936] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.330384 #8936] DEBUG -- : Device ram15 removable parameter: "0"
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.330422 #8936] 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"}]
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.330457 #8936] DEBUG -- : Block device seems to be physical data storage: sda
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.330493 #8936] DEBUG -- : Found block device: dm-0
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.330530 #8936] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.330543 #8936] DEBUG -- : Found block device: dm-1
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.330554 #8936] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.330573 #8936] DEBUG -- : Found block device: dm-2
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.330584 #8936] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.330605 #8936] DEBUG -- : Found block device: dm-3
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.330632 #8936] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.330641 #8936] DEBUG -- : Found block device: dm-4
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.330664 #8936] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.335896 #8936] DEBUG -- : Found block device: dm-5
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.335922 #8936] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.335935 #8936] DEBUG -- : Found block device: ram0
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.335945 #8936] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.335953 #8936] DEBUG -- : Found block device: ram1
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.335963 #8936] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.335971 #8936] DEBUG -- : Found block device: ram2
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.335980 #8936] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.335988 #8936] DEBUG -- : Found block device: ram3
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336052 #8936] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336061 #8936] DEBUG -- : Found block device: ram4
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336070 #8936] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336078 #8936] DEBUG -- : Found block device: ram5
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336089 #8936] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336097 #8936] DEBUG -- : Found block device: ram6
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336106 #8936] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336114 #8936] DEBUG -- : Found block device: ram7
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336163 #8936] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336172 #8936] DEBUG -- : Found block device: ram8
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336182 #8936] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336190 #8936] DEBUG -- : Found block device: ram9
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336199 #8936] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336206 #8936] DEBUG -- : Found block device: loop0
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336216 #8936] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336224 #8936] DEBUG -- : Found block device: loop1
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336234 #8936] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336291 #8936] DEBUG -- : Found block device: loop2
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336301 #8936] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336310 #8936] DEBUG -- : Found block device: loop3
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336320 #8936] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336328 #8936] DEBUG -- : Found block device: loop4
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336337 #8936] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336345 #8936] DEBUG -- : Found block device: loop5
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336353 #8936] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336407 #8936] DEBUG -- : Found block device: loop6
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336417 #8936] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336424 #8936] DEBUG -- : Found block device: loop7
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336432 #8936] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336440 #8936] DEBUG -- : Found block device: ram10
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336450 #8936] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336457 #8936] DEBUG -- : Found block device: ram11
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336466 #8936] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336474 #8936] DEBUG -- : Found block device: ram12
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336514 #8936] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336522 #8936] DEBUG -- : Found block device: ram13
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336531 #8936] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336538 #8936] DEBUG -- : Found block device: ram14
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336548 #8936] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336556 #8936] DEBUG -- : Found block device: ram15
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336566 #8936] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.336594 #8936] 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}]
Oct 28 07:03:43 node-1 nailgun-agent: D, [2016-10-28T07:03:43.487698 #8936] DEBUG -- : Response: status: 200 body: {"id": 1}
Oct 28 07:03:43 node-1 nailgun-agent: I, [2016-10-28T07:03:43.487897 #8936]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct 28 07:03:44 node-1 puppet-user[14121]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 28 07:03:44 node-1 puppet-user[14121]: Compiled catalog for node-1.domain.tld in environment production in 0.51 seconds
Oct 28 07:03:45 node-1 puppet-user[14121]: (/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
Oct 28 07:03:45 node-1 puppet-user[14121]: (/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
Oct 28 07:03:45 node-1 puppet-user[14121]: (/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
Oct 28 07:03:45 node-1 puppet-user[14121]: (/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
Oct 28 07:03:45 node-1 puppet-user[14121]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct 28 07:03:45 node-1 puppet-user[14121]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Oct 28 07:03:45 node-1 puppet-user[14121]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct 28 07:03:45 node-1 puppet-user[14121]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Oct 28 07:03:45 node-1 puppet-user[14121]: (/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
Oct 28 07:03:45 node-1 puppet-user[14121]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Oct 28 07:03:45 node-1 puppet-user[14121]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 28 07:03:45 node-1 puppet-user[14121]: Finished catalog run in 0.77 seconds
Oct 28 07:03:47 node-1 puppet-user[14632]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 28 07:03:47 node-1 puppet-user[14632]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Oct 28 07:03:50 node-1 puppet-user[14632]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 28 07:04:01 node-1 CRON[16131]: (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")
Oct 28 07:04:17 node-1 puppet-user[14632]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 28 07:04:17 node-1 puppet-user[14632]: Finished catalog run in 29.73 seconds
Oct 28 07:04:19 node-1 puppet-user[17029]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 28 07:04:19 node-1 puppet-user[17029]: Compiled catalog for node-1.domain.tld in environment production in 0.57 seconds
Oct 28 07:04:19 node-1 puppet-user[17029]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 28 07:04:19 node-1 puppet-user[17029]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 28 07:04:19 node-1 puppet-user[17029]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 28 07:04:19 node-1 puppet-user[17029]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 28 07:04:19 node-1 puppet-user[17029]: Finished catalog run in 0.09 seconds
Oct 28 07:04:21 node-1 puppet-user[17483]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 28 07:04:22 node-1 puppet-user[17483]: Compiled catalog for node-1.domain.tld in environment production in 0.94 seconds
Oct 28 07:04:22 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 28 07:04:22 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 28 07:04:22 node-1 crontab[17922]: (root) LIST (root)
Oct 28 07:04:22 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 28 07:04:22 node-1 crontab[17925]: (root) REPLACE (root)
Oct 28 07:04:24 node-1 puppet-user[17483]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/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
Oct 28 07:04:25 node-1 puppet-user[17483]: (/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
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/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
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/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
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/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
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/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
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 28 07:04:25 node-1 puppet-user[17483]: (/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
Oct 28 07:04:25 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 28 07:04:26 node-1 puppet-user[17483]: (/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
Oct 28 07:04:26 node-1 puppet-user[17483]: (/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
Oct 28 07:04:26 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 28 07:04:26 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 28 07:04:26 node-1 puppet-user[17483]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Oct 28 07:04:26 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8392" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 07:04:26 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 28 07:04:27 node-1 multipathd: uevent trigger error
<27>Oct 28 07:04:27 node-1 multipathd: uevent trigger error
<27>Oct 28 07:04:27 node-1 multipathd: uevent trigger error
<27>Oct 28 07:04:27 node-1 multipathd: uevent trigger error
<27>Oct 28 07:04:27 node-1 multipathd: uevent trigger error
<27>Oct 28 07:04:40 node-1 multipathd: uevent trigger error
<27>Oct 28 07:04:40 node-1 multipathd: uevent trigger error
<27>Oct 28 07:04:40 node-1 multipathd: uevent trigger error
<27>Oct 28 07:04:40 node-1 multipathd: uevent trigger error
<27>Oct 28 07:04:40 node-1 multipathd: uevent trigger error
<27>Oct 28 07:04:40 node-1 multipathd: uevent trigger error
<27>Oct 28 07:05:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:05:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:05:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:05:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:05:30 node-1 multipathd: uevent trigger error
<27>Oct 28 07:05:32 node-1 multipathd: uevent trigger error
<27>Oct 28 07:05:32 node-1 multipathd: uevent trigger error
<27>Oct 28 07:05:32 node-1 multipathd: uevent trigger error
<27>Oct 28 07:05:32 node-1 multipathd: uevent trigger error
<27>Oct 28 07:06:12 node-1 ntpdate[1456]: no servers can be used, exiting
<27>Oct 28 07:06:12 node-1 ntpdate[1666]: no servers can be used, exiting
<27>Oct 28 07:06:44 node-1 multipathd: uevent trigger error
<27>Oct 28 07:06:44 node-1 multipathd: uevent trigger error
<27>Oct 28 07:06:44 node-1 multipathd: uevent trigger error
<27>Oct 28 07:06:44 node-1 multipathd: uevent trigger error
<27>Oct 28 07:06:44 node-1 multipathd: uevent trigger error
<27>Oct 28 07:06:47 node-1 multipathd: uevent trigger error
<27>Oct 28 07:06:47 node-1 multipathd: uevent trigger error
<27>Oct 28 07:06:47 node-1 multipathd: uevent trigger error
<27>Oct 28 07:06:47 node-1 multipathd: uevent trigger error
<27>Oct 28 07:06:47 node-1 multipathd: uevent trigger error
<27>Oct 28 07:06:58 node-1 multipathd: uevent trigger error
<27>Oct 28 07:06:58 node-1 multipathd: uevent trigger error
<27>Oct 28 07:06:58 node-1 multipathd: uevent trigger error
<27>Oct 28 07:06:58 node-1 multipathd: uevent trigger error
<27>Oct 28 07:06:58 node-1 multipathd: uevent trigger error
<27>Oct 28 07:07:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:07:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:07:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:07:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:07:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:07:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:07:54 node-1 multipathd: uevent trigger error
<27>Oct 28 07:07:54 node-1 multipathd: uevent trigger error
<27>Oct 28 07:07:54 node-1 multipathd: uevent trigger error
<27>Oct 28 07:07:54 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:03 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:03 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:03 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:03 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:03 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:05 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 07:08:05 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 07:08:11 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 07:08:12 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 07:08:17 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 07:08:22 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 07:08:23 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 07:08:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:32 node-1 ntpdate[19527]: the NTP socket is in use, exiting
<27>Oct 28 07:08:32 node-1 ntpdate[19579]: the NTP socket is in use, exiting
<27>Oct 28 07:08:42 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:42 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:42 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:42 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:42 node-1 multipathd: uevent trigger error
<129>Oct 28 07:08:45 node-1 haproxy[21791]: 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>Oct 28 07:08:45 node-1 haproxy[21791]: 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>Oct 28 07:08:46 node-1 haproxy[21795]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:08:46 node-1 haproxy[21795]: proxy mysqld has no server available!
<27>Oct 28 07:08:48 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:48 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:48 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:48 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:48 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:51 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:51 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:51 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:51 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:51 node-1 multipathd: uevent trigger error
<129>Oct 28 07:08:54 node-1 haproxy[24397]: 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>Oct 28 07:08:54 node-1 haproxy[24397]: 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>Oct 28 07:08:55 node-1 haproxy[24401]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:08:55 node-1 haproxy[24401]: proxy mysqld has no server available!
<129>Oct 28 07:08:55 node-1 haproxy[24401]: 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>Oct 28 07:08:55 node-1 haproxy[24401]: 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>Oct 28 07:08:56 node-1 haproxy[24401]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:08:56 node-1 haproxy[24401]: proxy object-storage has no server available!
<27>Oct 28 07:08:57 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:57 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:57 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:57 node-1 multipathd: uevent trigger error
<27>Oct 28 07:08:57 node-1 multipathd: uevent trigger error
<129>Oct 28 07:08:59 node-1 haproxy[25760]: 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>Oct 28 07:09:00 node-1 haproxy[25764]: 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>Oct 28 07:09:00 node-1 haproxy[25764]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:00 node-1 haproxy[25764]: proxy neutron has no server available!
<129>Oct 28 07:09:00 node-1 haproxy[25764]: 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>Oct 28 07:09:00 node-1 haproxy[25764]: 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>Oct 28 07:09:00 node-1 haproxy[25764]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:00 node-1 haproxy[25764]: proxy mysqld has no server available!
<129>Oct 28 07:09:01 node-1 haproxy[25764]: 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>Oct 28 07:09:01 node-1 haproxy[25764]: 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>Oct 28 07:09:01 node-1 haproxy[25764]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:01 node-1 haproxy[25764]: proxy object-storage has no server available!
<27>Oct 28 07:09:02 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:02 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:02 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:02 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:02 node-1 multipathd: uevent trigger error
<129>Oct 28 07:09:05 node-1 haproxy[27269]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:05 node-1 haproxy[27269]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:05 node-1 haproxy[27269]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:05 node-1 haproxy[27269]: proxy keystone-1 has no server available!
<129>Oct 28 07:09:05 node-1 haproxy[27269]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:05 node-1 haproxy[27269]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:06 node-1 haproxy[27273]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:06 node-1 haproxy[27273]: proxy keystone-2 has no server available!
<129>Oct 28 07:09:06 node-1 haproxy[27273]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:06 node-1 haproxy[27273]: 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>Oct 28 07:09:06 node-1 haproxy[27273]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:06 node-1 haproxy[27273]: proxy neutron has no server available!
<129>Oct 28 07:09:06 node-1 haproxy[27273]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:06 node-1 haproxy[27273]: 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>Oct 28 07:09:06 node-1 haproxy[27273]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:06 node-1 haproxy[27273]: proxy mysqld has no server available!
<129>Oct 28 07:09:06 node-1 haproxy[27273]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:07 node-1 haproxy[27273]: 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>Oct 28 07:09:07 node-1 haproxy[27273]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:07 node-1 haproxy[27273]: proxy object-storage has no server available!
<27>Oct 28 07:09:08 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:08 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:08 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:08 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:08 node-1 multipathd: uevent trigger error
<129>Oct 28 07:09:10 node-1 haproxy[28592]: 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>Oct 28 07:09:10 node-1 haproxy[28592]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:10 node-1 haproxy[28592]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:10 node-1 haproxy[28592]: proxy keystone-1 has no server available!
<129>Oct 28 07:09:10 node-1 haproxy[28592]: 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>Oct 28 07:09:11 node-1 haproxy[28600]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:11 node-1 haproxy[28600]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:11 node-1 haproxy[28600]: proxy keystone-2 has no server available!
<129>Oct 28 07:09:11 node-1 haproxy[28600]: 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>Oct 28 07:09:11 node-1 haproxy[28600]: 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>Oct 28 07:09:11 node-1 haproxy[28600]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:11 node-1 haproxy[28600]: proxy neutron has no server available!
<129>Oct 28 07:09:11 node-1 haproxy[28600]: 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>Oct 28 07:09:11 node-1 haproxy[28600]: 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>Oct 28 07:09:11 node-1 haproxy[28600]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:11 node-1 haproxy[28600]: proxy mysqld has no server available!
<129>Oct 28 07:09:11 node-1 haproxy[28600]: 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>Oct 28 07:09:12 node-1 haproxy[28600]: 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>Oct 28 07:09:12 node-1 haproxy[28600]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:12 node-1 haproxy[28600]: proxy object-storage has no server available!
<129>Oct 28 07:09:12 node-1 haproxy[28600]: 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>Oct 28 07:09:12 node-1 haproxy[28600]: 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>Oct 28 07:09:12 node-1 haproxy[28600]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:12 node-1 haproxy[28600]: proxy aodh has no server available!
<27>Oct 28 07:09:13 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:13 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:13 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:13 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:13 node-1 multipathd: uevent trigger error
<129>Oct 28 07:09:15 node-1 haproxy[30108]: 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>Oct 28 07:09:16 node-1 haproxy[30112]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:16 node-1 haproxy[30112]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:16 node-1 haproxy[30112]: proxy keystone-1 has no server available!
<129>Oct 28 07:09:16 node-1 haproxy[30112]: 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>Oct 28 07:09:16 node-1 haproxy[30112]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:16 node-1 haproxy[30112]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:16 node-1 haproxy[30112]: proxy keystone-2 has no server available!
<129>Oct 28 07:09:16 node-1 haproxy[30112]: 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>Oct 28 07:09:16 node-1 haproxy[30112]: 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>Oct 28 07:09:16 node-1 haproxy[30112]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:16 node-1 haproxy[30112]: proxy neutron has no server available!
<129>Oct 28 07:09:16 node-1 haproxy[30112]: 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>Oct 28 07:09:16 node-1 haproxy[30112]: 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>Oct 28 07:09:16 node-1 haproxy[30112]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:16 node-1 haproxy[30112]: proxy mysqld has no server available!
<129>Oct 28 07:09:17 node-1 haproxy[30112]: 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>Oct 28 07:09:17 node-1 haproxy[30112]: 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>Oct 28 07:09:17 node-1 haproxy[30112]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:17 node-1 haproxy[30112]: proxy object-storage has no server available!
<129>Oct 28 07:09:17 node-1 haproxy[30112]: 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>Oct 28 07:09:17 node-1 haproxy[30112]: 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>Oct 28 07:09:17 node-1 haproxy[30112]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:17 node-1 haproxy[30112]: proxy aodh has no server available!
<129>Oct 28 07:09:17 node-1 haproxy[30112]: 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>Oct 28 07:09:17 node-1 haproxy[30112]: 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>Oct 28 07:09:17 node-1 haproxy[30112]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:17 node-1 haproxy[30112]: proxy ceilometer has no server available!
<27>Oct 28 07:09:19 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:19 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:19 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:19 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:19 node-1 multipathd: uevent trigger error
<129>Oct 28 07:09:21 node-1 haproxy[31448]: 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>Oct 28 07:09:21 node-1 haproxy[31448]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:21 node-1 haproxy[31448]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:21 node-1 haproxy[31448]: proxy keystone-1 has no server available!
<129>Oct 28 07:09:21 node-1 haproxy[31448]: 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>Oct 28 07:09:21 node-1 haproxy[31448]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:21 node-1 haproxy[31448]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:21 node-1 haproxy[31448]: proxy keystone-2 has no server available!
<129>Oct 28 07:09:21 node-1 haproxy[31448]: 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>Oct 28 07:09:22 node-1 haproxy[31455]: 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>Oct 28 07:09:22 node-1 haproxy[31455]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:22 node-1 haproxy[31455]: proxy neutron has no server available!
<129>Oct 28 07:09:22 node-1 haproxy[31455]: 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>Oct 28 07:09:22 node-1 haproxy[31455]: 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>Oct 28 07:09:22 node-1 haproxy[31455]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:22 node-1 haproxy[31455]: proxy mysqld has no server available!
<129>Oct 28 07:09:22 node-1 haproxy[31455]: 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>Oct 28 07:09:22 node-1 haproxy[31455]: 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>Oct 28 07:09:22 node-1 haproxy[31455]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:22 node-1 haproxy[31455]: proxy object-storage has no server available!
<129>Oct 28 07:09:22 node-1 haproxy[31455]: 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>Oct 28 07:09:22 node-1 haproxy[31455]: 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>Oct 28 07:09:23 node-1 haproxy[31455]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:23 node-1 haproxy[31455]: proxy aodh has no server available!
<129>Oct 28 07:09:23 node-1 haproxy[31455]: 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>Oct 28 07:09:23 node-1 haproxy[31455]: 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>Oct 28 07:09:23 node-1 haproxy[31455]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:23 node-1 haproxy[31455]: proxy ceilometer has no server available!
<27>Oct 28 07:09:24 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:24 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:24 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:24 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:24 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:24 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:24 node-1 multipathd: uevent trigger error
<129>Oct 28 07:09:26 node-1 haproxy[336]: 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>Oct 28 07:09:27 node-1 haproxy[340]: 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>Oct 28 07:09:27 node-1 haproxy[340]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:27 node-1 haproxy[340]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:27 node-1 haproxy[340]: proxy keystone-1 has no server available!
<129>Oct 28 07:09:27 node-1 haproxy[340]: 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>Oct 28 07:09:27 node-1 haproxy[340]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:27 node-1 haproxy[340]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:27 node-1 haproxy[340]: proxy keystone-2 has no server available!
<129>Oct 28 07:09:27 node-1 haproxy[340]: 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>Oct 28 07:09:27 node-1 haproxy[340]: 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>Oct 28 07:09:27 node-1 haproxy[340]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:27 node-1 haproxy[340]: proxy neutron has no server available!
<129>Oct 28 07:09:27 node-1 haproxy[340]: 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>Oct 28 07:09:27 node-1 haproxy[340]: 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>Oct 28 07:09:27 node-1 haproxy[340]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:27 node-1 haproxy[340]: proxy mysqld has no server available!
<129>Oct 28 07:09:28 node-1 haproxy[340]: 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>Oct 28 07:09:28 node-1 haproxy[340]: 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>Oct 28 07:09:28 node-1 haproxy[340]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:28 node-1 haproxy[340]: proxy object-storage has no server available!
<129>Oct 28 07:09:28 node-1 haproxy[340]: 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>Oct 28 07:09:28 node-1 haproxy[340]: 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>Oct 28 07:09:28 node-1 haproxy[340]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:28 node-1 haproxy[340]: proxy aodh has no server available!
<129>Oct 28 07:09:28 node-1 haproxy[340]: 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>Oct 28 07:09:28 node-1 haproxy[340]: 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>Oct 28 07:09:28 node-1 haproxy[340]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:28 node-1 haproxy[340]: proxy ceilometer has no server available!
<27>Oct 28 07:09:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:29 node-1 multipathd: uevent trigger error
<129>Oct 28 07:09:32 node-1 haproxy[1747]: 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>Oct 28 07:09:32 node-1 haproxy[1747]: 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>Oct 28 07:09:32 node-1 haproxy[1747]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:32 node-1 haproxy[1747]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:32 node-1 haproxy[1747]: proxy keystone-1 has no server available!
<129>Oct 28 07:09:32 node-1 haproxy[1747]: 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>Oct 28 07:09:33 node-1 haproxy[1751]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:33 node-1 haproxy[1751]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:33 node-1 haproxy[1751]: proxy keystone-2 has no server available!
<129>Oct 28 07:09:33 node-1 haproxy[1751]: 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>Oct 28 07:09:33 node-1 haproxy[1751]: 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>Oct 28 07:09:33 node-1 haproxy[1751]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:33 node-1 haproxy[1751]: proxy glance-api has no server available!
<129>Oct 28 07:09:33 node-1 haproxy[1751]: 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>Oct 28 07:09:33 node-1 haproxy[1751]: 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>Oct 28 07:09:33 node-1 haproxy[1751]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:33 node-1 haproxy[1751]: proxy glance-glare has no server available!
<129>Oct 28 07:09:33 node-1 haproxy[1751]: 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>Oct 28 07:09:33 node-1 haproxy[1751]: 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>Oct 28 07:09:33 node-1 haproxy[1751]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:33 node-1 haproxy[1751]: proxy neutron has no server available!
<129>Oct 28 07:09:33 node-1 haproxy[1751]: 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>Oct 28 07:09:33 node-1 haproxy[1751]: 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>Oct 28 07:09:33 node-1 haproxy[1751]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:33 node-1 haproxy[1751]: proxy glance-registry has no server available!
<129>Oct 28 07:09:33 node-1 haproxy[1751]: 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>Oct 28 07:09:33 node-1 haproxy[1751]: 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>Oct 28 07:09:33 node-1 haproxy[1751]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:33 node-1 haproxy[1751]: proxy mysqld has no server available!
<129>Oct 28 07:09:34 node-1 haproxy[1751]: 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>Oct 28 07:09:34 node-1 haproxy[1751]: 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>Oct 28 07:09:34 node-1 haproxy[1751]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:34 node-1 haproxy[1751]: proxy object-storage has no server available!
<129>Oct 28 07:09:34 node-1 haproxy[1751]: 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>Oct 28 07:09:34 node-1 haproxy[1751]: 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>Oct 28 07:09:34 node-1 haproxy[1751]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:34 node-1 haproxy[1751]: proxy aodh has no server available!
<129>Oct 28 07:09:34 node-1 haproxy[1751]: 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>Oct 28 07:09:34 node-1 haproxy[1751]: 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>Oct 28 07:09:34 node-1 haproxy[1751]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:34 node-1 haproxy[1751]: proxy ceilometer has no server available!
<27>Oct 28 07:09:35 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:35 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:35 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:35 node-1 multipathd: uevent trigger error
<129>Oct 28 07:09:38 node-1 haproxy[3134]: 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>Oct 28 07:09:38 node-1 haproxy[3134]: 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>Oct 28 07:09:38 node-1 haproxy[3134]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:38 node-1 haproxy[3134]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:38 node-1 haproxy[3134]: proxy keystone-1 has no server available!
<129>Oct 28 07:09:38 node-1 haproxy[3134]: 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>Oct 28 07:09:38 node-1 haproxy[3134]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:38 node-1 haproxy[3134]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:38 node-1 haproxy[3134]: proxy keystone-2 has no server available!
<129>Oct 28 07:09:38 node-1 haproxy[3134]: 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>Oct 28 07:09:38 node-1 haproxy[3134]: 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>Oct 28 07:09:38 node-1 haproxy[3134]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:38 node-1 haproxy[3134]: proxy nova-api has no server available!
<129>Oct 28 07:09:38 node-1 haproxy[3134]: 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>Oct 28 07:09:38 node-1 haproxy[3134]: 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>Oct 28 07:09:38 node-1 haproxy[3134]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:38 node-1 haproxy[3134]: proxy nova-metadata-api has no server available!
<129>Oct 28 07:09:38 node-1 haproxy[3134]: 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>Oct 28 07:09:38 node-1 haproxy[3134]: 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>Oct 28 07:09:38 node-1 haproxy[3134]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:38 node-1 haproxy[3134]: proxy glance-api has no server available!
<129>Oct 28 07:09:39 node-1 haproxy[3140]: 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>Oct 28 07:09:39 node-1 haproxy[3140]: 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>Oct 28 07:09:39 node-1 haproxy[3140]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:39 node-1 haproxy[3140]: proxy glance-glare has no server available!
<129>Oct 28 07:09:39 node-1 haproxy[3140]: 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>Oct 28 07:09:39 node-1 haproxy[3140]: 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>Oct 28 07:09:39 node-1 haproxy[3140]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:39 node-1 haproxy[3140]: proxy neutron has no server available!
<129>Oct 28 07:09:39 node-1 haproxy[3140]: 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>Oct 28 07:09:39 node-1 haproxy[3140]: 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>Oct 28 07:09:39 node-1 haproxy[3140]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:39 node-1 haproxy[3140]: proxy glance-registry has no server available!
<129>Oct 28 07:09:39 node-1 haproxy[3140]: 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>Oct 28 07:09:39 node-1 haproxy[3140]: 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>Oct 28 07:09:39 node-1 haproxy[3140]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:39 node-1 haproxy[3140]: proxy mysqld has no server available!
<129>Oct 28 07:09:39 node-1 haproxy[3140]: 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>Oct 28 07:09:39 node-1 haproxy[3140]: 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>Oct 28 07:09:39 node-1 haproxy[3140]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:39 node-1 haproxy[3140]: proxy object-storage has no server available!
<129>Oct 28 07:09:39 node-1 haproxy[3140]: 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>Oct 28 07:09:39 node-1 haproxy[3140]: 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>Oct 28 07:09:39 node-1 haproxy[3140]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:39 node-1 haproxy[3140]: proxy aodh has no server available!
<129>Oct 28 07:09:39 node-1 haproxy[3140]: 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>Oct 28 07:09:39 node-1 haproxy[3140]: 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>Oct 28 07:09:39 node-1 haproxy[3140]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:39 node-1 haproxy[3140]: proxy ceilometer has no server available!
<129>Oct 28 07:09:40 node-1 haproxy[3140]: 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>Oct 28 07:09:40 node-1 haproxy[3140]: 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>Oct 28 07:09:40 node-1 haproxy[3140]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:40 node-1 haproxy[3140]: proxy nova-novncproxy has no server available!
<27>Oct 28 07:09:41 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:41 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:41 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:41 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:41 node-1 multipathd: uevent trigger error
<129>Oct 28 07:09:43 node-1 haproxy[4466]: 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>Oct 28 07:09:43 node-1 haproxy[4466]: 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>Oct 28 07:09:43 node-1 haproxy[4466]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:43 node-1 haproxy[4466]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:43 node-1 haproxy[4466]: proxy keystone-1 has no server available!
<129>Oct 28 07:09:43 node-1 haproxy[4466]: 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>Oct 28 07:09:43 node-1 haproxy[4466]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:43 node-1 haproxy[4466]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:43 node-1 haproxy[4466]: proxy keystone-2 has no server available!
<129>Oct 28 07:09:43 node-1 haproxy[4466]: 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>Oct 28 07:09:43 node-1 haproxy[4466]: 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>Oct 28 07:09:44 node-1 haproxy[4470]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:44 node-1 haproxy[4470]: proxy nova-api has no server available!
<129>Oct 28 07:09:44 node-1 haproxy[4470]: 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>Oct 28 07:09:44 node-1 haproxy[4470]: 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>Oct 28 07:09:44 node-1 haproxy[4470]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:44 node-1 haproxy[4470]: proxy nova-metadata-api has no server available!
<129>Oct 28 07:09:44 node-1 haproxy[4470]: 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>Oct 28 07:09:44 node-1 haproxy[4470]: 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>Oct 28 07:09:44 node-1 haproxy[4470]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:44 node-1 haproxy[4470]: proxy cinder-api has no server available!
<129>Oct 28 07:09:44 node-1 haproxy[4470]: 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>Oct 28 07:09:44 node-1 haproxy[4470]: 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>Oct 28 07:09:44 node-1 haproxy[4470]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:44 node-1 haproxy[4470]: proxy glance-api has no server available!
<129>Oct 28 07:09:44 node-1 haproxy[4470]: 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>Oct 28 07:09:44 node-1 haproxy[4470]: 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>Oct 28 07:09:44 node-1 haproxy[4470]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:44 node-1 haproxy[4470]: proxy glance-glare has no server available!
<129>Oct 28 07:09:44 node-1 haproxy[4470]: 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>Oct 28 07:09:44 node-1 haproxy[4470]: 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>Oct 28 07:09:44 node-1 haproxy[4470]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:44 node-1 haproxy[4470]: proxy neutron has no server available!
<129>Oct 28 07:09:44 node-1 haproxy[4470]: 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>Oct 28 07:09:44 node-1 haproxy[4470]: 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>Oct 28 07:09:44 node-1 haproxy[4470]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:44 node-1 haproxy[4470]: proxy glance-registry has no server available!
<129>Oct 28 07:09:44 node-1 haproxy[4470]: 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>Oct 28 07:09:44 node-1 haproxy[4470]: 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>Oct 28 07:09:44 node-1 haproxy[4470]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:44 node-1 haproxy[4470]: proxy mysqld has no server available!
<129>Oct 28 07:09:45 node-1 haproxy[4470]: 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>Oct 28 07:09:45 node-1 haproxy[4470]: 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>Oct 28 07:09:45 node-1 haproxy[4470]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:45 node-1 haproxy[4470]: proxy object-storage has no server available!
<129>Oct 28 07:09:45 node-1 haproxy[4470]: 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>Oct 28 07:09:45 node-1 haproxy[4470]: 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>Oct 28 07:09:45 node-1 haproxy[4470]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:45 node-1 haproxy[4470]: proxy aodh has no server available!
<129>Oct 28 07:09:45 node-1 haproxy[4470]: 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>Oct 28 07:09:45 node-1 haproxy[4470]: 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>Oct 28 07:09:45 node-1 haproxy[4470]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:45 node-1 haproxy[4470]: proxy ceilometer has no server available!
<129>Oct 28 07:09:45 node-1 haproxy[4470]: 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>Oct 28 07:09:45 node-1 haproxy[4470]: 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>Oct 28 07:09:45 node-1 haproxy[4470]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:45 node-1 haproxy[4470]: proxy nova-novncproxy has no server available!
<27>Oct 28 07:09:46 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:46 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:46 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:46 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:46 node-1 multipathd: uevent trigger error
<129>Oct 28 07:09:49 node-1 haproxy[5854]: 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>Oct 28 07:09:49 node-1 haproxy[5854]: 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>Oct 28 07:09:49 node-1 haproxy[5854]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:49 node-1 haproxy[5854]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:49 node-1 haproxy[5854]: proxy keystone-1 has no server available!
<129>Oct 28 07:09:49 node-1 haproxy[5854]: 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>Oct 28 07:09:49 node-1 haproxy[5854]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:09:49 node-1 haproxy[5854]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:49 node-1 haproxy[5854]: proxy keystone-2 has no server available!
<129>Oct 28 07:09:49 node-1 haproxy[5854]: 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>Oct 28 07:09:49 node-1 haproxy[5854]: 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>Oct 28 07:09:49 node-1 haproxy[5854]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:49 node-1 haproxy[5854]: proxy nova-api has no server available!
<129>Oct 28 07:09:49 node-1 haproxy[5854]: 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>Oct 28 07:09:49 node-1 haproxy[5854]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:50 node-1 haproxy[5861]: proxy nova-metadata-api has no server available!
<129>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:50 node-1 haproxy[5861]: proxy cinder-api has no server available!
<129>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:50 node-1 haproxy[5861]: proxy glance-api has no server available!
<129>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:50 node-1 haproxy[5861]: proxy glance-glare has no server available!
<129>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:50 node-1 haproxy[5861]: proxy neutron has no server available!
<129>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:50 node-1 haproxy[5861]: proxy glance-registry has no server available!
<129>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:50 node-1 haproxy[5861]: proxy mysqld has no server available!
<129>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:50 node-1 haproxy[5861]: proxy object-storage has no server available!
<129>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:50 node-1 haproxy[5861]: proxy aodh has no server available!
<129>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:50 node-1 haproxy[5861]: 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>Oct 28 07:09:51 node-1 haproxy[5861]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:51 node-1 haproxy[5861]: proxy ceilometer has no server available!
<129>Oct 28 07:09:51 node-1 haproxy[5861]: 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>Oct 28 07:09:51 node-1 haproxy[5861]: 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>Oct 28 07:09:51 node-1 haproxy[5861]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:51 node-1 haproxy[5861]: proxy heat-api has no server available!
<129>Oct 28 07:09:51 node-1 haproxy[5861]: 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>Oct 28 07:09:51 node-1 haproxy[5861]: 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>Oct 28 07:09:51 node-1 haproxy[5861]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:51 node-1 haproxy[5861]: proxy heat-api-cfn has no server available!
<129>Oct 28 07:09:51 node-1 haproxy[5861]: 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>Oct 28 07:09:51 node-1 haproxy[5861]: 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>Oct 28 07:09:51 node-1 haproxy[5861]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:51 node-1 haproxy[5861]: proxy heat-api-cloudwatch has no server available!
<129>Oct 28 07:09:51 node-1 haproxy[5861]: 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>Oct 28 07:09:51 node-1 haproxy[5861]: 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>Oct 28 07:09:51 node-1 haproxy[5861]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 07:09:51 node-1 haproxy[5861]: proxy nova-novncproxy has no server available!
<27>Oct 28 07:09:52 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:52 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:52 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:52 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:52 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:55 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:55 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:55 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:55 node-1 multipathd: uevent trigger error
<27>Oct 28 07:09:55 node-1 multipathd: uevent trigger error
<27>Oct 28 07:10:02 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 28 07:10:27 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Oct 28 07:10:29 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 28 07:10:55 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 07:11:03 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 07:11:20 node-1 multipathd: uevent trigger error
<27>Oct 28 07:11:20 node-1 multipathd: uevent trigger error
<27>Oct 28 07:11:20 node-1 multipathd: uevent trigger error
<27>Oct 28 07:11:20 node-1 multipathd: uevent trigger error
<27>Oct 28 07:11:20 node-1 multipathd: uevent trigger error
<27>Oct 28 07:11:20 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:06 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:07 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:07 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:07 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:07 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:12 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:12 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:12 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:12 node-1 multipathd: uevent trigger error
<43>Oct 28 07:13:26 node-1 apache2_error [Fri Oct 28 07:13:23.415261 2016] [mpm_event:notice] [pid 11701:tid 139991610419072] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 28 07:13:26 node-1 apache2_error [Fri Oct 28 07:13:23.415392 2016] [core:notice] [pid 11701:tid 139991610419072] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 28 07:13:26 node-1 apache2_error [Fri Oct 28 07:13:26.256280 2016] [mpm_event:notice] [pid 11701:tid 139991610419072] AH00491: caught SIGTERM, shutting down
<27>Oct 28 07:13:31 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:31 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:31 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:31 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:35 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:35 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:35 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:35 node-1 multipathd: uevent trigger error
<43>Oct 28 07:13:36 node-1 apache2_error [Fri Oct 28 07:13:27.340965 2016] [mpm_worker:notice] [pid 12249:tid 140565765932928] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 28 07:13:36 node-1 apache2_error [Fri Oct 28 07:13:27.340984 2016] [core:notice] [pid 12249:tid 140565765932928] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 07:13:44 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:44 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:44 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:44 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:52 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:52 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:52 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:52 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:52 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:56 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:56 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:57 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:57 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:57 node-1 multipathd: uevent trigger error
<27>Oct 28 07:13:57 node-1 multipathd: uevent trigger error
<27>Oct 28 07:14:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:14:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:14:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:14:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:14:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:14:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:14:10 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 28 07:15:07 node-1 apache2_error [Fri Oct 28 07:15:04.566526 2016] [mpm_worker:notice] [pid 12249:tid 140565765932928] AH00295: caught SIGTERM, shutting down
<43>Oct 28 07:15:07 node-1 apache2_error [Fri Oct 28 07:15:05.321538 2016] [mpm_worker:notice] [pid 30330:tid 139973884929920] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 07:15:07 node-1 apache2_error [Fri Oct 28 07:15:05.321579 2016] [core:notice] [pid 30330:tid 139973884929920] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 28 07:15:57 node-1 apache2_error [Fri Oct 28 07:15:49.272912 2016] [mpm_worker:notice] [pid 30330:tid 139973884929920] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 07:15:57 node-1 apache2_error [Fri Oct 28 07:15:49.465650 2016] [mpm_worker:warn] [pid 30330:tid 139973884929920] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 07:15:57 node-1 apache2_error [Fri Oct 28 07:15:49.469796 2016] [mpm_worker:notice] [pid 30330:tid 139973884929920] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 07:15:57 node-1 apache2_error [Fri Oct 28 07:15:49.469823 2016] [core:notice] [pid 30330:tid 139973884929920] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 07:16:33 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:33 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:33 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:33 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:33 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:37 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:37 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:37 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:37 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:37 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:42 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:42 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:42 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:42 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:42 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:58 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:58 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:58 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:58 node-1 multipathd: uevent trigger error
<27>Oct 28 07:16:58 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:15 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 07:17:23 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:23 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:23 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:23 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:23 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:28 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:28 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:28 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:28 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:28 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:28 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:46 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:46 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:46 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:46 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:46 node-1 multipathd: uevent trigger error
<27>Oct 28 07:17:46 node-1 multipathd: uevent trigger error
<27>Oct 28 07:18:36 node-1 multipathd: uevent trigger error
<27>Oct 28 07:18:36 node-1 multipathd: uevent trigger error
<27>Oct 28 07:18:36 node-1 multipathd: uevent trigger error
<27>Oct 28 07:18:36 node-1 multipathd: uevent trigger error
<27>Oct 28 07:18:36 node-1 multipathd: uevent trigger error
<27>Oct 28 07:19:42 node-1 multipathd: uevent trigger error
<27>Oct 28 07:19:42 node-1 multipathd: uevent trigger error
<27>Oct 28 07:19:42 node-1 multipathd: uevent trigger error
<27>Oct 28 07:19:42 node-1 multipathd: uevent trigger error
<27>Oct 28 07:19:42 node-1 multipathd: uevent trigger error
<27>Oct 28 07:20:16 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 07:20:37 node-1 multipathd: uevent trigger error
<27>Oct 28 07:20:37 node-1 multipathd: uevent trigger error
<27>Oct 28 07:20:37 node-1 multipathd: uevent trigger error
<27>Oct 28 07:20:37 node-1 multipathd: uevent trigger error
<27>Oct 28 07:21:03 node-1 multipathd: uevent trigger error
<27>Oct 28 07:21:03 node-1 multipathd: uevent trigger error
<27>Oct 28 07:21:03 node-1 multipathd: uevent trigger error
<27>Oct 28 07:21:03 node-1 multipathd: uevent trigger error
<27>Oct 28 07:21:03 node-1 multipathd: uevent trigger error
<27>Oct 28 07:21:09 node-1 multipathd: uevent trigger error
<27>Oct 28 07:21:09 node-1 multipathd: uevent trigger error
<27>Oct 28 07:21:09 node-1 multipathd: uevent trigger error
<27>Oct 28 07:21:09 node-1 multipathd: uevent trigger error
<27>Oct 28 07:21:09 node-1 multipathd: uevent trigger error
<27>Oct 28 07:23:18 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 07:23:28 node-1 multipathd: uevent trigger error
<27>Oct 28 07:23:28 node-1 multipathd: uevent trigger error
<27>Oct 28 07:23:28 node-1 multipathd: uevent trigger error
<27>Oct 28 07:23:28 node-1 multipathd: uevent trigger error
<27>Oct 28 07:23:28 node-1 multipathd: uevent trigger error
<27>Oct 28 07:23:43 node-1 multipathd: uevent trigger error
<27>Oct 28 07:23:43 node-1 multipathd: uevent trigger error
<27>Oct 28 07:23:43 node-1 multipathd: uevent trigger error
<27>Oct 28 07:23:43 node-1 multipathd: uevent trigger error
<27>Oct 28 07:23:43 node-1 multipathd: uevent trigger error
<27>Oct 28 07:23:43 node-1 multipathd: uevent trigger error
<27>Oct 28 07:23:49 node-1 multipathd: uevent trigger error
<27>Oct 28 07:23:49 node-1 multipathd: uevent trigger error
<27>Oct 28 07:23:49 node-1 multipathd: uevent trigger error
<27>Oct 28 07:23:49 node-1 multipathd: uevent trigger error
<27>Oct 28 07:23:49 node-1 multipathd: uevent trigger error
<27>Oct 28 07:24:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:24:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:24:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:24:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:24:29 node-1 multipathd: uevent trigger error
<27>Oct 28 07:24:34 node-1 multipathd: uevent trigger error
<27>Oct 28 07:24:34 node-1 multipathd: uevent trigger error
<27>Oct 28 07:24:34 node-1 multipathd: uevent trigger error
<27>Oct 28 07:24:34 node-1 multipathd: uevent trigger error
<27>Oct 28 07:24:34 node-1 multipathd: uevent trigger error
<27>Oct 28 07:24:34 node-1 multipathd: uevent trigger error
<27>Oct 28 07:24:55 node-1 multipathd: uevent trigger error
<27>Oct 28 07:24:55 node-1 multipathd: uevent trigger error
<27>Oct 28 07:24:55 node-1 multipathd: uevent trigger error
<27>Oct 28 07:24:55 node-1 multipathd: uevent trigger error
<27>Oct 28 07:24:55 node-1 multipathd: uevent trigger error
<27>Oct 28 07:25:38 node-1 multipathd: uevent trigger error
<27>Oct 28 07:25:38 node-1 multipathd: uevent trigger error
<27>Oct 28 07:25:38 node-1 multipathd: uevent trigger error
<27>Oct 28 07:25:38 node-1 multipathd: uevent trigger error
<27>Oct 28 07:25:38 node-1 multipathd: uevent trigger error
<27>Oct 28 07:25:38 node-1 multipathd: uevent trigger error
<27>Oct 28 07:25:45 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Oct 28 07:25:45 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Oct 28 07:25:46 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Oct 28 07:25:47 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Oct 28 07:25:47 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Oct 28 07:25:47 node-1 multipathd: uevent trigger error
<27>Oct 28 07:25:47 node-1 multipathd: uevent trigger error
<27>Oct 28 07:25:47 node-1 multipathd: uevent trigger error
<27>Oct 28 07:25:47 node-1 multipathd: uevent trigger error
<27>Oct 28 07:25:47 node-1 multipathd: uevent trigger error
<27>Oct 28 07:26:00 node-1 multipathd: uevent trigger error
<27>Oct 28 07:26:00 node-1 multipathd: uevent trigger error
<27>Oct 28 07:26:00 node-1 multipathd: uevent trigger error
<27>Oct 28 07:26:00 node-1 multipathd: uevent trigger error
<27>Oct 28 07:26:14 node-1 multipathd: uevent trigger error
<27>Oct 28 07:26:14 node-1 multipathd: uevent trigger error
<27>Oct 28 07:26:14 node-1 multipathd: uevent trigger error
<27>Oct 28 07:26:14 node-1 multipathd: uevent trigger error
<27>Oct 28 07:26:14 node-1 multipathd: uevent trigger error
<27>Oct 28 07:26:20 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 07:26:31 node-1 multipathd: uevent trigger error
<27>Oct 28 07:26:31 node-1 multipathd: uevent trigger error
<27>Oct 28 07:26:31 node-1 multipathd: uevent trigger error
<27>Oct 28 07:26:31 node-1 multipathd: uevent trigger error
<27>Oct 28 07:26:31 node-1 multipathd: uevent trigger error
<27>Oct 28 07:28:49 node-1 multipathd: uevent trigger error
<27>Oct 28 07:28:49 node-1 multipathd: uevent trigger error
<27>Oct 28 07:28:49 node-1 multipathd: uevent trigger error
<27>Oct 28 07:28:49 node-1 multipathd: uevent trigger error
<27>Oct 28 07:28:49 node-1 multipathd: uevent trigger error
<27>Oct 28 07:29:21 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 07:29:22 node-1 multipathd: uevent trigger error
<27>Oct 28 07:29:22 node-1 multipathd: uevent trigger error
<27>Oct 28 07:29:22 node-1 multipathd: uevent trigger error
<27>Oct 28 07:29:22 node-1 multipathd: uevent trigger error
<27>Oct 28 07:29:27 node-1 multipathd: uevent trigger error
<27>Oct 28 07:29:27 node-1 multipathd: uevent trigger error
<27>Oct 28 07:29:27 node-1 multipathd: uevent trigger error
<27>Oct 28 07:29:27 node-1 multipathd: uevent trigger error
<27>Oct 28 07:29:27 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:01 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:06 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:06 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:06 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:06 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:10 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:10 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:10 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:10 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:22 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:22 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:22 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:22 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:28 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:28 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:28 node-1 multipathd: uevent trigger error
<27>Oct 28 07:30:28 node-1 multipathd: uevent trigger error
<27>Oct 28 07:31:09 node-1 multipathd: uevent trigger error
<27>Oct 28 07:31:09 node-1 multipathd: uevent trigger error
<27>Oct 28 07:31:09 node-1 multipathd: uevent trigger error
<27>Oct 28 07:31:09 node-1 multipathd: uevent trigger error
<27>Oct 28 07:31:09 node-1 multipathd: uevent trigger error
<27>Oct 28 07:32:15 node-1 multipathd: uevent trigger error
<27>Oct 28 07:32:15 node-1 multipathd: uevent trigger error
<27>Oct 28 07:32:15 node-1 multipathd: uevent trigger error
<27>Oct 28 07:32:15 node-1 multipathd: uevent trigger error
<27>Oct 28 07:32:15 node-1 multipathd: uevent trigger error
<27>Oct 28 07:32:23 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 07:32:30 node-1 multipathd: uevent trigger error
<27>Oct 28 07:32:30 node-1 multipathd: uevent trigger error
<27>Oct 28 07:32:30 node-1 multipathd: uevent trigger error
<27>Oct 28 07:32:30 node-1 multipathd: uevent trigger error
<11>Oct 28 07:32:43 node-1 liberasurecode[9527]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:43 node-1 liberasurecode[9527]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:43 node-1 liberasurecode[9527]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:43 node-1 liberasurecode[9527]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:43 node-1 liberasurecode[9559]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:43 node-1 liberasurecode[9559]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:43 node-1 liberasurecode[9559]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:43 node-1 liberasurecode[9559]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:45 node-1 liberasurecode[9989]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:45 node-1 liberasurecode[9989]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:45 node-1 liberasurecode[9989]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:45 node-1 liberasurecode[9989]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:49 node-1 liberasurecode[10499]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:49 node-1 liberasurecode[10499]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:49 node-1 liberasurecode[10499]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:49 node-1 liberasurecode[10499]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:49 node-1 liberasurecode[10542]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:49 node-1 liberasurecode[10542]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:49 node-1 liberasurecode[10542]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:49 node-1 liberasurecode[10542]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:49 node-1 liberasurecode[10603]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:49 node-1 liberasurecode[10603]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:49 node-1 liberasurecode[10603]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:49 node-1 liberasurecode[10603]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:50 node-1 liberasurecode[10664]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:50 node-1 liberasurecode[10664]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:50 node-1 liberasurecode[10664]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:50 node-1 liberasurecode[10664]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:50 node-1 liberasurecode[10687]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:50 node-1 liberasurecode[10687]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:50 node-1 liberasurecode[10687]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:50 node-1 liberasurecode[10687]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:50 node-1 liberasurecode[10702]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:50 node-1 liberasurecode[10702]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:50 node-1 liberasurecode[10702]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:50 node-1 liberasurecode[10702]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:50 node-1 liberasurecode[10714]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:50 node-1 liberasurecode[10714]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:50 node-1 liberasurecode[10714]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:32:50 node-1 liberasurecode[10714]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 07:33:07 node-1 liberasurecode[12957]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:33:07 node-1 liberasurecode[12957]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:33:07 node-1 liberasurecode[12957]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:33:07 node-1 liberasurecode[12957]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 28 07:33:16 node-1 multipathd: uevent trigger error
<27>Oct 28 07:33:16 node-1 multipathd: uevent trigger error
<27>Oct 28 07:33:16 node-1 multipathd: uevent trigger error
<27>Oct 28 07:33:16 node-1 multipathd: uevent trigger error
<43>Oct 28 07:34:08 node-1 apache2_error [Fri Oct 28 07:34:02.150650 2016] [mpm_worker:notice] [pid 30330:tid 139973884929920] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 07:34:08 node-1 apache2_error [Fri Oct 28 07:34:02.532984 2016] [mpm_worker:warn] [pid 30330:tid 139973884929920] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 07:34:08 node-1 apache2_error [Fri Oct 28 07:34:02.536897 2016] [mpm_worker:notice] [pid 30330:tid 139973884929920] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 07:34:08 node-1 apache2_error [Fri Oct 28 07:34:02.536922 2016] [core:notice] [pid 30330:tid 139973884929920] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 07:34:43 node-1 multipathd: uevent trigger error
<27>Oct 28 07:34:43 node-1 multipathd: uevent trigger error
<27>Oct 28 07:34:43 node-1 multipathd: uevent trigger error
<27>Oct 28 07:34:43 node-1 multipathd: uevent trigger error
<43>Oct 28 07:34:48 node-1 apache2_error [Fri Oct 28 07:34:39.261206 2016] [mpm_worker:notice] [pid 30330:tid 139973884929920] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 07:34:48 node-1 apache2_error [Fri Oct 28 07:34:39.458347 2016] [mpm_worker:warn] [pid 30330:tid 139973884929920] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 07:34:48 node-1 apache2_error [Fri Oct 28 07:34:39.461888 2016] [mpm_worker:notice] [pid 30330:tid 139973884929920] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 07:34:48 node-1 apache2_error [Fri Oct 28 07:34:39.461900 2016] [core:notice] [pid 30330:tid 139973884929920] AH00094: Command line: '/usr/sbin/apache2'
<11>Oct 28 07:35:01 node-1 liberasurecode[28823]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:35:01 node-1 liberasurecode[28823]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:35:01 node-1 liberasurecode[28823]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:35:01 node-1 liberasurecode[28823]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Oct 28 07:35:18 node-1 apache2_error [Fri Oct 28 07:35:17.530402 2016] [mpm_worker:notice] [pid 30330:tid 139973884929920] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 07:35:18 node-1 apache2_error [Fri Oct 28 07:35:17.726908 2016] [mpm_worker:warn] [pid 30330:tid 139973884929920] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 07:35:18 node-1 apache2_error [Fri Oct 28 07:35:17.730606 2016] [mpm_worker:notice] [pid 30330:tid 139973884929920] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 07:35:18 node-1 apache2_error [Fri Oct 28 07:35:17.730628 2016] [core:notice] [pid 30330:tid 139973884929920] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 07:35:21 node-1 multipathd: uevent trigger error
<27>Oct 28 07:35:21 node-1 multipathd: uevent trigger error
<27>Oct 28 07:35:21 node-1 multipathd: uevent trigger error
<27>Oct 28 07:35:21 node-1 multipathd: uevent trigger error
<27>Oct 28 07:35:25 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 07:35:27 node-1 multipathd: uevent trigger error
<27>Oct 28 07:35:27 node-1 multipathd: uevent trigger error
<27>Oct 28 07:35:27 node-1 multipathd: uevent trigger error
<27>Oct 28 07:35:27 node-1 multipathd: uevent trigger error
<27>Oct 28 07:35:33 node-1 multipathd: uevent trigger error
<27>Oct 28 07:35:33 node-1 multipathd: uevent trigger error
<27>Oct 28 07:35:33 node-1 multipathd: uevent trigger error
<27>Oct 28 07:35:33 node-1 multipathd: uevent trigger error
<27>Oct 28 07:35:33 node-1 multipathd: uevent trigger error
<27>Oct 28 07:35:50 node-1 multipathd: uevent trigger error
<27>Oct 28 07:35:50 node-1 multipathd: uevent trigger error
<27>Oct 28 07:35:50 node-1 multipathd: uevent trigger error
<27>Oct 28 07:35:50 node-1 multipathd: uevent trigger error
<27>Oct 28 07:36:10 node-1 multipathd: uevent trigger error
<27>Oct 28 07:36:17 node-1 multipathd: uevent trigger error
<27>Oct 28 07:36:17 node-1 multipathd: uevent trigger error
<27>Oct 28 07:36:17 node-1 multipathd: uevent trigger error
<27>Oct 28 07:36:17 node-1 multipathd: uevent trigger error
<27>Oct 28 07:36:23 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 28 07:36:32 node-1 multipathd: uevent trigger error
<27>Oct 28 07:36:32 node-1 multipathd: uevent trigger error
<27>Oct 28 07:36:32 node-1 multipathd: uevent trigger error
<27>Oct 28 07:36:32 node-1 multipathd: uevent trigger error
<27>Oct 28 07:36:32 node-1 multipathd: uevent trigger error
<27>Oct 28 07:36:37 node-1 multipathd: uevent trigger error
<27>Oct 28 07:36:37 node-1 multipathd: uevent trigger error
<27>Oct 28 07:36:37 node-1 multipathd: uevent trigger error
<27>Oct 28 07:36:37 node-1 multipathd: uevent trigger error
<27>Oct 28 07:36:37 node-1 multipathd: uevent trigger error
<27>Oct 28 07:37:18 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 07:39:30 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:30 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:30 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:30 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:30 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:36 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:36 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:36 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:36 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:44 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:44 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:44 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:44 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:44 node-1 multipathd: uevent trigger error
<129>Oct 28 07:39:55 node-1 haproxy[22076]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 28 07:39:55 node-1 haproxy[22076]: 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>Oct 28 07:39:56 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:56 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:56 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:56 node-1 multipathd: uevent trigger error
<27>Oct 28 07:39:56 node-1 multipathd: uevent trigger error
<11>Oct 28 07:40:01 node-1 liberasurecode[27534]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:40:01 node-1 liberasurecode[27534]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:40:01 node-1 liberasurecode[27534]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 07:40:01 node-1 liberasurecode[27534]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 28 07:40:12 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:12 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:12 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:12 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:12 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:18 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:18 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:18 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:18 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:32 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:32 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:32 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:32 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:32 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:39 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:39 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:39 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:39 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:39 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:43 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:43 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:43 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:43 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:56 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:56 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:56 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:56 node-1 multipathd: uevent trigger error
<27>Oct 28 07:40:56 node-1 multipathd: uevent trigger error
<27>Oct 28 07:41:07 node-1 multipathd: uevent trigger error
<27>Oct 28 07:41:07 node-1 multipathd: uevent trigger error
<27>Oct 28 07:41:07 node-1 multipathd: uevent trigger error
<27>Oct 28 07:41:07 node-1 multipathd: uevent trigger error
<27>Oct 28 07:41:07 node-1 multipathd: uevent trigger error
<129>Oct 28 07:41:15 node-1 haproxy[22076]: 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>Oct 28 07:41:59 node-1 multipathd: uevent trigger error
<27>Oct 28 07:41:59 node-1 multipathd: uevent trigger error
<27>Oct 28 07:41:59 node-1 multipathd: uevent trigger error
<27>Oct 28 07:41:59 node-1 multipathd: uevent trigger error
<27>Oct 28 07:41:59 node-1 multipathd: uevent trigger error
<27>Oct 28 07:41:59 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:04 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:04 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:04 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:04 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:04 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:08 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:08 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:08 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:08 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:12 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:12 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:12 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:13 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:13 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:17 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:17 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:17 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:17 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:17 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:21 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:21 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:21 node-1 multipathd: uevent trigger error
<27>Oct 28 07:42:21 node-1 multipathd: uevent trigger error
