Oct 28 16:53:53 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8425" x-info="http://www.rsyslog.com"] start
Oct 28 16:53:53 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 28 16:53:53 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct 28 16:53:53 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct 28 16:53:53 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 28 16:53:53 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 28 16:53:53 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 28 16:53:53 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 16:53:53 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=afdbeedb-22e7-470e-bad6-fe5716245850 nomdmonddf nomdmonisw
Oct 28 16:53:53 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct 28 16:53:53 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct 28 16:53:53 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct 28 16:53:53 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct 28 16:53:53 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 28 16:53:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 28 16:53:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 28 16:53:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 28 16:53:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct 28 16:53:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct 28 16:53:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct 28 16:53:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct 28 16:53:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct 28 16:53:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 28 16:53:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 28 16:53:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 28 16:53:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 28 16:53:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 28 16:53:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 28 16:53:53 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 28 16:53:53 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 28 16:53:53 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 28 16:53:53 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 16:53:53 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 28 16:53:53 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 28 16:53:53 node-1 kernel: [    0.000000] No AGP bridge found
Oct 28 16:53:53 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 28 16:53:53 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct 28 16:53:53 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 28 16:53:53 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct 28 16:53:53 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 28 16:53:53 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 28 16:53:53 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 28 16:53:53 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 28 16:53:53 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 28 16:53:53 node-1 kernel: [    0.000000]   2 disabled
Oct 28 16:53:53 node-1 kernel: [    0.000000]   3 disabled
Oct 28 16:53:53 node-1 kernel: [    0.000000]   4 disabled
Oct 28 16:53:53 node-1 kernel: [    0.000000]   5 disabled
Oct 28 16:53:53 node-1 kernel: [    0.000000]   6 disabled
Oct 28 16:53:53 node-1 kernel: [    0.000000]   7 disabled
Oct 28 16:53:53 node-1 kernel: [    0.000000]   8 disabled
Oct 28 16:53:53 node-1 kernel: [    0.000000]   9 disabled
Oct 28 16:53:53 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 28 16:53:53 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 28 16:53:53 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 28 16:53:53 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 28 16:53:53 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 28 16:53:53 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct 28 16:53:53 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 28 16:53:53 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 28 16:53:53 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 28 16:53:53 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 28 16:53:53 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 28 16:53:53 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 28 16:53:53 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 28 16:53:53 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 28 16:53:53 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 28 16:53:53 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct 28 16:53:53 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 28 16:53:53 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 28 16:53:53 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 28 16:53:53 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 28 16:53:53 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 28 16:53:53 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 28 16:53:53 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 28 16:53:53 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 28 16:53:53 node-1 kernel: [    0.000000] Zone ranges:
Oct 28 16:53:53 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] Movable zone start for each node
Oct 28 16:53:53 node-1 kernel: [    0.000000] Early memory node ranges
Oct 28 16:53:53 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct 28 16:53:53 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 28 16:53:53 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 28 16:53:53 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 28 16:53:53 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct 28 16:53:53 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct 28 16:53:53 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 28 16:53:53 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 28 16:53:53 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 28 16:53:53 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 28 16:53:53 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 28 16:53:53 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 28 16:53:53 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 28 16:53:53 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 28 16:53:53 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 28 16:53:53 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 28 16:53:53 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 28 16:53:53 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 28 16:53:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 28 16:53:53 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 28 16:53:53 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 28 16:53:53 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 28 16:53:53 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 28 16:53:53 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 28 16:53:53 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 16:53:53 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct 28 16:53:53 node-1 kernel: [    0.000000] Policy zone: Normal
Oct 28 16:53:53 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=afdbeedb-22e7-470e-bad6-fe5716245850 nomdmonddf nomdmonisw
Oct 28 16:53:53 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 28 16:53:53 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 28 16:53:53 node-1 kernel: [    0.000000] Checking aperture...
Oct 28 16:53:53 node-1 kernel: [    0.000000] No AGP bridge found
Oct 28 16:53:53 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 28 16:53:53 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 28 16:53:53 node-1 kernel: [    0.000000] Memory: 32653320K/33280496K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627176K reserved)
Oct 28 16:53:53 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 28 16:53:53 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 28 16:53:53 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 28 16:53:53 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 28 16:53:53 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 28 16:53:53 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 28 16:53:53 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 28 16:53:53 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 28 16:53:53 node-1 kernel: [    0.000000] console [tty0] enabled
Oct 28 16:53:53 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 28 16:53:53 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 28 16:53:53 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 28 16:53:53 node-1 kernel: [    0.000000] hpet clockevent registered
Oct 28 16:53:53 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 28 16:53:53 node-1 kernel: [    0.004000] tsc: Detected 3491.882 MHz processor
Oct 28 16:53:53 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.76 BogoMIPS (lpj=13967528)
Oct 28 16:53:53 node-1 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Oct 28 16:53:53 node-1 kernel: [    0.000042] Security Framework initialized
Oct 28 16:53:53 node-1 kernel: [    0.000061] AppArmor: AppArmor initialized
Oct 28 16:53:53 node-1 kernel: [    0.000062] Yama: becoming mindful.
Oct 28 16:53:53 node-1 kernel: [    0.001471] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 28 16:53:53 node-1 kernel: [    0.006330] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 28 16:53:53 node-1 kernel: [    0.008263] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 28 16:53:53 node-1 kernel: [    0.008291] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 28 16:53:53 node-1 kernel: [    0.008581] Initializing cgroup subsys memory
Oct 28 16:53:53 node-1 kernel: [    0.008589] Initializing cgroup subsys devices
Oct 28 16:53:53 node-1 kernel: [    0.008591] Initializing cgroup subsys freezer
Oct 28 16:53:53 node-1 kernel: [    0.008593] Initializing cgroup subsys blkio
Oct 28 16:53:53 node-1 kernel: [    0.008594] Initializing cgroup subsys perf_event
Oct 28 16:53:53 node-1 kernel: [    0.008597] Initializing cgroup subsys hugetlb
Oct 28 16:53:53 node-1 kernel: [    0.008616] CPU: Physical Processor ID: 0
Oct 28 16:53:53 node-1 kernel: [    0.008617] CPU: Processor Core ID: 0
Oct 28 16:53:53 node-1 kernel: [    0.008621] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 28 16:53:53 node-1 kernel: [    0.008621] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 28 16:53:53 node-1 kernel: [    0.009315] mce: CPU supports 22 MCE banks
Oct 28 16:53:53 node-1 kernel: [    0.009342] CPU0: Thermal monitoring enabled (TM1)
Oct 28 16:53:53 node-1 kernel: [    0.009363] process: using mwait in idle threads
Oct 28 16:53:53 node-1 kernel: [    0.009366] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 28 16:53:53 node-1 kernel: [    0.009366] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 28 16:53:53 node-1 kernel: [    0.009366] tlb_flushall_shift: 6
Oct 28 16:53:53 node-1 kernel: [    0.009454] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 28 16:53:53 node-1 kernel: [    0.010177] ACPI: Core revision 20131115
Oct 28 16:53:53 node-1 kernel: [    0.022992] ACPI: All ACPI Tables successfully acquired
Oct 28 16:53:53 node-1 kernel: [    0.023152] ftrace: allocating 28622 entries in 112 pages
Oct 28 16:53:53 node-1 kernel: [    0.031901] dmar: Host address width 46
Oct 28 16:53:53 node-1 kernel: [    0.031903] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 28 16:53:53 node-1 kernel: [    0.031909] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 28 16:53:53 node-1 kernel: [    0.031911] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 28 16:53:53 node-1 kernel: [    0.031915] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 28 16:53:53 node-1 kernel: [    0.031917] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 28 16:53:53 node-1 kernel: [    0.031918] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 28 16:53:53 node-1 kernel: [    0.031919] dmar: ATSR flags: 0x0
Oct 28 16:53:53 node-1 kernel: [    0.031920] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 28 16:53:53 node-1 kernel: [    0.031921] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 28 16:53:53 node-1 kernel: [    0.032037] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 28 16:53:53 node-1 kernel: [    0.032039] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 28 16:53:53 node-1 kernel: [    0.032040] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 28 16:53:53 node-1 kernel: [    0.032041] HPET id 0 under DRHD base 0xc7ffc000
Oct 28 16:53:53 node-1 kernel: [    0.032042] Your BIOS is broken and requested that x2apic be disabled.
Oct 28 16:53:53 node-1 kernel: [    0.032042] This will slightly decrease performance.
Oct 28 16:53:53 node-1 kernel: [    0.032042] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 28 16:53:53 node-1 kernel: [    0.032472] Enabled IRQ remapping in xapic mode
Oct 28 16:53:53 node-1 kernel: [    0.032473] x2apic not enabled, IRQ remapping is in xapic mode
Oct 28 16:53:53 node-1 kernel: [    0.032477] Switched APIC routing to physical flat.
Oct 28 16:53:53 node-1 kernel: [    0.033107] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 28 16:53:53 node-1 kernel: [    0.072757] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 28 16:53:53 node-1 kernel: [    0.072763] TSC deadline timer enabled
Oct 28 16:53:53 node-1 kernel: [    0.072770] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 28 16:53:53 node-1 kernel: [    0.072776] ... version:                3
Oct 28 16:53:53 node-1 kernel: [    0.072777] ... bit width:              48
Oct 28 16:53:53 node-1 kernel: [    0.072778] ... generic registers:      4
Oct 28 16:53:53 node-1 kernel: [    0.072779] ... value mask:             0000ffffffffffff
Oct 28 16:53:53 node-1 kernel: [    0.072780] ... max period:             0000ffffffffffff
Oct 28 16:53:53 node-1 kernel: [    0.072781] ... fixed-purpose events:   3
Oct 28 16:53:53 node-1 kernel: [    0.072781] ... event mask:             000000070000000f
Oct 28 16:53:53 node-1 kernel: [    0.074192] x86: Booting SMP configuration:
Oct 28 16:53:53 node-1 kernel: [    0.088298] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 28 16:53:53 node-1 kernel: [    0.074194] .... node  #0, CPUs:        #1  #2  #3
Oct 28 16:53:53 node-1 kernel: [    0.116209] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 28 16:53:53 node-1 kernel: [    0.270349] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 28 16:53:53 node-1 kernel: [    0.325964] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 28 16:53:53 node-1 kernel: [    0.382807] x86: Booted up 2 nodes, 16 CPUs
Oct 28 16:53:53 node-1 kernel: [    0.382811] smpboot: Total of 16 processors activated (111753.03 BogoMIPS)
Oct 28 16:53:53 node-1 kernel: [    0.407589] devtmpfs: initialized
Oct 28 16:53:53 node-1 kernel: [    0.410174] EVM: security.selinux
Oct 28 16:53:53 node-1 kernel: [    0.410176] EVM: security.SMACK64
Oct 28 16:53:53 node-1 kernel: [    0.410177] EVM: security.ima
Oct 28 16:53:53 node-1 kernel: [    0.410178] EVM: security.capability
Oct 28 16:53:53 node-1 kernel: [    0.410227] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct 28 16:53:53 node-1 kernel: [    0.410892] pinctrl core: initialized pinctrl subsystem
Oct 28 16:53:53 node-1 kernel: [    0.410955] regulator-dummy: no parameters
Oct 28 16:53:53 node-1 kernel: [    0.410987] RTC time: 16:53:15, date: 10/28/16
Oct 28 16:53:53 node-1 kernel: [    0.411022] NET: Registered protocol family 16
Oct 28 16:53:53 node-1 kernel: [    0.411121] cpuidle: using governor ladder
Oct 28 16:53:53 node-1 kernel: [    0.411123] cpuidle: using governor menu
Oct 28 16:53:53 node-1 kernel: [    0.411157] ACPI: bus type PCI registered
Oct 28 16:53:53 node-1 kernel: [    0.411159] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 28 16:53:53 node-1 kernel: [    0.411205] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 28 16:53:53 node-1 kernel: [    0.411208] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 28 16:53:53 node-1 kernel: [    0.424939] PCI: Using configuration type 1 for base access
Oct 28 16:53:53 node-1 kernel: [    0.425937] bio: create slab <bio-0> at 0
Oct 28 16:53:53 node-1 kernel: [    0.426203] ACPI: Added _OSI(Module Device)
Oct 28 16:53:53 node-1 kernel: [    0.426205] ACPI: Added _OSI(Processor Device)
Oct 28 16:53:53 node-1 kernel: [    0.426206] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 28 16:53:53 node-1 kernel: [    0.426207] ACPI: Added _OSI(Processor Aggregator Device)
Oct 28 16:53:53 node-1 kernel: [    0.438899] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 28 16:53:53 node-1 kernel: [    0.449526] ACPI: Interpreter enabled
Oct 28 16:53:53 node-1 kernel: [    0.449532] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 28 16:53:53 node-1 kernel: [    0.449536] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 28 16:53:53 node-1 kernel: [    0.449539] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 28 16:53:53 node-1 kernel: [    0.449546] ACPI: (supports S0 S4 S5)
Oct 28 16:53:53 node-1 kernel: [    0.449547] ACPI: Using IOAPIC for interrupt routing
Oct 28 16:53:53 node-1 kernel: [    0.449587] HEST: Table parsing has been initialized.
Oct 28 16:53:53 node-1 kernel: [    0.449590] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 28 16:53:53 node-1 kernel: [    0.450143] ACPI: No dock devices found.
Oct 28 16:53:53 node-1 kernel: [    0.461679] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 28 16:53:53 node-1 kernel: [    0.461684] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 16:53:53 node-1 kernel: [    0.461687] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 28 16:53:53 node-1 kernel: [    0.461716] PCI host bridge to bus 0000:ff
Oct 28 16:53:53 node-1 kernel: [    0.461718] pci_bus 0000:ff: root bus resource [bus ff]
Oct 28 16:53:53 node-1 kernel: [    0.461726] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.461763] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 28 16:53:53 node-1 kernel: [    0.461794] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.461829] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.461858] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 28 16:53:53 node-1 kernel: [    0.461887] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 28 16:53:53 node-1 kernel: [    0.461917] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.461946] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.461974] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462002] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462028] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462054] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462082] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462107] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462134] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462160] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462190] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462217] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462243] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 28 16:53:53 node-1 kernel: [    0.462271] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462297] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 28 16:53:53 node-1 kernel: [    0.462322] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462348] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462378] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 28 16:53:53 node-1 kernel: [    0.462412] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462443] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462473] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462503] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462533] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462564] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462594] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462626] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462657] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462689] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462721] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462754] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462787] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462816] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462844] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462875] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462908] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462943] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.462978] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463010] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463040] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463069] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463099] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463127] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463157] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463190] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463221] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463249] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463278] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463306] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463335] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463366] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463397] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463453] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 28 16:53:53 node-1 kernel: [    0.463455] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 16:53:53 node-1 kernel: [    0.463458] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 28 16:53:53 node-1 kernel: [    0.463476] PCI host bridge to bus 0000:7f
Oct 28 16:53:53 node-1 kernel: [    0.463478] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 28 16:53:53 node-1 kernel: [    0.463483] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463510] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 28 16:53:53 node-1 kernel: [    0.463538] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463567] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463589] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 28 16:53:53 node-1 kernel: [    0.463613] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 28 16:53:53 node-1 kernel: [    0.463637] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463661] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463687] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463711] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463735] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463758] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463784] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463806] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463830] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463855] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463876] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463899] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463921] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 28 16:53:53 node-1 kernel: [    0.463945] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.463967] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 28 16:53:53 node-1 kernel: [    0.463988] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464011] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464037] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 28 16:53:53 node-1 kernel: [    0.464070] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464096] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464122] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464150] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464175] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464203] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464228] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464255] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464280] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464306] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464331] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464359] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464387] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464411] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464435] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464463] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464488] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464514] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464543] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464571] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464595] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464620] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464645] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464671] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464697] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464723] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464752] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464777] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464800] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464825] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464850] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464878] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.464904] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.466148] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 28 16:53:53 node-1 kernel: [    0.466152] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 16:53:53 node-1 kernel: [    0.467269] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 28 16:53:53 node-1 kernel: [    0.467781] PCI host bridge to bus 0000:00
Oct 28 16:53:53 node-1 kernel: [    0.467783] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 28 16:53:53 node-1 kernel: [    0.467785] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 28 16:53:53 node-1 kernel: [    0.467786] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 28 16:53:53 node-1 kernel: [    0.467788] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 28 16:53:53 node-1 kernel: [    0.467789] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 28 16:53:53 node-1 kernel: [    0.467790] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 28 16:53:53 node-1 kernel: [    0.467792] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 28 16:53:53 node-1 kernel: [    0.467798] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 28 16:53:53 node-1 kernel: [    0.467880] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 28 16:53:53 node-1 kernel: [    0.467910] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 28 16:53:53 node-1 kernel: [    0.467952] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 28 16:53:53 node-1 kernel: [    0.467971] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 28 16:53:53 node-1 kernel: [    0.468000] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 28 16:53:53 node-1 kernel: [    0.468040] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 28 16:53:53 node-1 kernel: [    0.468058] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 28 16:53:53 node-1 kernel: [    0.468088] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 28 16:53:53 node-1 kernel: [    0.468130] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 28 16:53:53 node-1 kernel: [    0.468147] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.468217] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.468293] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.468368] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 28 16:53:53 node-1 kernel: [    0.468373] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 28 16:53:53 node-1 kernel: [    0.468457] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 28 16:53:53 node-1 kernel: [    0.468605] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 28 16:53:53 node-1 kernel: [    0.468622] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 28 16:53:53 node-1 kernel: [    0.468700] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 28 16:53:53 node-1 kernel: [    0.468753] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 28 16:53:53 node-1 kernel: [    0.468774] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 28 16:53:53 node-1 kernel: [    0.468829] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 28 16:53:53 node-1 kernel: [    0.468873] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 28 16:53:53 node-1 kernel: [    0.468899] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 28 16:53:53 node-1 kernel: [    0.468955] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 28 16:53:53 node-1 kernel: [    0.468997] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 28 16:53:53 node-1 kernel: [    0.469021] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 28 16:53:53 node-1 kernel: [    0.469039] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 28 16:53:53 node-1 kernel: [    0.469116] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 28 16:53:53 node-1 kernel: [    0.469166] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 28 16:53:53 node-1 kernel: [    0.469191] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 28 16:53:53 node-1 kernel: [    0.469439] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 28 16:53:53 node-1 kernel: [    0.469445] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 28 16:53:53 node-1 kernel: [    0.469451] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 28 16:53:53 node-1 kernel: [    0.469457] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 28 16:53:53 node-1 kernel: [    0.469464] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 28 16:53:53 node-1 kernel: [    0.469494] pci 0000:01:00.0: supports D1 D2
Oct 28 16:53:53 node-1 kernel: [    0.479692] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 28 16:53:53 node-1 kernel: [    0.479698] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 28 16:53:53 node-1 kernel: [    0.479702] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 28 16:53:53 node-1 kernel: [    0.479961] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 28 16:53:53 node-1 kernel: [    0.479994] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 28 16:53:53 node-1 kernel: [    0.491687] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 28 16:53:53 node-1 kernel: [    0.491693] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 28 16:53:53 node-1 kernel: [    0.491697] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 16:53:53 node-1 kernel: [    0.491781] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 28 16:53:53 node-1 kernel: [    0.491853] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 28 16:53:53 node-1 kernel: [    0.491968] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 28 16:53:53 node-1 kernel: [    0.492014] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 28 16:53:53 node-1 kernel: [    0.492018] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 16:53:53 node-1 kernel: [    0.492019] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 16:53:53 node-1 kernel: [    0.492072] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 28 16:53:53 node-1 kernel: [    0.492194] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 28 16:53:53 node-1 kernel: [    0.492248] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 28 16:53:53 node-1 kernel: [    0.492251] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 16:53:53 node-1 kernel: [    0.492253] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 16:53:53 node-1 kernel: [    0.492306] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 28 16:53:53 node-1 kernel: [    0.492425] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 28 16:53:53 node-1 kernel: [    0.492463] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 28 16:53:53 node-1 kernel: [    0.492583] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 28 16:53:53 node-1 kernel: [    0.492619] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 28 16:53:53 node-1 kernel: [    0.492741] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 28 16:53:53 node-1 kernel: [    0.492777] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 28 16:53:53 node-1 kernel: [    0.492896] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 28 16:53:53 node-1 kernel: [    0.492956] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 28 16:53:53 node-1 kernel: [    0.492959] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 16:53:53 node-1 kernel: [    0.492961] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 16:53:53 node-1 kernel: [    0.493020] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 28 16:53:53 node-1 kernel: [    0.493084] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 28 16:53:53 node-1 kernel: [    0.493136] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 28 16:53:53 node-1 kernel: [    0.493178] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 28 16:53:53 node-1 kernel: [    0.493263] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 28 16:53:53 node-1 kernel: [    0.493369] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 28 16:53:53 node-1 kernel: [    0.493371] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 16:53:53 node-1 kernel: [    0.493373] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 28 16:53:53 node-1 kernel: [    0.493429] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 28 16:53:53 node-1 kernel: [    0.493483] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 28 16:53:53 node-1 kernel: [    0.493531] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 28 16:53:53 node-1 kernel: [    0.493746] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 28 16:53:53 node-1 kernel: [    0.493750] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 28 16:53:53 node-1 kernel: [    0.493815] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 28 16:53:53 node-1 kernel: [    0.493868] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 28 16:53:53 node-1 kernel: [    0.493941] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 28 16:53:53 node-1 kernel: [    0.494151] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 28 16:53:53 node-1 kernel: [    0.494155] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 28 16:53:53 node-1 kernel: [    0.494212] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 28 16:53:53 node-1 kernel: [    0.494272] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 28 16:53:53 node-1 kernel: [    0.494328] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 28 16:53:53 node-1 kernel: [    0.494550] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 28 16:53:53 node-1 kernel: [    0.494554] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 28 16:53:53 node-1 kernel: [    0.494729] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 28 16:53:53 node-1 kernel: [    0.494768] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 28 16:53:53 node-1 kernel: [    0.494843] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 28 16:53:53 node-1 kernel: [    0.494862] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 28 16:53:53 node-1 kernel: [    0.494875] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 28 16:53:53 node-1 kernel: [    0.494888] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 28 16:53:53 node-1 kernel: [    0.494938] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 28 16:53:53 node-1 kernel: [    0.499695] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 28 16:53:53 node-1 kernel: [    0.499704] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 28 16:53:53 node-1 kernel: [    0.499756] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 28 16:53:53 node-1 kernel: [    0.500427] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 28 16:53:53 node-1 kernel: [    0.500430] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 28 16:53:53 node-1 kernel: [    0.500555] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 28 16:53:53 node-1 kernel: [    0.500662] PCI host bridge to bus 0000:80
Oct 28 16:53:53 node-1 kernel: [    0.500664] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 28 16:53:53 node-1 kernel: [    0.500666] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 28 16:53:53 node-1 kernel: [    0.500667] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 28 16:53:53 node-1 kernel: [    0.500676] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.500740] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.500809] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 28 16:53:53 node-1 kernel: [    0.500871] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 28 16:53:53 node-1 kernel: [    0.500877] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 28 16:53:53 node-1 kernel: [    0.500950] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 28 16:53:53 node-1 kernel: [    0.501250] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 28 16:53:53 node-1 kernel: [    0.501281] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 28 16:53:53 node-1 kernel: [    0.501311] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 28 16:53:53 node-1 kernel: [    0.501339] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 28 16:53:53 node-1 kernel: [    0.501369] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 16:53:53 node-1 kernel: [    0.501398] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 16:53:53 node-1 kernel: [    0.501428] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 16:53:53 node-1 kernel: [    0.501458] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 28 16:53:53 node-1 kernel: [    0.501543] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 28 16:53:53 node-1 kernel: [    0.501548] ACPI: \_SB_.UNC1: notify handler is installed
Oct 28 16:53:53 node-1 kernel: [    0.501549] ACPI: \_SB_.UNC0: notify handler is installed
Oct 28 16:53:53 node-1 kernel: [    0.501564] ACPI: \_SB_.PCI0: notify handler is installed
Oct 28 16:53:53 node-1 kernel: [    0.501617] ACPI: \_SB_.PCI1: notify handler is installed
Oct 28 16:53:53 node-1 kernel: [    0.501697] Found 4 acpi root devices
Oct 28 16:53:53 node-1 kernel: [    0.501806] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 28 16:53:53 node-1 kernel: [    0.501808] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 28 16:53:53 node-1 kernel: [    0.501810] vgaarb: loaded
Oct 28 16:53:53 node-1 kernel: [    0.501811] vgaarb: bridge control possible 0000:0c:00.0
Oct 28 16:53:53 node-1 kernel: [    0.501939] SCSI subsystem initialized
Oct 28 16:53:53 node-1 kernel: [    0.502004] libata version 3.00 loaded.
Oct 28 16:53:53 node-1 kernel: [    0.502019] ACPI: bus type USB registered
Oct 28 16:53:53 node-1 kernel: [    0.502029] usbcore: registered new interface driver usbfs
Oct 28 16:53:53 node-1 kernel: [    0.502034] usbcore: registered new interface driver hub
Oct 28 16:53:53 node-1 kernel: [    0.502059] usbcore: registered new device driver usb
Oct 28 16:53:53 node-1 kernel: [    0.502226] PCI: Using ACPI for IRQ routing
Oct 28 16:53:53 node-1 kernel: [    0.505822] PCI: pci_cache_line_size set to 64 bytes
Oct 28 16:53:53 node-1 kernel: [    0.506047] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 28 16:53:53 node-1 kernel: [    0.506049] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct 28 16:53:53 node-1 kernel: [    0.506049] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 28 16:53:53 node-1 kernel: [    0.506115] NetLabel: Initializing
Oct 28 16:53:53 node-1 kernel: [    0.506116] NetLabel:  domain hash size = 128
Oct 28 16:53:53 node-1 kernel: [    0.506117] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 28 16:53:53 node-1 kernel: [    0.506127] NetLabel:  unlabeled traffic allowed by default
Oct 28 16:53:53 node-1 kernel: [    0.506183] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 28 16:53:53 node-1 kernel: [    0.506187] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 28 16:53:53 node-1 kernel: [    0.508244] Switched to clocksource hpet
Oct 28 16:53:53 node-1 kernel: [    0.512146] AppArmor: AppArmor Filesystem Enabled
Oct 28 16:53:53 node-1 kernel: [    0.512160] pnp: PnP ACPI init
Oct 28 16:53:53 node-1 kernel: [    0.512167] ACPI: bus type PNP registered
Oct 28 16:53:53 node-1 kernel: [    0.512290] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 28 16:53:53 node-1 kernel: [    0.512298] pnp 00:01: [dma 4]
Oct 28 16:53:53 node-1 kernel: [    0.512310] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 28 16:53:53 node-1 kernel: [    0.512336] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 28 16:53:53 node-1 kernel: [    0.512356] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 28 16:53:53 node-1 kernel: [    0.512374] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 28 16:53:53 node-1 kernel: [    0.512407] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 28 16:53:53 node-1 kernel: [    0.512458] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 28 16:53:53 node-1 kernel: [    0.512461] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 28 16:53:53 node-1 kernel: [    0.512462] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 28 16:53:53 node-1 kernel: [    0.512464] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 28 16:53:53 node-1 kernel: [    0.512465] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 28 16:53:53 node-1 kernel: [    0.512469] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 28 16:53:53 node-1 kernel: [    0.512472] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 28 16:53:53 node-1 kernel: [    0.512473] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 28 16:53:53 node-1 kernel: [    0.512475] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 28 16:53:53 node-1 kernel: [    0.512476] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 28 16:53:53 node-1 kernel: [    0.512478] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 28 16:53:53 node-1 kernel: [    0.512479] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 28 16:53:53 node-1 kernel: [    0.512481] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 28 16:53:53 node-1 kernel: [    0.512483] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 28 16:53:53 node-1 kernel: [    0.512566] pnp 00:07: [dma 0 disabled]
Oct 28 16:53:53 node-1 kernel: [    0.512595] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 28 16:53:53 node-1 kernel: [    0.512670] pnp 00:08: [dma 0 disabled]
Oct 28 16:53:53 node-1 kernel: [    0.512701] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 28 16:53:53 node-1 kernel: [    0.512751] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 28 16:53:53 node-1 kernel: [    0.513097] pnp: PnP ACPI: found 10 devices
Oct 28 16:53:53 node-1 kernel: [    0.513099] ACPI: bus type PNP unregistered
Oct 28 16:53:53 node-1 kernel: [    0.519316] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 28 16:53:53 node-1 kernel: [    0.519319] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 28 16:53:53 node-1 kernel: [    0.519321] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 28 16:53:53 node-1 kernel: [    0.519326] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 28 16:53:53 node-1 kernel: [    0.519327] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 16:53:53 node-1 kernel: [    0.519342] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 28 16:53:53 node-1 kernel: [    0.519371] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 28 16:53:53 node-1 kernel: [    0.519386] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 28 16:53:53 node-1 kernel: [    0.519415] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 28 16:53:53 node-1 kernel: [    0.519429] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 28 16:53:53 node-1 kernel: [    0.519462] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 28 16:53:53 node-1 kernel: [    0.519476] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 28 16:53:53 node-1 kernel: [    0.519505] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 28 16:53:53 node-1 kernel: [    0.519507] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 16:53:53 node-1 kernel: [    0.519521] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 16:53:53 node-1 kernel: [    0.519550] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 28 16:53:53 node-1 kernel: [    0.519552] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 16:53:53 node-1 kernel: [    0.519566] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 28 16:53:53 node-1 kernel: [    0.519595] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 28 16:53:53 node-1 kernel: [    0.519597] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 28 16:53:53 node-1 kernel: [    0.519600] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 16:53:53 node-1 kernel: [    0.519604] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 28 16:53:53 node-1 kernel: [    0.519606] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 28 16:53:53 node-1 kernel: [    0.519608] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 28 16:53:53 node-1 kernel: [    0.519612] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 28 16:53:53 node-1 kernel: [    0.519616] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 28 16:53:53 node-1 kernel: [    0.519624] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 28 16:53:53 node-1 kernel: [    0.519628] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 28 16:53:53 node-1 kernel: [    0.519634] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 28 16:53:53 node-1 kernel: [    0.519635] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 28 16:53:53 node-1 kernel: [    0.519636] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 28 16:53:53 node-1 kernel: [    0.519637] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 28 16:53:53 node-1 kernel: [    0.519638] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 28 16:53:53 node-1 kernel: [    0.519639] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 28 16:53:53 node-1 kernel: [    0.519640] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 28 16:53:53 node-1 kernel: [    0.519641] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 28 16:53:53 node-1 kernel: [    0.519642] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 28 16:53:53 node-1 kernel: [    0.519642] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 28 16:53:53 node-1 kernel: [    0.519643] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 28 16:53:53 node-1 kernel: [    0.519644] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 28 16:53:53 node-1 kernel: [    0.519645] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 28 16:53:53 node-1 kernel: [    0.519646] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 28 16:53:53 node-1 kernel: [    0.519647] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 28 16:53:53 node-1 kernel: [    0.519648] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 28 16:53:53 node-1 kernel: [    0.519649] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 28 16:53:53 node-1 kernel: [    0.519650] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 28 16:53:53 node-1 kernel: [    0.519651] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 28 16:53:53 node-1 kernel: [    0.519652] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 28 16:53:53 node-1 kernel: [    0.519653] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 28 16:53:53 node-1 kernel: [    0.519654] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 28 16:53:53 node-1 kernel: [    0.519656] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 28 16:53:53 node-1 kernel: [    0.519657] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 28 16:53:53 node-1 kernel: [    0.519692] NET: Registered protocol family 2
Oct 28 16:53:53 node-1 kernel: [    0.519950] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 28 16:53:53 node-1 kernel: [    0.520288] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 28 16:53:53 node-1 kernel: [    0.520431] TCP: Hash tables configured (established 262144 bind 65536)
Oct 28 16:53:53 node-1 kernel: [    0.520468] TCP: reno registered
Oct 28 16:53:53 node-1 kernel: [    0.520496] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 28 16:53:53 node-1 kernel: [    0.520593] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 28 16:53:53 node-1 kernel: [    0.520740] NET: Registered protocol family 1
Oct 28 16:53:53 node-1 kernel: [    0.556344] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 28 16:53:53 node-1 kernel: [    0.556357] PCI: CLS 64 bytes, default 64
Oct 28 16:53:53 node-1 kernel: [    0.556434] Trying to unpack rootfs image as initramfs...
Oct 28 16:53:53 node-1 kernel: [    0.775952] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Oct 28 16:53:53 node-1 kernel: [    0.775999] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 28 16:53:53 node-1 kernel: [    0.776002] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct 28 16:53:53 node-1 kernel: [    0.776430] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 16:53:53 node-1 kernel: [    0.776436] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 16:53:53 node-1 kernel: [    0.776441] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 16:53:53 node-1 kernel: [    0.776447] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 16:53:53 node-1 kernel: [    0.776458] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 16:53:53 node-1 kernel: [    0.776475] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 16:53:53 node-1 kernel: [    0.776490] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 16:53:53 node-1 kernel: [    0.776505] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 16:53:53 node-1 kernel: [    0.776517] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 16:53:53 node-1 kernel: [    0.776527] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 16:53:53 node-1 kernel: [    0.776533] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 16:53:53 node-1 kernel: [    0.776540] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 16:53:53 node-1 kernel: [    0.776549] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 16:53:53 node-1 kernel: [    0.776562] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 16:53:53 node-1 kernel: [    0.776574] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 16:53:53 node-1 kernel: [    0.776587] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 28 16:53:53 node-1 kernel: [    0.776697] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 28 16:53:53 node-1 kernel: [    0.776703] Scanning for low memory corruption every 60 seconds
Oct 28 16:53:53 node-1 kernel: [    0.777153] Initialise system trusted keyring
Oct 28 16:53:53 node-1 kernel: [    0.777204] audit: initializing netlink socket (disabled)
Oct 28 16:53:53 node-1 kernel: [    0.777219] type=2000 audit(1477673594.728:1): initialized
Oct 28 16:53:53 node-1 kernel: [    0.795013] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 28 16:53:53 node-1 kernel: [    0.796548] zbud: loaded
Oct 28 16:53:53 node-1 kernel: [    0.796675] VFS: Disk quotas dquot_6.5.2
Oct 28 16:53:53 node-1 kernel: [    0.796709] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 28 16:53:53 node-1 kernel: [    0.797092] fuse init (API version 7.22)
Oct 28 16:53:53 node-1 kernel: [    0.797157] msgmni has been set to 32768
Oct 28 16:53:53 node-1 kernel: [    0.797206] Key type big_key registered
Oct 28 16:53:53 node-1 kernel: [    0.797686] Key type asymmetric registered
Oct 28 16:53:53 node-1 kernel: [    0.797688] Asymmetric key parser 'x509' registered
Oct 28 16:53:53 node-1 kernel: [    0.797710] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 28 16:53:53 node-1 kernel: [    0.797783] io scheduler noop registered
Oct 28 16:53:53 node-1 kernel: [    0.797785] io scheduler deadline registered (default)
Oct 28 16:53:53 node-1 kernel: [    0.797805] io scheduler cfq registered
Oct 28 16:53:53 node-1 kernel: [    0.798293] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    0.798413] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    0.798528] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 28 16:53:53 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 16:53:53 node-1 kernel: [    0.798638] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    0.798752] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    0.798849] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    0.799251] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 28 16:53:53 node-1 kernel: [    0.799297] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 28 16:53:53 node-1 kernel: [    0.799324] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 28 16:53:53 node-1 kernel: [    0.799343] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799348] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799354] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 28 16:53:53 node-1 kernel: [    0.799365] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799369] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799372] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799376] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799380] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799384] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799388] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799392] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799395] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799399] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799403] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799406] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799412] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 28 16:53:53 node-1 kernel: [    0.799422] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799427] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 28 16:53:53 node-1 kernel: [    0.799452] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799458] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 28 16:53:53 node-1 kernel: [    0.799477] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799481] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 28 16:53:53 node-1 kernel: [    0.799487] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 28 16:53:53 node-1 kernel: [    0.799547] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 28 16:53:53 node-1 kernel: [    0.799560] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 28 16:53:53 node-1 kernel: [    0.799569] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 28 16:53:53 node-1 kernel: [    0.799591] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 28 16:53:53 node-1 kernel: [    0.799680] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 28 16:53:53 node-1 kernel: [    0.799684] vesafb: scrolling: redraw
Oct 28 16:53:53 node-1 kernel: [    0.799688] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 28 16:53:53 node-1 kernel: [    0.820481] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 28 16:53:53 node-1 kernel: [    0.828965] Console: switching to colour frame buffer device 80x30
Oct 28 16:53:53 node-1 kernel: [    0.837642] fb0: VESA VGA frame buffer device
Oct 28 16:53:53 node-1 kernel: [    0.837839] intel_idle: MWAIT substates: 0x2120
Oct 28 16:53:53 node-1 kernel: [    0.837840] intel_idle: v0.4 model 0x3F
Oct 28 16:53:53 node-1 kernel: [    0.837840] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 28 16:53:53 node-1 kernel: [    0.838069] ipmi message handler version 39.2
Oct 28 16:53:53 node-1 kernel: [    0.838350] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 28 16:53:53 node-1 kernel: [    0.838782] ACPI: AC Adapter [P111] (on-line)
Oct 28 16:53:53 node-1 kernel: [    0.844029] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 28 16:53:53 node-1 kernel: [    0.855082] ACPI: Power Button [PWRB]
Oct 28 16:53:53 node-1 kernel: [    0.860881] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 28 16:53:53 node-1 kernel: [    0.872575] ACPI: Power Button [PWRF]
Oct 28 16:53:53 node-1 kernel: [    0.897779] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 28 16:53:53 node-1 kernel: [    0.909449] pstore: Registered erst as persistent store backend
Oct 28 16:53:53 node-1 kernel: [    0.915663] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 28 16:53:53 node-1 kernel: [    0.927662] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 28 16:53:53 node-1 kernel: [    0.954495] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 28 16:53:53 node-1 kernel: [    0.987785] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 28 16:53:53 node-1 kernel: [    1.001797] Linux agpgart interface v0.103
Oct 28 16:53:53 node-1 kernel: [    1.009444] brd: module loaded
Oct 28 16:53:53 node-1 kernel: [    1.016519] loop: module loaded
Oct 28 16:53:53 node-1 kernel: [    1.023241] libphy: Fixed MDIO Bus: probed
Oct 28 16:53:53 node-1 kernel: [    1.029716] tun: Universal TUN/TAP device driver, 1.6
Oct 28 16:53:53 node-1 kernel: [    1.036186] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 28 16:53:53 node-1 kernel: [    1.042703] PPP generic driver version 2.4.2
Oct 28 16:53:53 node-1 kernel: [    1.049078] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 28 16:53:53 node-1 kernel: [    1.055512] ehci-pci: EHCI PCI platform driver
Oct 28 16:53:53 node-1 kernel: [    1.062019] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 28 16:53:53 node-1 kernel: [    1.068416] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 28 16:53:53 node-1 kernel: [    1.080937] ehci-pci 0000:00:1a.0: debug port 2
Oct 28 16:53:53 node-1 kernel: [    1.091117] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 28 16:53:53 node-1 kernel: [    1.091136] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 28 16:53:53 node-1 kernel: [    1.107740] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 28 16:53:53 node-1 kernel: [    1.113799] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 28 16:53:53 node-1 kernel: [    1.119965] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 28 16:53:53 node-1 kernel: [    1.131840] usb usb1: Product: EHCI Host Controller
Oct 28 16:53:53 node-1 kernel: [    1.137898] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 28 16:53:53 node-1 kernel: [    1.143939] usb usb1: SerialNumber: 0000:00:1a.0
Oct 28 16:53:53 node-1 kernel: [    1.149900] hub 1-0:1.0: USB hub found
Oct 28 16:53:53 node-1 kernel: [    1.155661] hub 1-0:1.0: 2 ports detected
Oct 28 16:53:53 node-1 kernel: [    1.161438] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 28 16:53:53 node-1 kernel: [    1.167003] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 28 16:53:53 node-1 kernel: [    1.177884] ehci-pci 0000:00:1d.0: debug port 2
Oct 28 16:53:53 node-1 kernel: [    1.187192] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 28 16:53:53 node-1 kernel: [    1.187195] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 28 16:53:53 node-1 kernel: [    1.203659] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 28 16:53:53 node-1 kernel: [    1.208854] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 28 16:53:53 node-1 kernel: [    1.214149] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 28 16:53:53 node-1 kernel: [    1.224721] usb usb2: Product: EHCI Host Controller
Oct 28 16:53:53 node-1 kernel: [    1.230199] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 28 16:53:53 node-1 kernel: [    1.235751] usb usb2: SerialNumber: 0000:00:1d.0
Oct 28 16:53:53 node-1 kernel: [    1.241311] hub 2-0:1.0: USB hub found
Oct 28 16:53:53 node-1 kernel: [    1.246663] hub 2-0:1.0: 2 ports detected
Oct 28 16:53:53 node-1 kernel: [    1.251977] ehci-platform: EHCI generic platform driver
Oct 28 16:53:53 node-1 kernel: [    1.257219] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 28 16:53:53 node-1 kernel: [    1.262536] ohci-pci: OHCI PCI platform driver
Oct 28 16:53:53 node-1 kernel: [    1.267842] ohci-platform: OHCI generic platform driver
Oct 28 16:53:53 node-1 kernel: [    1.273061] uhci_hcd: USB Universal Host Controller Interface driver
Oct 28 16:53:53 node-1 kernel: [    1.278405] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 28 16:53:53 node-1 kernel: [    1.471436] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 28 16:53:53 node-1 kernel: [    1.779167] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct 28 16:53:53 node-1 kernel: [    1.803513] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 28 16:53:53 node-1 kernel: [    1.809143] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 28 16:53:53 node-1 kernel: [    1.814904] hub 1-1:1.0: USB hub found
Oct 28 16:53:53 node-1 kernel: [    1.820497] hub 1-1:1.0: 6 ports detected
Oct 28 16:53:53 node-1 kernel: [    1.935041] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 28 16:53:53 node-1 kernel: [    2.317233] i8042: No controller found
Oct 28 16:53:53 node-1 kernel: [    2.322768] mousedev: PS/2 mouse device common for all mice
Oct 28 16:53:53 node-1 kernel: [    2.328494] rtc_cmos 00:02: RTC can wake from S4
Oct 28 16:53:53 node-1 kernel: [    2.331636] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 28 16:53:53 node-1 kernel: [    2.331637] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 28 16:53:53 node-1 kernel: [    2.332269] hub 2-1:1.0: USB hub found
Oct 28 16:53:53 node-1 kernel: [    2.332503] hub 2-1:1.0: 8 ports detected
Oct 28 16:53:53 node-1 kernel: [    2.356824] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 28 16:53:53 node-1 kernel: [    2.362574] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 28 16:53:53 node-1 kernel: [    2.373892] device-mapper: uevent: version 1.0.3
Oct 28 16:53:53 node-1 kernel: [    2.379614] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 28 16:53:53 node-1 kernel: [    2.391005] ledtrig-cpu: registered to indicate activity on CPUs
Oct 28 16:53:53 node-1 kernel: [    2.396979] TCP: cubic registered
Oct 28 16:53:53 node-1 kernel: [    2.402853] NET: Registered protocol family 10
Oct 28 16:53:53 node-1 kernel: [    2.408942] NET: Registered protocol family 17
Oct 28 16:53:53 node-1 kernel: [    2.414722] Key type dns_resolver registered
Oct 28 16:53:53 node-1 kernel: [    2.420808] Loading compiled-in X.509 certificates
Oct 28 16:53:53 node-1 kernel: [    2.427045] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Oct 28 16:53:53 node-1 kernel: [    2.438719] registered taskstats version 1
Oct 28 16:53:53 node-1 kernel: [    2.446869] Key type trusted registered
Oct 28 16:53:53 node-1 kernel: [    2.454596] Key type encrypted registered
Oct 28 16:53:53 node-1 kernel: [    2.460105] AppArmor: AppArmor sha1 policy hashing enabled
Oct 28 16:53:53 node-1 kernel: [    2.465653] IMA: No TPM chip found, activating TPM-bypass!
Oct 28 16:53:53 node-1 kernel: [    2.471757] regulator-dummy: disabling
Oct 28 16:53:53 node-1 kernel: [    2.477290]   Magic number: 4:167:895
Oct 28 16:53:53 node-1 kernel: [    2.483052] rtc_cmos 00:02: setting system clock to 2016-10-28 16:53:17 UTC (1477673597)
Oct 28 16:53:53 node-1 kernel: [    2.495572] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 28 16:53:53 node-1 kernel: [    2.501251] EDD information not available.
Oct 28 16:53:53 node-1 kernel: [    2.506889] PM: Hibernation image not present or could not be loaded.
Oct 28 16:53:53 node-1 kernel: [    2.507749] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 28 16:53:53 node-1 kernel: [    2.519093] Write protecting the kernel read-only data: 12288k
Oct 28 16:53:53 node-1 kernel: [    2.525409] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 28 16:53:53 node-1 kernel: [    2.538548] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 28 16:53:53 node-1 kernel: [    2.570730] device-mapper: multipath: version 1.6.0 loaded
Oct 28 16:53:53 node-1 kernel: [    2.578671] systemd-udevd[215]: starting version 204
Oct 28 16:53:53 node-1 kernel: [    2.602994] md: linear personality registered for level -1
Oct 28 16:53:53 node-1 kernel: [    2.610901] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 28 16:53:53 node-1 kernel: [    2.622813] md: multipath personality registered for level -4
Oct 28 16:53:53 node-1 kernel: [    2.630935] md: raid0 personality registered for level 0
Oct 28 16:53:53 node-1 kernel: [    2.639233] md: raid1 personality registered for level 1
Oct 28 16:53:53 node-1 kernel: [    2.650325] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 28 16:53:53 node-1 kernel: [    2.656758] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 28 16:53:53 node-1 kernel: [    2.663077] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 28 16:53:53 node-1 kernel: [    2.667493] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Oct 28 16:53:53 node-1 kernel: [    2.667522] 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 16:53:53 node-1 kernel: [    2.667523] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 28 16:53:53 node-1 kernel: [    2.667810] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.667968] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.668011] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.668098] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.668318] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.683572] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Oct 28 16:53:53 node-1 kernel: [    2.683584] 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 16:53:53 node-1 kernel: [    2.683585] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 28 16:53:53 node-1 kernel: [    2.683751] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.683836] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.683953] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.684045] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.684155] enic 0000:07:00.0: irq 104 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.684273] enic 0000:07:00.0: irq 105 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.684478] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.702032] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Oct 28 16:53:53 node-1 kernel: [    2.702044] 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 16:53:53 node-1 kernel: [    2.702045] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 28 16:53:53 node-1 kernel: [    2.702211] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.702277] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.702382] enic 0000:08:00.0: irq 108 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.702608] enic 0000:08:00.0: irq 109 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.702896] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.714600] raid6: sse2x1     703 MB/s
Oct 28 16:53:53 node-1 kernel: [    2.717003] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Oct 28 16:53:53 node-1 kernel: [    2.717015] 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 16:53:53 node-1 kernel: [    2.717031] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 28 16:53:53 node-1 kernel: [    2.717337] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.717461] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.717615] enic 0000:09:00.0: irq 112 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.717764] enic 0000:09:00.0: irq 113 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.717964] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 28 16:53:53 node-1 kernel: [    2.782480] raid6: sse2x2     426 MB/s
Oct 28 16:53:53 node-1 kernel: [    2.850485] raid6: sse2x4     548 MB/s
Oct 28 16:53:53 node-1 kernel: [    2.918222] raid6: avx2x1    9602 MB/s
Oct 28 16:53:53 node-1 kernel: [    2.990159] raid6: avx2x2   18874 MB/s
Oct 28 16:53:53 node-1 kernel: [    3.062086] raid6: avx2x4   21265 MB/s
Oct 28 16:53:53 node-1 kernel: [    3.067941] raid6: using algorithm avx2x4 (21265 MB/s)
Oct 28 16:53:53 node-1 kernel: [    3.073940] raid6: using avx2x2 recovery algorithm
Oct 28 16:53:53 node-1 kernel: [    3.079805] Switched to clocksource tsc
Oct 28 16:53:53 node-1 kernel: [    3.079839] megasas: FW now in Ready state
Oct 28 16:53:53 node-1 kernel: [    3.079907] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    3.079918] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    3.079957] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    3.079973] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    3.080007] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    3.080041] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    3.080064] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    3.080100] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    3.080134] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    3.080172] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    3.080208] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    3.080232] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    3.080259] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    3.080263] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    3.080266] megaraid_sas 0000:01:00.0: irq 128 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    3.080270] megaraid_sas 0000:01:00.0: irq 129 for MSI/MSI-X
Oct 28 16:53:53 node-1 kernel: [    3.080429] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 28 16:53:53 node-1 kernel: [    3.102317] xor: automatically using best checksumming function:
Oct 28 16:53:53 node-1 kernel: [    3.141755] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 28 16:53:53 node-1 kernel: [    3.146073]    avx       : 36584.000 MB/sec
Oct 28 16:53:53 node-1 kernel: [    3.153266] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 28 16:53:53 node-1 kernel: [    3.164572] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 28 16:53:53 node-1 kernel: [    3.170239] usb 2-1.4: Manufacturer: Avocent
Oct 28 16:53:53 node-1 kernel: [    3.175714] async_tx: api initialized (async)
Oct 28 16:53:53 node-1 kernel: [    3.175716] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 28 16:53:53 node-1 kernel: [    3.188087] hidraw: raw HID events driver (C) Jiri Kosina
Oct 28 16:53:53 node-1 kernel: [    3.195496] md: raid6 personality registered for level 6
Oct 28 16:53:53 node-1 kernel: [    3.201017] md: raid5 personality registered for level 5
Oct 28 16:53:53 node-1 kernel: [    3.201021] usbcore: registered new interface driver usbhid
Oct 28 16:53:53 node-1 kernel: [    3.201022] usbhid: USB HID core driver
Oct 28 16:53:53 node-1 kernel: [    3.216630] md: raid4 personality registered for level 4
Oct 28 16:53:53 node-1 kernel: [    3.222642] 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 16:53:53 node-1 kernel: [    3.233070] 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 16:53:53 node-1 kernel: [    3.243961] md: raid10 personality registered for level 10
Oct 28 16:53:53 node-1 kernel: [    3.244015] 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 16:53:53 node-1 kernel: [    3.244076] 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 16:53:53 node-1 kernel: [    3.244131] 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 16:53:53 node-1 kernel: [    3.244184] 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 16:53:53 node-1 kernel: [    3.352240] multipathd (354): /proc/354/oom_adj is deprecated, please use /proc/354/oom_score_adj instead.
Oct 28 16:53:53 node-1 kernel: [    3.437805] megasas:IOC Init cmd success
Oct 28 16:53:53 node-1 kernel: [    3.489772] megasas: INIT adapter done
Oct 28 16:53:53 node-1 kernel: [    3.565699] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 28 16:53:53 node-1 kernel: [    3.572795] scsi0 : LSI SAS based MegaRAID driver
Oct 28 16:53:53 node-1 kernel: [    3.580521] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 28 16:53:53 node-1 kernel: [    3.600281] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 28 16:53:53 node-1 kernel: [    3.617391] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 28 16:53:53 node-1 kernel: [    3.624686] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 28 16:53:53 node-1 kernel: [    3.639089] sd 0:2:0:0: [sda] Write Protect is off
Oct 28 16:53:53 node-1 kernel: [    3.646093] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 28 16:53:53 node-1 kernel: [    3.646112] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 28 16:53:53 node-1 kernel: [    3.689802]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Oct 28 16:53:53 node-1 kernel: [    3.697225] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 28 16:53:53 node-1 kernel: [    3.827515] random: lvm urandom read with 29 bits of entropy available
Oct 28 16:53:53 node-1 kernel: [    4.002553] bio: create slab <bio-1> at 1
Oct 28 16:53:53 node-1 kernel: [    4.859281] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 16:53:53 node-1 kernel: [    5.469359] random: nonblocking pool is initialized
Oct 28 16:53:53 node-1 kernel: [    5.627608] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Oct 28 16:53:53 node-1 kernel: [    5.652561] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 28 16:53:53 node-1 kernel: [    5.803323] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 28 16:53:53 node-1 kernel: [    5.839291] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 28 16:53:53 node-1 kernel: [    5.896939] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 16:53:53 node-1 kernel: [    6.095631] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 28 16:53:53 node-1 kernel: [    6.146349] XFS (dm-1): Mounting Filesystem
Oct 28 16:53:53 node-1 kernel: [    6.401299] XFS (dm-1): Ending clean mount
Oct 28 16:53:53 node-1 kernel: [    6.465816] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 16:53:53 node-1 kernel: [    6.497787] XFS (dm-2): Mounting Filesystem
Oct 28 16:53:53 node-1 kernel: [    6.582721] XFS (dm-2): Ending clean mount
Oct 28 16:53:53 node-1 kernel: [    6.745753] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Oct 28 16:53:53 node-1 kernel: [    8.954055] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 28 16:53:53 node-1 kernel: [    8.979828] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 28 16:53:53 node-1 kernel: [    9.214028] systemd-udevd[800]: starting version 204
Oct 28 16:53:53 node-1 kernel: [    9.489524] wmi: Mapper loaded
Oct 28 16:53:53 node-1 kernel: [    9.502694] power_meter ACPI000D:00: Found ACPI power meter.
Oct 28 16:53:53 node-1 kernel: [    9.502702] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 28 16:53:53 node-1 kernel: [    9.518909] IPMI System Interface driver.
Oct 28 16:53:53 node-1 kernel: [    9.518952] ipmi_si: probing via ACPI
Oct 28 16:53:53 node-1 kernel: [    9.518963] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 28 16:53:53 node-1 kernel: [    9.518964] ipmi_si: Adding ACPI-specified kcs state machine
Oct 28 16:53:53 node-1 kernel: [    9.518972] ipmi_si: probing via SMBIOS
Oct 28 16:53:53 node-1 kernel: [    9.518973] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 28 16:53:53 node-1 kernel: [    9.518973] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 28 16:53:53 node-1 kernel: [    9.518975] ipmi_si: probing via SPMI
Oct 28 16:53:53 node-1 kernel: [    9.518976] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 28 16:53:53 node-1 kernel: [    9.518976] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 28 16:53:53 node-1 kernel: [    9.518977] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 28 16:53:53 node-1 kernel: [    9.550391] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 28 16:53:53 node-1 kernel: [    9.550396] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 28 16:53:53 node-1 kernel: [    9.550399] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 28 16:53:53 node-1 kernel: [    9.550400] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 28 16:53:53 node-1 kernel: [    9.550427] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 28 16:53:53 node-1 kernel: [    9.579702] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 28 16:53:53 node-1 kernel: [    9.640995] systemd-udevd[817]: renamed network interface eth2 to enp8s0
Oct 28 16:53:53 node-1 kernel: [    9.657820] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 28 16:53:53 node-1 kernel: [    9.657826] ipmi_si 00:09: IPMI kcs interface initialized
Oct 28 16:53:53 node-1 kernel: [    9.664952] systemd-udevd[819]: renamed network interface eth1 to enp7s0
Oct 28 16:53:53 node-1 kernel: [    9.696862] systemd-udevd[818]: renamed network interface eth3 to enp9s0
Oct 28 16:53:53 node-1 kernel: [    9.744825] systemd-udevd[829]: renamed network interface eth0 to enp6s0
Oct 28 16:53:53 node-1 kernel: [   10.096877] type=1400 audit(1477673605.117:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1079 comm="apparmor_parser"
Oct 28 16:53:53 node-1 kernel: [   10.097038] type=1400 audit(1477673605.117:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1079 comm="apparmor_parser"
Oct 28 16:53:53 node-1 kernel: [   10.097168] type=1400 audit(1477673605.117:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1079 comm="apparmor_parser"
Oct 28 16:53:53 node-1 kernel: [   10.115289] type=1400 audit(1477673605.133:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1082 comm="apparmor_parser"
Oct 28 16:53:53 node-1 kernel: [   10.115435] type=1400 audit(1477673605.133:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1082 comm="apparmor_parser"
Oct 28 16:53:53 node-1 kernel: [   10.115572] type=1400 audit(1477673605.133:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1082 comm="apparmor_parser"
Oct 28 16:53:53 node-1 kernel: [   10.115661] type=1400 audit(1477673605.133:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1081 comm="apparmor_parser"
Oct 28 16:53:53 node-1 kernel: [   10.115814] type=1400 audit(1477673605.133:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1081 comm="apparmor_parser"
Oct 28 16:53:53 node-1 kernel: [   10.115936] type=1400 audit(1477673605.133:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1081 comm="apparmor_parser"
Oct 28 16:53:53 node-1 kernel: [   10.127378] type=1400 audit(1477673605.145:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1080 comm="apparmor_parser"
Oct 28 16:53:53 node-1 kernel: [   10.547542] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct 28 16:53:53 node-1 kernel: [   10.548272] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct 28 16:53:53 node-1 kernel: [   10.748527] enic 0000:06:00.0 enp6s0: Link UP
Oct 28 16:53:53 node-1 kernel: [   10.748950] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 28 16:53:53 node-1 kernel: [   10.748956] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 28 16:53:53 node-1 kernel: [   21.036553] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 28 16:53:55 node-1 failsafe: Failsafe of 120 seconds reached.
Oct 28 16:53:55 node-1 kernel: [   40.269924] init: failsafe main process (8452) killed by TERM signal
Oct 28 16:53:55 node-1 dbus[8518]: [system] AppArmor D-Bus mediation is enabled
Oct 28 16:53:55 node-1 kernel: [   40.483716] audit_printk_skb: 30 callbacks suppressed
Oct 28 16:53:55 node-1 kernel: [   40.483718] type=1400 audit(1477673635.438:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8570 comm="apparmor_parser"
Oct 28 16:53:55 node-1 kernel: [   40.483722] type=1400 audit(1477673635.438:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8570 comm="apparmor_parser"
Oct 28 16:53:55 node-1 kernel: [   40.483725] type=1400 audit(1477673635.438:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8570 comm="apparmor_parser"
Oct 28 16:53:55 node-1 kernel: [   40.483947] type=1400 audit(1477673635.438:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8570 comm="apparmor_parser"
Oct 28 16:53:55 node-1 kernel: [   40.483949] type=1400 audit(1477673635.438:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8570 comm="apparmor_parser"
Oct 28 16:53:55 node-1 kernel: [   40.484063] type=1400 audit(1477673635.438:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8570 comm="apparmor_parser"
Oct 28 16:53:55 node-1 kernel: [   40.485561] type=1400 audit(1477673635.438:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8571 comm="apparmor_parser"
Oct 28 16:53:55 node-1 kernel: [   40.556682] type=1400 audit(1477673635.510:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8573 comm="apparmor_parser"
Oct 28 16:53:55 node-1 cron[8611]: (CRON) INFO (pidfile fd = 3)
Oct 28 16:53:55 node-1 anacron[8646]: Anacron 2.3 started on 2016-10-28
Oct 28 16:53:55 node-1 cron[8651]: (CRON) STARTUP (fork ok)
Oct 28 16:53:55 node-1 anacron[8646]: Will run job `cron.daily' in 5 min.
Oct 28 16:53:55 node-1 anacron[8646]: Will run job `cron.weekly' in 10 min.
Oct 28 16:53:55 node-1 anacron[8646]: Will run job `cron.monthly' in 15 min.
Oct 28 16:53:55 node-1 anacron[8646]: Jobs will be executed sequentially
Oct 28 16:53:55 node-1 multipathd: path checkers start up
Oct 28 16:53:55 node-1 cron[8651]: (CRON) INFO (Running @reboot jobs)
Oct 28 16:53:56 node-1 postfix/master[8790]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 28 16:53:59 node-1 puppet-agent[8974]: Reopening log files
Oct 28 16:54:00 node-1 puppet-agent[8974]: Could not request certificate: Connection refused - connect(2)
Oct 28 16:54:01 node-1 CRON[9005]: (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 16:54:11 node-1 puppet-user[9064]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 28 16:54:11 node-1 puppet-user[9064]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct 28 16:54:12 node-1 puppet-user[9064]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 28 16:54:12 node-1 puppet-user[9064]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 28 16:54:12 node-1 puppet-user[9064]: Finished catalog run in 1.05 seconds
Oct 28 16:54:13 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 28 16:54:14 node-1 multipathd: uevent trigger error
Oct 28 16:54:14 node-1 nailgun-agent: D, [2016-10-28T16:54:01.957993 #9008] DEBUG -- : Sleep for 12 seconds before sending request
Oct 28 16:54:14 node-1 nailgun-agent: I, [2016-10-28T16:54:13.989569 #9008]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 28 16:54:14 node-1 puppet-user[9499]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 28 16:54:14 node-1 puppet-user[9499]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Oct 28 16:54:14 node-1 puppet-user[9499]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 28 16:54:14 node-1 puppet-user[9499]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 28 16:54:14 node-1 puppet-user[9499]: (/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 16:54:14 node-1 puppet-user[9499]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 28 16:54:14 node-1 puppet-user[9499]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 28 16:54:14 node-1 puppet-user[9499]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 28 16:54:14 node-1 puppet-user[9499]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 28 16:54:14 node-1 puppet-user[9499]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 28 16:54:14 node-1 puppet-user[9499]: Finished catalog run in 0.07 seconds
Oct 28 16:54:14 node-1 nailgun-agent: D, [2016-10-28T16:54:14.950563 #9008] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Oct 28 16:54:15 node-1 puppet-user[10083]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 28 16:54:15 node-1 puppet-user[10083]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct 28 16:54:15 node-1 puppet-user[10083]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 28 16:54:15 node-1 puppet-user[10083]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 28 16:54:15 node-1 puppet-user[10083]: Finished catalog run in 0.05 seconds
Oct 28 16:54:17 node-1 puppet-user[10557]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 28 16:54:17 node-1 puppet-user[10557]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 28 16:54:17 node-1 puppet-user[10557]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 28 16:54:17 node-1 puppet-user[10557]: Finished catalog run in 0.03 seconds
Oct 28 16:54:19 node-1 puppet-user[11020]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 28 16:54:19 node-1 puppet-user[11020]: Compiled catalog for node-1.domain.tld in environment production in 0.22 seconds
Oct 28 16:54:19 node-1 puppet-user[11020]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 28 16:54:19 node-1 puppet-user[11020]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Oct 28 16:54:20 node-1 puppet-user[11020]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Oct 28 16:54:20 node-1 puppet-user[11020]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/bgpvpn-0.9/]/Exec[rsync /etc/fuel/plugins/bgpvpn-0.9/]/returns) executed successfully
Oct 28 16:54:20 node-1 puppet-user[11020]: Finished catalog run in 1.20 seconds
Oct 28 16:54:21 node-1 puppet-user[11557]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 28 16:54:22 node-1 puppet-user[11557]: Compiled catalog for node-1.domain.tld in environment production in 0.25 seconds
Oct 28 16:54:22 node-1 puppet-user[11557]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Oct 28 16:54:22 node-1 puppet-user[11557]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[bgpvpn-0.9.0]/Apt::Setting[list-bgpvpn-0.9.0]/File[/etc/apt/sources.list.d/bgpvpn-0.9.0.list]/ensure) created
Oct 28 16:54:22 node-1 puppet-user[11557]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 28 16:54:22 node-1 puppet-user[11557]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 28 16:54:22 node-1 puppet-user[11557]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Oct 28 16:54:22 node-1 puppet-user[11557]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 28 16:54:22 node-1 puppet-user[11557]: Finished catalog run in 0.43 seconds
Oct 28 16:54:24 node-1 puppet-user[12171]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 28 16:54:24 node-1 puppet-user[12171]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Oct 28 16:54:24 node-1 puppet-user[12171]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 28 16:54:24 node-1 kernel: [   69.515949] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 28 16:54:24 node-1 kernel: [   69.515996] 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 16:54:24 node-1 puppet-user[12171]: (/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 16:54:24 node-1 puppet-user[12171]: Finished catalog run in 0.06 seconds
Oct 28 16:54:26 node-1 puppet-user[12630]: (Scope(Class[main])) MODULAR: sync_time
Oct 28 16:54:26 node-1 puppet-user[12630]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct 28 16:54:26 node-1 ntpdate[13053]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.014845 #9008] DEBUG -- : Trying to find block devices
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.014919 #9008] DEBUG -- : Found block device: sda
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.014957 #9008] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.014997 #9008] DEBUG -- : Trying to get list of physical devices
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.015148 #9008] DEBUG -- : Getting udev properties for device: sda
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.017112 #9008] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0 /dev/disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"00c001b0054d88c71c90a8737283728e", "ID_SERIAL"=>"3618e72837273a8901cc7884d05b001c0", "ID_SERIAL_SHORT"=>"618e72837273a8901cc7884d05b001c0", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a890", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7884d05b001c0", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a8901cc7884
Oct 28 16:54:27 node-1 nailgun-agent: d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51529", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.017139 #9008] DEBUG -- : Trying to find out if device sda is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.017180 #9008] DEBUG -- : Device sda removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.017195 #9008] DEBUG -- : Device sda seems to be appropriate
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.017639 #9008] DEBUG -- : Getting udev properties for device: dm-0
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.019194 #9008] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-UyWFBHZ3MLg1TNRVM7Wgd9NLH7tBeKQKgExJYmU83OFllEBPH2tzSnMpFAEipuXq /dev/disk/by-uuid/ed7c5922-9b1e-4299-b92a-5da9fdfcdcaa /dev/mapper/mongo-mongodb /dev/mongo/mongodb", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"mongodb", "DM_NAME"=>"mongo-mongodb", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-UyWFBHZ3MLg1TNRVM7Wgd9NLH7tBeKQKgExJYmU83OFllEBPH2tzSnMpFAEipuXq", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ed7c5922-9b1e-4299-b92a-5da9fdfcdcaa", "ID_FS_UUID_ENC"=>"ed7c5922-9b1e-4299-b92a-5da9fdfcdcaa", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57
Oct 28 16:54:27 node-1 nailgun-agent: 180", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.019221 #9008] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.019253 #9008] DEBUG -- : Device dm-0 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.019292 #9008] DEBUG -- : Device dm-0 seems to be appropriate
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.019307 #9008] DEBUG -- : Getting udev properties for device: dm-1
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.020876 #9008] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-ixXPWn3UlqYVeHWoau547gPO6GuFaBfvy7zeScoK6r4DoivKPYNEM3C1yWLCoQ2H /dev/disk/by-uuid/dfc5353d-d431-4ff8-b721-2ab8dddda4a9 /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-ixXPWn3UlqYVeHWoau547gPO6GuFaBfvy7zeScoK6r4DoivKPYNEM3C1yWLCoQ2H", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"dfc5353d-d431-4ff8-b721-2ab8dddda4a9", "ID_FS_UUID_ENC"=>"dfc5353d-d431-4ff8-b721-2ab8dddda4a9", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75975", "nomdmonddf"=>"1", "nomd
Oct 28 16:54:27 node-1 nailgun-agent: monisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.020913 #9008] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.020972 #9008] DEBUG -- : Device dm-1 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.020986 #9008] DEBUG -- : Device dm-1 seems to be appropriate
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.021001 #9008] DEBUG -- : Getting udev properties for device: dm-2
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.022523 #9008] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-BkhqwilA0Y8u4Z7oBB5n7ZgM8g1WPHqQdUV9kH3NrGyq3XT4UJJm1ML0yo6JwuGP /dev/disk/by-uuid/19dbfc6c-fdab-491e-aa0d-c05b3cd7e7e6 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-BkhqwilA0Y8u4Z7oBB5n7ZgM8g1WPHqQdUV9kH3NrGyq3XT4UJJm1ML0yo6JwuGP", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"19dbfc6c-fdab-491e-aa0d-c05b3cd7e7e6", "ID_FS_UUID_ENC"=>"19dbfc6c-fdab-491e-aa0d-c05b3cd7e7e6", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97
Oct 28 16:54:27 node-1 nailgun-agent: 566", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.022549 #9008] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.022580 #9008] DEBUG -- : Device dm-2 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.022610 #9008] DEBUG -- : Device dm-2 seems to be appropriate
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.022625 #9008] DEBUG -- : Getting udev properties for device: dm-3
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.024183 #9008] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-goAuX9Bl2Q0pp6RPUUCWghg5hVouE3xqW0pZHJTIkm1A7nKlovFUMF2nCwidditg /dev/disk/by-uuid/13d0c4ed-620f-4643-957a-8f1e2fccf7b7 /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-goAuX9Bl2Q0pp6RPUUCWghg5hVouE3xqW0pZHJTIkm1A7nKlovFUMF2nCwidditg", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"13d0c4ed-620f-4643-957a-8f1e2fccf7b7", "ID_FS_UUID_ENC"=>"13d0c4ed-620f-4643-957a-8f1e2fccf7b7", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"945", "nomdmonddf
Oct 28 16:54:27 node-1 nailgun-agent: "=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.024211 #9008] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.024266 #9008] DEBUG -- : Device dm-3 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.024280 #9008] DEBUG -- : Device dm-3 seems to be appropriate
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.024296 #9008] DEBUG -- : Getting udev properties for device: dm-4
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.025930 #9008] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-hXaD7NEouXH1rr2gU9WSKw3qdbLWtM6hY84jYS7fpi4nhfvt99EltOTACGV3nDSF /dev/disk/by-uuid/3655c0d6-fe82-4e7c-9d4a-699c0704ba75 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-hXaD7NEouXH1rr2gU9WSKw3qdbLWtM6hY84jYS7fpi4nhfvt99EltOTACGV3nDSF", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"3655c0d6-fe82-4e7c-9d4a-699c0704ba75", "ID_FS_UUID_ENC"=>"3655c0d6-fe82-4e7c-9d4a-699c0704ba75", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"5901", "nomdmonddf"=>"1", "
Oct 28 16:54:27 node-1 nailgun-agent: nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.025977 #9008] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.026008 #9008] DEBUG -- : Device dm-4 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.026030 #9008] DEBUG -- : Device dm-4 seems to be appropriate
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.026056 #9008] DEBUG -- : Getting udev properties for device: dm-5
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.027554 #9008] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-j7BHt2v7dv6g2u6tgk2eQZ5aF0dY48HrzP1I22yoSXUCRwbRm8AZlpg6KEdINP5O /dev/disk/by-uuid/afdbeedb-22e7-470e-bad6-fe5716245850 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-j7BHt2v7dv6g2u6tgk2eQZ5aF0dY48HrzP1I22yoSXUCRwbRm8AZlpg6KEdINP5O", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"afdbeedb-22e7-470e-bad6-fe5716245850", "ID_FS_UUID_ENC"=>"afdbeedb-22e7-470e-bad6-fe5716245850", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"10771", "nomdmonddf"=>"1", "nomd
Oct 28 16:54:27 node-1 nailgun-agent: monisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.027580 #9008] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.027653 #9008] DEBUG -- : Device dm-5 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.027667 #9008] DEBUG -- : Device dm-5 seems to be appropriate
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.027682 #9008] DEBUG -- : Getting udev properties for device: dm-6
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.029242 #9008] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-j7BHt2v7dv6g2u6tgk2eQZ5aF0dY48HrwshKm5e774VBL9Ctx6BGPOl1bMhpPdwl /dev/disk/by-uuid/be77f9c1-bedd-4402-b2da-aa0d0251fad0 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-6", "DEVPATH"=>"/devices/virtual/block/dm-6", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-j7BHt2v7dv6g2u6tgk2eQZ5aF0dY48HrwshKm5e774VBL9Ctx6BGPOl1bMhpPdwl", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"be77f9c1-bedd-4402-b2da-aa0d0251fad0", "ID_FS_UUID_ENC"=>"be77f9c1-bedd-4402-b2da-aa0d0251fad0", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"11239", "nomdmonddf"=>"1", "nomdmonisw"
Oct 28 16:54:27 node-1 nailgun-agent: =>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.029265 #9008] DEBUG -- : Trying to find out if device dm-6 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.029305 #9008] DEBUG -- : Device dm-6 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.029318 #9008] DEBUG -- : Device dm-6 seems to be appropriate
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.029331 #9008] DEBUG -- : Getting udev properties for device: ram0
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.030715 #9008] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"30145", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.030736 #9008] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.030783 #9008] DEBUG -- : Device ram0 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.030801 #9008] DEBUG -- : Getting udev properties for device: ram1
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.032175 #9008] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"30258", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.032203 #9008] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.032236 #9008] DEBUG -- : Device ram1 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.032260 #9008] DEBUG -- : Getting udev properties for device: ram2
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.033620 #9008] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"30907", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.033649 #9008] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.033678 #9008] DEBUG -- : Device ram2 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.033719 #9008] DEBUG -- : Getting udev properties for device: ram3
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.035095 #9008] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"30992", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.035124 #9008] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.035163 #9008] DEBUG -- : Device ram3 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.035182 #9008] DEBUG -- : Getting udev properties for device: ram4
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.036530 #9008] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31088", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.036551 #9008] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.036580 #9008] DEBUG -- : Device ram4 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.036607 #9008] DEBUG -- : Getting udev properties for device: ram5
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.037976 #9008] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31149", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.037995 #9008] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.038024 #9008] DEBUG -- : Device ram5 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.038041 #9008] DEBUG -- : Getting udev properties for device: ram6
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.039382 #9008] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31209", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.039413 #9008] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.039443 #9008] DEBUG -- : Device ram6 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.039467 #9008] DEBUG -- : Getting udev properties for device: ram7
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.040857 #9008] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31275", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.040886 #9008] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.040917 #9008] DEBUG -- : Device ram7 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.040935 #9008] DEBUG -- : Getting udev properties for device: ram8
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.042288 #9008] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31350", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.042308 #9008] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.042347 #9008] DEBUG -- : Device ram8 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.042364 #9008] DEBUG -- : Getting udev properties for device: ram9
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.043694 #9008] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31473", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.043713 #9008] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.043758 #9008] DEBUG -- : Device ram9 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.043775 #9008] DEBUG -- : Getting udev properties for device: loop0
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.045130 #9008] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"29403", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.045150 #9008] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.045191 #9008] DEBUG -- : Device loop0 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.045209 #9008] DEBUG -- : Getting udev properties for device: loop1
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.046534 #9008] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"29478", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.046553 #9008] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.046582 #9008] DEBUG -- : Device loop1 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.046609 #9008] DEBUG -- : Getting udev properties for device: loop2
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.047924 #9008] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"29568", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.047953 #9008] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.047987 #9008] DEBUG -- : Device loop2 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.051648 #9008] DEBUG -- : Getting udev properties for device: loop3
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.053189 #9008] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"29657", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.053210 #9008] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.053241 #9008] DEBUG -- : Device loop3 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.053259 #9008] DEBUG -- : Getting udev properties for device: loop4
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.054640 #9008] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"29747", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.054659 #9008] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.054687 #9008] DEBUG -- : Device loop4 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.054704 #9008] DEBUG -- : Getting udev properties for device: loop5
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.056100 #9008] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"29825", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.056120 #9008] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.056150 #9008] DEBUG -- : Device loop5 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.056167 #9008] DEBUG -- : Getting udev properties for device: loop6
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.057529 #9008] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"29900", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.057548 #9008] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.057578 #9008] DEBUG -- : Device loop6 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.057594 #9008] DEBUG -- : Getting udev properties for device: loop7
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.058982 #9008] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"29998", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.059002 #9008] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.059033 #9008] DEBUG -- : Device loop7 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.059049 #9008] DEBUG -- : Getting udev properties for device: ram10
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.060397 #9008] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"30383", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.060417 #9008] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.060444 #9008] DEBUG -- : Device ram10 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.060461 #9008] DEBUG -- : Getting udev properties for device: ram11
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.061831 #9008] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"30488", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.061851 #9008] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.061887 #9008] DEBUG -- : Device ram11 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.061903 #9008] DEBUG -- : Getting udev properties for device: ram12
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.063219 #9008] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"30612", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.063240 #9008] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.063322 #9008] DEBUG -- : Device ram12 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.063338 #9008] DEBUG -- : Getting udev properties for device: ram13
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.064694 #9008] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"30697", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.064750 #9008] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.064792 #9008] DEBUG -- : Device ram13 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.064808 #9008] DEBUG -- : Getting udev properties for device: ram14
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.066129 #9008] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"30772", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.066195 #9008] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.066236 #9008] DEBUG -- : Device ram14 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.066253 #9008] DEBUG -- : Getting udev properties for device: ram15
Oct 28 16:54:27 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067599 #9008] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"30823", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067660 #9008] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067704 #9008] DEBUG -- : Device ram15 removable parameter: "0"
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067735 #9008] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0"}]
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067748 #9008] DEBUG -- : Block device seems to be physical data storage: sda
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067792 #9008] DEBUG -- : Found block device: dm-0
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067805 #9008] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067817 #9008] DEBUG -- : Found block device: dm-1
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067827 #9008] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067875 #9008] DEBUG -- : Found block device: dm-2
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067885 #9008] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067894 #9008] DEBUG -- : Found block device: dm-3
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067903 #9008] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067912 #9008] DEBUG -- : Found block device: dm-4
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067921 #9008] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067930 #9008] DEBUG -- : Found block device: dm-5
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067939 #9008] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067985 #9008] DEBUG -- : Found block device: dm-6
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.067996 #9008] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068005 #9008] DEBUG -- : Found block device: ram0
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068014 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068021 #9008] DEBUG -- : Found block device: ram1
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068030 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068040 #9008] DEBUG -- : Found block device: ram2
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068049 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068057 #9008] DEBUG -- : Found block device: ram3
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068092 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068100 #9008] DEBUG -- : Found block device: ram4
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068110 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068118 #9008] DEBUG -- : Found block device: ram5
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068126 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068135 #9008] DEBUG -- : Found block device: ram6
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068144 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068152 #9008] DEBUG -- : Found block device: ram7
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068162 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068197 #9008] DEBUG -- : Found block device: ram8
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068206 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068215 #9008] DEBUG -- : Found block device: ram9
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068224 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068232 #9008] DEBUG -- : Found block device: loop0
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068241 #9008] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068250 #9008] DEBUG -- : Found block device: loop1
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068259 #9008] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068267 #9008] DEBUG -- : Found block device: loop2
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068276 #9008] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068308 #9008] DEBUG -- : Found block device: loop3
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068318 #9008] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068326 #9008] DEBUG -- : Found block device: loop4
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068335 #9008] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068343 #9008] DEBUG -- : Found block device: loop5
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068354 #9008] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068362 #9008] DEBUG -- : Found block device: loop6
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068372 #9008] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068386 #9008] DEBUG -- : Found block device: loop7
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068412 #9008] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068421 #9008] DEBUG -- : Found block device: ram10
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068431 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068440 #9008] DEBUG -- : Found block device: ram11
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068450 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068458 #9008] DEBUG -- : Found block device: ram12
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068468 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068476 #9008] DEBUG -- : Found block device: ram13
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068486 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068494 #9008] DEBUG -- : Found block device: ram14
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068531 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068541 #9008] DEBUG -- : Found block device: ram15
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068550 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.068576 #9008] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.149035 #9008] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Oct 28 16:54:27 node-1 nailgun-agent: D, [2016-10-28T16:54:27.149107 #9008] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct 28 16:54:32 node-1 ntpdate[13053]: adjust time server 10.20.0.2 offset 0.001967 sec
Oct 28 16:54:32 node-1 puppet-user[12630]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 28 16:54:32 node-1 puppet-user[12630]: Finished catalog run in 6.18 seconds
Oct 28 16:54:37 node-1 puppet-user[13624]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 28 16:54:38 node-1 puppet-user[13624]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Oct 28 16:54:38 node-1 puppet-user[13624]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 28 16:54:38 node-1 puppet-user[13624]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/bgpvpn", "plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Oct 28 16:54:38 node-1 puppet-user[13624]: Finished catalog run in 0.09 seconds
Oct 28 16:54:39 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022508 #9008] DEBUG -- : Trying to find block devices
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022568 #9008] DEBUG -- : Found block device: sda
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022595 #9008] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022613 #9008] DEBUG -- : Block device seems to be physical data storage: sda
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022633 #9008] DEBUG -- : Found block device: dm-0
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022674 #9008] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022685 #9008] DEBUG -- : Found block device: dm-1
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022695 #9008] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022704 #9008] DEBUG -- : Found block device: dm-2
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022714 #9008] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022723 #9008] DEBUG -- : Found block device: dm-3
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022734 #9008] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022742 #9008] DEBUG -- : Found block device: dm-4
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022751 #9008] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022771 #9008] DEBUG -- : Found block device: dm-5
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022805 #9008] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022814 #9008] DEBUG -- : Found block device: dm-6
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022824 #9008] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022833 #9008] DEBUG -- : Found block device: ram0
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022842 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022850 #9008] DEBUG -- : Found block device: ram1
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022860 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022868 #9008] DEBUG -- : Found block device: ram2
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022877 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022884 #9008] DEBUG -- : Found block device: ram3
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022921 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022931 #9008] DEBUG -- : Found block device: ram4
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022940 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022947 #9008] DEBUG -- : Found block device: ram5
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022956 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022965 #9008] DEBUG -- : Found block device: ram6
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022974 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022982 #9008] DEBUG -- : Found block device: ram7
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022991 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.022998 #9008] DEBUG -- : Found block device: ram8
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023029 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023038 #9008] DEBUG -- : Found block device: ram9
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023047 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023055 #9008] DEBUG -- : Found block device: loop0
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023064 #9008] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023072 #9008] DEBUG -- : Found block device: loop1
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023080 #9008] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023089 #9008] DEBUG -- : Found block device: loop2
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023097 #9008] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023105 #9008] DEBUG -- : Found block device: loop3
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023135 #9008] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023145 #9008] DEBUG -- : Found block device: loop4
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023153 #9008] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023162 #9008] DEBUG -- : Found block device: loop5
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023170 #9008] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023178 #9008] DEBUG -- : Found block device: loop6
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023186 #9008] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023194 #9008] DEBUG -- : Found block device: loop7
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023203 #9008] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023211 #9008] DEBUG -- : Found block device: ram10
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023239 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023248 #9008] DEBUG -- : Found block device: ram11
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023257 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023264 #9008] DEBUG -- : Found block device: ram12
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023273 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023281 #9008] DEBUG -- : Found block device: ram13
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023290 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023298 #9008] DEBUG -- : Found block device: ram14
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023306 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023314 #9008] DEBUG -- : Found block device: ram15
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023341 #9008] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.023368 #9008] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Oct 28 16:54:39 node-1 nailgun-agent: D, [2016-10-28T16:54:39.195188 #9008] DEBUG -- : Response: status: 200 body: {"id": 1}
Oct 28 16:54:39 node-1 nailgun-agent: I, [2016-10-28T16:54:39.195339 #9008]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct 28 16:54:39 node-1 puppet-user[14089]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 28 16:54:40 node-1 puppet-user[14089]: Compiled catalog for node-1.domain.tld in environment production in 0.53 seconds
Oct 28 16:54:40 node-1 puppet-user[14089]: (/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 16:54:40 node-1 puppet-user[14089]: (/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 16:54:40 node-1 puppet-user[14089]: (/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 16:54:40 node-1 puppet-user[14089]: (/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 16:54:40 node-1 puppet-user[14089]: (/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 16:54:40 node-1 puppet-user[14089]: (/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 16:54:40 node-1 puppet-user[14089]: (/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 16:54:40 node-1 puppet-user[14089]: (/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 16:54:40 node-1 puppet-user[14089]: (/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 16:54:40 node-1 puppet-user[14089]: (/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 16:54:41 node-1 puppet-user[14089]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 28 16:54:41 node-1 puppet-user[14089]: Finished catalog run in 1.00 seconds
Oct 28 16:54:43 node-1 puppet-user[14717]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 28 16:54:43 node-1 puppet-user[14717]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Oct 28 16:54:46 node-1 kernel: [   91.101972] init: plymouth-upstart-bridge main process ended, respawning
Oct 28 16:54:46 node-1 puppet-agent[8974]: Could not run: SIGTERM
Oct 28 16:54:46 node-1 puppet-user[14717]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 28 16:54:46 node-1 kernel: [   91.465097] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 28 16:54:46 node-1 ec2: 
Oct 28 16:54:46 node-1 ec2: #############################################################
Oct 28 16:54:46 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 28 16:54:46 node-1 ec2: 1024 51:37:d8:d5:5f:e6:a7:9a:75:ce:fc:4a:94:22:4d:8d  root@node-1.domain.tld (DSA)
Oct 28 16:54:46 node-1 ec2: 256 cb:70:73:51:62:25:a9:f8:a2:4b:49:ad:f7:5d:f9:4f  root@node-1.domain.tld (ECDSA)
Oct 28 16:54:46 node-1 ec2: 256 64:28:52:e5:ae:01:bc:f5:02:dd:ac:e0:f3:79:1e:e2  root@node-1.domain.tld (ED25519)
Oct 28 16:54:46 node-1 ec2: 2048 92:46:5a:69:56:e2:e6:5a:95:ee:2b:fa:d2:2f:94:cc  root@node-1.domain.tld (RSA)
Oct 28 16:54:46 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 28 16:54:46 node-1 ec2: #############################################################
Oct 28 16:55:01 node-1 CRON[16483]: (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 16:55:16 node-1 puppet-user[14717]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 28 16:55:16 node-1 puppet-user[14717]: Finished catalog run in 32.80 seconds
Oct 28 16:55:18 node-1 puppet-user[17355]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 28 16:55:18 node-1 puppet-user[17355]: Compiled catalog for node-1.domain.tld in environment production in 0.53 seconds
Oct 28 16:55:18 node-1 puppet-user[17355]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 28 16:55:18 node-1 puppet-user[17355]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 28 16:55:18 node-1 puppet-user[17355]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 28 16:55:18 node-1 puppet-user[17355]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 28 16:55:18 node-1 puppet-user[17355]: Finished catalog run in 0.12 seconds
Oct 28 16:55:20 node-1 puppet-user[17829]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 28 16:55:21 node-1 puppet-user[17829]: Compiled catalog for node-1.domain.tld in environment production in 0.98 seconds
Oct 28 16:55:21 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 28 16:55:21 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 28 16:55:21 node-1 crontab[18267]: (root) LIST (root)
Oct 28 16:55:21 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 28 16:55:21 node-1 crontab[18268]: (root) REPLACE (root)
Oct 28 16:55:23 node-1 puppet-user[17829]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/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 16:55:24 node-1 puppet-user[17829]: (/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 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/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 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/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 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/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 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/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 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/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 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 28 16:55:24 node-1 puppet-user[17829]: (/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 16:55:24 node-1 puppet-user[17829]: (/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 16:55:24 node-1 puppet-user[17829]: (/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 16:55:24 node-1 puppet-user[17829]: (/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 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 28 16:55:24 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 28 16:55:25 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 28 16:55:25 node-1 puppet-user[17829]: (/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 16:55:25 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 28 16:55:25 node-1 puppet-user[17829]: (/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 16:55:25 node-1 puppet-user[17829]: (/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 16:55:25 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 28 16:55:25 node-1 puppet-user[17829]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 28 16:55:25 node-1 puppet-user[17829]: (/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 16:55:25 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8425" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 28 16:55:25 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 28 16:55:27 node-1 multipathd: uevent trigger error
<27>Oct 28 16:55:27 node-1 multipathd: uevent trigger error
<27>Oct 28 16:55:27 node-1 multipathd: uevent trigger error
<27>Oct 28 16:55:27 node-1 multipathd: uevent trigger error
<27>Oct 28 16:55:27 node-1 multipathd: uevent trigger error
<27>Oct 28 16:55:40 node-1 multipathd: uevent trigger error
<27>Oct 28 16:55:40 node-1 multipathd: uevent trigger error
<27>Oct 28 16:55:40 node-1 multipathd: uevent trigger error
<27>Oct 28 16:55:40 node-1 multipathd: uevent trigger error
<27>Oct 28 16:55:40 node-1 multipathd: uevent trigger error
<27>Oct 28 16:55:42 node-1 multipathd: uevent trigger error
<27>Oct 28 16:55:42 node-1 multipathd: uevent trigger error
<27>Oct 28 16:55:42 node-1 multipathd: uevent trigger error
<27>Oct 28 16:55:42 node-1 multipathd: uevent trigger error
<27>Oct 28 16:55:42 node-1 multipathd: uevent trigger error
<27>Oct 28 16:55:42 node-1 multipathd: uevent trigger error
<27>Oct 28 16:56:37 node-1 ntpdate[28181]: no servers can be used, exiting
<27>Oct 28 16:56:37 node-1 ntpdate[28352]: no servers can be used, exiting
<27>Oct 28 16:57:09 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:09 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:09 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:09 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:09 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:12 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:12 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:12 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:12 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:12 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:22 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:22 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:22 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:22 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:22 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:25 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:25 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:25 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:25 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:25 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:25 node-1 multipathd: uevent trigger error
<27>Oct 28 16:57:25 node-1 multipathd: uevent trigger error
<27>Oct 28 16:58:22 node-1 multipathd: uevent trigger error
<27>Oct 28 16:58:22 node-1 multipathd: uevent trigger error
<27>Oct 28 16:58:22 node-1 multipathd: uevent trigger error
<27>Oct 28 16:58:22 node-1 multipathd: uevent trigger error
<27>Oct 28 16:58:22 node-1 multipathd: uevent trigger error
<27>Oct 28 16:58:30 node-1 multipathd: uevent trigger error
<27>Oct 28 16:58:30 node-1 multipathd: uevent trigger error
<27>Oct 28 16:58:30 node-1 multipathd: uevent trigger error
<27>Oct 28 16:58:30 node-1 multipathd: uevent trigger error
<27>Oct 28 16:58:30 node-1 multipathd: uevent trigger error
<27>Oct 28 16:58:33 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 16:58:33 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 16:58:39 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 16:58:39 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 16:58:44 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 16:58:50 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 16:58:50 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 28 16:59:02 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:02 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:02 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:02 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:02 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:12 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:12 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:12 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:12 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:29 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:29 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:29 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:30 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:30 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:35 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:35 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:35 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:35 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:35 node-1 multipathd: uevent trigger error
<129>Oct 28 16:59:37 node-1 haproxy[18323]: 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 16:59:38 node-1 haproxy[18330]: 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 16:59:38 node-1 haproxy[18330]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 16:59:38 node-1 haproxy[18330]: proxy mysqld has no server available!
<27>Oct 28 16:59:41 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:41 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:41 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:41 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:41 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:41 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:41 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:44 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:44 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:44 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:44 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:44 node-1 multipathd: uevent trigger error
<129>Oct 28 16:59:46 node-1 haproxy[20687]: 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 16:59:47 node-1 haproxy[20697]: 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 16:59:47 node-1 haproxy[20697]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 16:59:47 node-1 haproxy[20697]: proxy mysqld has no server available!
<129>Oct 28 16:59:47 node-1 haproxy[20697]: 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 16:59:47 node-1 haproxy[20697]: 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 16:59:48 node-1 haproxy[20697]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 16:59:48 node-1 haproxy[20697]: proxy object-storage has no server available!
<27>Oct 28 16:59:49 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:49 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:49 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:49 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:49 node-1 multipathd: uevent trigger error
<129>Oct 28 16:59:52 node-1 haproxy[21933]: 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 16:59:52 node-1 haproxy[21933]: 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 16:59:52 node-1 haproxy[21933]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 16:59:52 node-1 haproxy[21933]: proxy neutron has no server available!
<129>Oct 28 16:59:52 node-1 haproxy[21933]: 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 16:59:52 node-1 haproxy[21933]: 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 16:59:52 node-1 haproxy[21933]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 16:59:52 node-1 haproxy[21933]: proxy mysqld has no server available!
<129>Oct 28 16:59:53 node-1 haproxy[21940]: 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 16:59:53 node-1 haproxy[21940]: 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 16:59:53 node-1 haproxy[21940]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 16:59:53 node-1 haproxy[21940]: proxy object-storage has no server available!
<27>Oct 28 16:59:55 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:55 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:55 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:55 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:55 node-1 multipathd: uevent trigger error
<27>Oct 28 16:59:55 node-1 multipathd: uevent trigger error
<129>Oct 28 16:59:57 node-1 haproxy[23193]: 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 16:59:57 node-1 haproxy[23193]: 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 16:59:57 node-1 haproxy[23193]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 16:59:57 node-1 haproxy[23193]: proxy keystone-1 has no server available!
<129>Oct 28 16:59:57 node-1 haproxy[23193]: 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 16:59:57 node-1 haproxy[23193]: 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 16:59:57 node-1 haproxy[23193]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 16:59:57 node-1 haproxy[23193]: proxy keystone-2 has no server available!
<129>Oct 28 16:59:58 node-1 haproxy[23197]: 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 16:59:58 node-1 haproxy[23197]: 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 16:59:58 node-1 haproxy[23197]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 16:59:58 node-1 haproxy[23197]: proxy neutron has no server available!
<129>Oct 28 16:59:58 node-1 haproxy[23197]: 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 16:59:58 node-1 haproxy[23197]: 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 16:59:58 node-1 haproxy[23197]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 16:59:58 node-1 haproxy[23197]: proxy mysqld has no server available!
<129>Oct 28 16:59:58 node-1 haproxy[23197]: 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 16:59:58 node-1 haproxy[23197]: 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 16:59:59 node-1 haproxy[23197]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 16:59:59 node-1 haproxy[23197]: proxy object-storage has no server available!
<27>Oct 28 17:00:00 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:00 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:00 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:00 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:00 node-1 multipathd: uevent trigger error
<129>Oct 28 17:00:02 node-1 haproxy[24447]: 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 17:00:02 node-1 haproxy[24447]: 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 17:00:02 node-1 haproxy[24447]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:02 node-1 haproxy[24447]: proxy keystone-1 has no server available!
<129>Oct 28 17:00:02 node-1 haproxy[24447]: 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 17:00:03 node-1 haproxy[24451]: 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 17:00:03 node-1 haproxy[24451]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:03 node-1 haproxy[24451]: proxy keystone-2 has no server available!
<129>Oct 28 17:00:03 node-1 haproxy[24451]: 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 17:00:03 node-1 haproxy[24451]: 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 17:00:03 node-1 haproxy[24451]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:03 node-1 haproxy[24451]: proxy neutron has no server available!
<129>Oct 28 17:00:03 node-1 haproxy[24451]: 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 17:00:03 node-1 haproxy[24451]: 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 17:00:03 node-1 haproxy[24451]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:03 node-1 haproxy[24451]: proxy mysqld has no server available!
<129>Oct 28 17:00:03 node-1 haproxy[24451]: 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 17:00:03 node-1 haproxy[24451]: 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 17:00:04 node-1 haproxy[24451]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:04 node-1 haproxy[24451]: proxy object-storage has no server available!
<129>Oct 28 17:00:04 node-1 haproxy[24451]: 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 17:00:04 node-1 haproxy[24451]: 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 17:00:04 node-1 haproxy[24451]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:04 node-1 haproxy[24451]: proxy aodh has no server available!
<27>Oct 28 17:00:05 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:05 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:05 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:05 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:05 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:05 node-1 multipathd: uevent trigger error
<129>Oct 28 17:00:07 node-1 haproxy[25671]: 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 17:00:07 node-1 haproxy[25671]: 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 17:00:08 node-1 haproxy[25675]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:08 node-1 haproxy[25675]: proxy keystone-1 has no server available!
<129>Oct 28 17:00:08 node-1 haproxy[25675]: 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 17:00:08 node-1 haproxy[25675]: 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 17:00:08 node-1 haproxy[25675]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:08 node-1 haproxy[25675]: proxy keystone-2 has no server available!
<129>Oct 28 17:00:08 node-1 haproxy[25675]: 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 17:00:08 node-1 haproxy[25675]: 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 17:00:08 node-1 haproxy[25675]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:08 node-1 haproxy[25675]: proxy neutron has no server available!
<129>Oct 28 17:00:08 node-1 haproxy[25675]: 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 17:00:08 node-1 haproxy[25675]: 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 17:00:08 node-1 haproxy[25675]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:08 node-1 haproxy[25675]: proxy mysqld has no server available!
<129>Oct 28 17:00:08 node-1 haproxy[25675]: 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 17:00:09 node-1 haproxy[25675]: 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 17:00:09 node-1 haproxy[25675]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:09 node-1 haproxy[25675]: proxy object-storage has no server available!
<129>Oct 28 17:00:09 node-1 haproxy[25675]: 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 17:00:09 node-1 haproxy[25675]: 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 17:00:09 node-1 haproxy[25675]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:09 node-1 haproxy[25675]: proxy aodh has no server available!
<129>Oct 28 17:00:09 node-1 haproxy[25675]: 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 17:00:09 node-1 haproxy[25675]: 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 17:00:09 node-1 haproxy[25675]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:09 node-1 haproxy[25675]: proxy ceilometer has no server available!
<27>Oct 28 17:00:11 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:11 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:11 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:11 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:11 node-1 multipathd: uevent trigger error
<129>Oct 28 17:00:13 node-1 haproxy[27013]: 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 17:00:13 node-1 haproxy[27013]: 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 17:00:13 node-1 haproxy[27013]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:13 node-1 haproxy[27013]: proxy keystone-1 has no server available!
<129>Oct 28 17:00:13 node-1 haproxy[27013]: 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 17:00:13 node-1 haproxy[27013]: 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 17:00:13 node-1 haproxy[27013]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:13 node-1 haproxy[27013]: proxy keystone-2 has no server available!
<129>Oct 28 17:00:13 node-1 haproxy[27013]: 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 17:00:13 node-1 haproxy[27013]: 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 17:00:13 node-1 haproxy[27013]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:13 node-1 haproxy[27013]: proxy neutron has no server available!
<129>Oct 28 17:00:14 node-1 haproxy[27017]: 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 17:00:14 node-1 haproxy[27017]: 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 17:00:14 node-1 haproxy[27017]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:14 node-1 haproxy[27017]: proxy mysqld has no server available!
<129>Oct 28 17:00:14 node-1 haproxy[27017]: 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 17:00:14 node-1 haproxy[27017]: 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 17:00:14 node-1 haproxy[27017]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:14 node-1 haproxy[27017]: proxy object-storage has no server available!
<129>Oct 28 17:00:14 node-1 haproxy[27017]: 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 17:00:14 node-1 haproxy[27017]: 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 17:00:14 node-1 haproxy[27017]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:14 node-1 haproxy[27017]: proxy aodh has no server available!
<129>Oct 28 17:00:14 node-1 haproxy[27017]: 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 17:00:14 node-1 haproxy[27017]: 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 17:00:14 node-1 haproxy[27017]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:14 node-1 haproxy[27017]: proxy ceilometer has no server available!
<27>Oct 28 17:00:16 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:16 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:16 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:16 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:16 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:16 node-1 multipathd: uevent trigger error
<129>Oct 28 17:00:18 node-1 haproxy[28273]: 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 17:00:18 node-1 haproxy[28273]: 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 17:00:18 node-1 haproxy[28273]: 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 17:00:19 node-1 haproxy[28277]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:19 node-1 haproxy[28277]: proxy keystone-1 has no server available!
<129>Oct 28 17:00:19 node-1 haproxy[28277]: 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 17:00:19 node-1 haproxy[28277]: 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 17:00:19 node-1 haproxy[28277]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:19 node-1 haproxy[28277]: proxy keystone-2 has no server available!
<129>Oct 28 17:00:19 node-1 haproxy[28277]: 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 17:00:19 node-1 haproxy[28277]: 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 17:00:19 node-1 haproxy[28277]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:19 node-1 haproxy[28277]: proxy neutron has no server available!
<129>Oct 28 17:00:19 node-1 haproxy[28277]: 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 17:00:19 node-1 haproxy[28277]: 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 17:00:19 node-1 haproxy[28277]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:19 node-1 haproxy[28277]: proxy mysqld has no server available!
<129>Oct 28 17:00:19 node-1 haproxy[28277]: 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 17:00:19 node-1 haproxy[28277]: 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 17:00:19 node-1 haproxy[28277]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:19 node-1 haproxy[28277]: proxy object-storage has no server available!
<129>Oct 28 17:00:20 node-1 haproxy[28277]: 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 17:00:20 node-1 haproxy[28277]: 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 17:00:20 node-1 haproxy[28277]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:20 node-1 haproxy[28277]: proxy aodh has no server available!
<129>Oct 28 17:00:20 node-1 haproxy[28277]: 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 17:00:20 node-1 haproxy[28277]: 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 17:00:20 node-1 haproxy[28277]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:20 node-1 haproxy[28277]: proxy ceilometer has no server available!
<27>Oct 28 17:00:21 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:21 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:21 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:21 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:21 node-1 multipathd: uevent trigger error
<129>Oct 28 17:00:24 node-1 haproxy[29753]: 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 17:00:24 node-1 haproxy[29753]: 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 17:00:24 node-1 haproxy[29753]: 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 17:00:24 node-1 haproxy[29753]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:24 node-1 haproxy[29753]: proxy keystone-1 has no server available!
<129>Oct 28 17:00:24 node-1 haproxy[29753]: 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 17:00:24 node-1 haproxy[29753]: 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 17:00:24 node-1 haproxy[29753]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:24 node-1 haproxy[29753]: proxy keystone-2 has no server available!
<129>Oct 28 17:00:24 node-1 haproxy[29753]: 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 17:00:25 node-1 haproxy[29759]: 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 17:00:25 node-1 haproxy[29759]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:25 node-1 haproxy[29759]: proxy glance-api has no server available!
<129>Oct 28 17:00:25 node-1 haproxy[29759]: 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 17:00:25 node-1 haproxy[29759]: 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 17:00:25 node-1 haproxy[29759]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:25 node-1 haproxy[29759]: proxy glance-glare has no server available!
<129>Oct 28 17:00:25 node-1 haproxy[29759]: 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 17:00:25 node-1 haproxy[29759]: 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 17:00:25 node-1 haproxy[29759]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:25 node-1 haproxy[29759]: proxy neutron has no server available!
<129>Oct 28 17:00:25 node-1 haproxy[29759]: 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 17:00:25 node-1 haproxy[29759]: 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 17:00:25 node-1 haproxy[29759]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:25 node-1 haproxy[29759]: proxy glance-registry has no server available!
<129>Oct 28 17:00:25 node-1 haproxy[29759]: 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 17:00:25 node-1 haproxy[29759]: 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 17:00:25 node-1 haproxy[29759]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:25 node-1 haproxy[29759]: proxy mysqld has no server available!
<129>Oct 28 17:00:25 node-1 haproxy[29759]: 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 17:00:25 node-1 haproxy[29759]: 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 17:00:25 node-1 haproxy[29759]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:25 node-1 haproxy[29759]: proxy object-storage has no server available!
<129>Oct 28 17:00:26 node-1 haproxy[29759]: 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 17:00:26 node-1 haproxy[29759]: 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 17:00:26 node-1 haproxy[29759]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:26 node-1 haproxy[29759]: proxy aodh has no server available!
<129>Oct 28 17:00:26 node-1 haproxy[29759]: 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 17:00:26 node-1 haproxy[29759]: 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 17:00:26 node-1 haproxy[29759]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:26 node-1 haproxy[29759]: proxy ceilometer has no server available!
<27>Oct 28 17:00:27 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:27 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:27 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:27 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:27 node-1 multipathd: uevent trigger error
<129>Oct 28 17:00:30 node-1 haproxy[31030]: 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 17:00:30 node-1 haproxy[31030]: 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 17:00:30 node-1 haproxy[31030]: 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 17:00:30 node-1 haproxy[31030]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:30 node-1 haproxy[31030]: proxy keystone-1 has no server available!
<129>Oct 28 17:00:30 node-1 haproxy[31030]: 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 17:00:30 node-1 haproxy[31030]: 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 17:00:30 node-1 haproxy[31030]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:30 node-1 haproxy[31030]: proxy keystone-2 has no server available!
<129>Oct 28 17:00:30 node-1 haproxy[31030]: 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 17:00:30 node-1 haproxy[31030]: 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 17:00:30 node-1 haproxy[31030]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:30 node-1 haproxy[31030]: proxy nova-api has no server available!
<129>Oct 28 17:00:30 node-1 haproxy[31030]: 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 17:00:30 node-1 haproxy[31030]: 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 17:00:30 node-1 haproxy[31030]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:30 node-1 haproxy[31030]: proxy nova-metadata-api has no server available!
<129>Oct 28 17:00:30 node-1 haproxy[31030]: 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 17:00:30 node-1 haproxy[31030]: 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 17:00:30 node-1 haproxy[31030]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:30 node-1 haproxy[31030]: proxy glance-api has no server available!
<129>Oct 28 17:00:30 node-1 haproxy[31030]: 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 17:00:31 node-1 haproxy[31034]: 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 17:00:31 node-1 haproxy[31034]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:31 node-1 haproxy[31034]: proxy glance-glare has no server available!
<129>Oct 28 17:00:31 node-1 haproxy[31034]: 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 17:00:31 node-1 haproxy[31034]: 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 17:00:31 node-1 haproxy[31034]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:31 node-1 haproxy[31034]: proxy neutron has no server available!
<129>Oct 28 17:00:31 node-1 haproxy[31034]: 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 17:00:31 node-1 haproxy[31034]: 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 17:00:31 node-1 haproxy[31034]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:31 node-1 haproxy[31034]: proxy glance-registry has no server available!
<129>Oct 28 17:00:31 node-1 haproxy[31034]: 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 17:00:31 node-1 haproxy[31034]: 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 17:00:31 node-1 haproxy[31034]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:31 node-1 haproxy[31034]: proxy mysqld has no server available!
<129>Oct 28 17:00:31 node-1 haproxy[31034]: 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 17:00:31 node-1 haproxy[31034]: 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 17:00:31 node-1 haproxy[31034]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:31 node-1 haproxy[31034]: proxy object-storage has no server available!
<129>Oct 28 17:00:31 node-1 haproxy[31034]: 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 17:00:31 node-1 haproxy[31034]: 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 17:00:31 node-1 haproxy[31034]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:31 node-1 haproxy[31034]: proxy aodh has no server available!
<129>Oct 28 17:00:31 node-1 haproxy[31034]: 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 17:00:31 node-1 haproxy[31034]: 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 17:00:31 node-1 haproxy[31034]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:31 node-1 haproxy[31034]: proxy ceilometer has no server available!
<129>Oct 28 17:00:31 node-1 haproxy[31034]: 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 17:00:31 node-1 haproxy[31034]: 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 17:00:32 node-1 haproxy[31034]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:32 node-1 haproxy[31034]: proxy nova-novncproxy has no server available!
<27>Oct 28 17:00:33 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:33 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:33 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:33 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:33 node-1 multipathd: uevent trigger error
<129>Oct 28 17:00:35 node-1 haproxy[32244]: 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 17:00:35 node-1 haproxy[32244]: 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 17:00:35 node-1 haproxy[32244]: 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 17:00:35 node-1 haproxy[32244]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:35 node-1 haproxy[32244]: proxy keystone-1 has no server available!
<129>Oct 28 17:00:35 node-1 haproxy[32244]: 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 17:00:35 node-1 haproxy[32244]: 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 17:00:35 node-1 haproxy[32244]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:35 node-1 haproxy[32244]: proxy keystone-2 has no server available!
<129>Oct 28 17:00:35 node-1 haproxy[32244]: 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 17:00:35 node-1 haproxy[32244]: 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 17:00:35 node-1 haproxy[32244]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:35 node-1 haproxy[32244]: proxy nova-api has no server available!
<129>Oct 28 17:00:35 node-1 haproxy[32244]: 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 17:00:35 node-1 haproxy[32244]: 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 17:00:35 node-1 haproxy[32244]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:35 node-1 haproxy[32244]: proxy nova-metadata-api has no server available!
<129>Oct 28 17:00:36 node-1 haproxy[32251]: 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 17:00:36 node-1 haproxy[32251]: 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 17:00:36 node-1 haproxy[32251]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:36 node-1 haproxy[32251]: proxy cinder-api has no server available!
<129>Oct 28 17:00:36 node-1 haproxy[32251]: 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 17:00:36 node-1 haproxy[32251]: 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 17:00:36 node-1 haproxy[32251]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:36 node-1 haproxy[32251]: proxy glance-api has no server available!
<129>Oct 28 17:00:36 node-1 haproxy[32251]: 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 17:00:36 node-1 haproxy[32251]: 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 17:00:36 node-1 haproxy[32251]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:36 node-1 haproxy[32251]: proxy glance-glare has no server available!
<129>Oct 28 17:00:36 node-1 haproxy[32251]: 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 17:00:36 node-1 haproxy[32251]: 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 17:00:36 node-1 haproxy[32251]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:36 node-1 haproxy[32251]: proxy neutron has no server available!
<129>Oct 28 17:00:36 node-1 haproxy[32251]: 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 17:00:36 node-1 haproxy[32251]: 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 17:00:36 node-1 haproxy[32251]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:36 node-1 haproxy[32251]: proxy glance-registry has no server available!
<129>Oct 28 17:00:36 node-1 haproxy[32251]: 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 17:00:36 node-1 haproxy[32251]: 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 17:00:36 node-1 haproxy[32251]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:36 node-1 haproxy[32251]: proxy mysqld has no server available!
<129>Oct 28 17:00:36 node-1 haproxy[32251]: 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 17:00:36 node-1 haproxy[32251]: 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 17:00:36 node-1 haproxy[32251]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:36 node-1 haproxy[32251]: proxy object-storage has no server available!
<129>Oct 28 17:00:36 node-1 haproxy[32251]: 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 17:00:36 node-1 haproxy[32251]: 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 17:00:36 node-1 haproxy[32251]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:36 node-1 haproxy[32251]: proxy aodh has no server available!
<129>Oct 28 17:00:37 node-1 haproxy[32251]: 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 17:00:37 node-1 haproxy[32251]: 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 17:00:37 node-1 haproxy[32251]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:37 node-1 haproxy[32251]: proxy ceilometer has no server available!
<129>Oct 28 17:00:37 node-1 haproxy[32251]: 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 17:00:37 node-1 haproxy[32251]: 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 17:00:37 node-1 haproxy[32251]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:37 node-1 haproxy[32251]: proxy nova-novncproxy has no server available!
<27>Oct 28 17:00:38 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:38 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:38 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:38 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:38 node-1 multipathd: uevent trigger error
<129>Oct 28 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:41 node-1 haproxy[1119]: proxy keystone-1 has no server available!
<129>Oct 28 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:41 node-1 haproxy[1119]: proxy keystone-2 has no server available!
<129>Oct 28 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:41 node-1 haproxy[1119]: proxy nova-api has no server available!
<129>Oct 28 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:41 node-1 haproxy[1119]: proxy nova-metadata-api has no server available!
<129>Oct 28 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:41 node-1 haproxy[1119]: proxy cinder-api has no server available!
<129>Oct 28 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:41 node-1 haproxy[1119]: proxy glance-api has no server available!
<129>Oct 28 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:41 node-1 haproxy[1119]: proxy glance-glare has no server available!
<129>Oct 28 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: 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 17:00:41 node-1 haproxy[1119]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:41 node-1 haproxy[1119]: proxy neutron has no server available!
<129>Oct 28 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:42 node-1 haproxy[1123]: proxy glance-registry has no server available!
<129>Oct 28 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:42 node-1 haproxy[1123]: proxy mysqld has no server available!
<129>Oct 28 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:42 node-1 haproxy[1123]: proxy object-storage has no server available!
<129>Oct 28 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:42 node-1 haproxy[1123]: proxy aodh has no server available!
<129>Oct 28 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:42 node-1 haproxy[1123]: proxy ceilometer has no server available!
<129>Oct 28 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:42 node-1 haproxy[1123]: proxy heat-api has no server available!
<129>Oct 28 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:42 node-1 haproxy[1123]: proxy heat-api-cfn has no server available!
<129>Oct 28 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:42 node-1 haproxy[1123]: proxy heat-api-cloudwatch has no server available!
<129>Oct 28 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: 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 17:00:42 node-1 haproxy[1123]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 28 17:00:42 node-1 haproxy[1123]: proxy nova-novncproxy has no server available!
<27>Oct 28 17:00:44 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:44 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:44 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:44 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:44 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:44 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:47 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:47 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:47 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:47 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:47 node-1 multipathd: uevent trigger error
<27>Oct 28 17:00:55 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 28 17:01:01 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 17:01:08 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 28 17:01:20 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 17:01:22 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 28 17:02:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:02:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:02:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:02:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:15 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 17:04:28 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:28 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:28 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:28 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:28 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:34 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:34 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:34 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:34 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:34 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:34 node-1 multipathd: uevent trigger error
<43>Oct 28 17:04:46 node-1 apache2_error [Fri Oct 28 17:04:45.812418 2016] [mpm_event:notice] [pid 10660:tid 139701164824448] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 28 17:04:46 node-1 apache2_error [Fri Oct 28 17:04:45.812566 2016] [core:notice] [pid 10660:tid 139701164824448] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 17:04:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:53 node-1 multipathd: uevent trigger error
<43>Oct 28 17:04:56 node-1 apache2_error [Fri Oct 28 17:04:48.040039 2016] [mpm_event:notice] [pid 10660:tid 139701164824448] AH00491: caught SIGTERM, shutting down
<43>Oct 28 17:04:56 node-1 apache2_error [Fri Oct 28 17:04:49.122887 2016] [mpm_worker:notice] [pid 11928:tid 139948801648512] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 28 17:04:56 node-1 apache2_error [Fri Oct 28 17:04:49.122918 2016] [core:notice] [pid 11928:tid 139948801648512] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 17:04:58 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:58 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:58 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:58 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:58 node-1 multipathd: uevent trigger error
<27>Oct 28 17:04:58 node-1 multipathd: uevent trigger error
<27>Oct 28 17:05:01 node-1 multipathd: uevent trigger error
<27>Oct 28 17:05:01 node-1 multipathd: uevent trigger error
<27>Oct 28 17:05:01 node-1 multipathd: uevent trigger error
<27>Oct 28 17:05:01 node-1 multipathd: uevent trigger error
<27>Oct 28 17:05:01 node-1 multipathd: uevent trigger error
<27>Oct 28 17:05:01 node-1 multipathd: uevent trigger error
<27>Oct 28 17:05:01 node-1 multipathd: uevent trigger error
<43>Oct 28 17:06:16 node-1 apache2_error [Fri Oct 28 17:06:09.309150 2016] [mpm_worker:notice] [pid 11928:tid 139948801648512] AH00295: caught SIGTERM, shutting down
<43>Oct 28 17:06:16 node-1 apache2_error [Fri Oct 28 17:06:10.065984 2016] [mpm_worker:notice] [pid 25467:tid 139871631046528] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 17:06:16 node-1 apache2_error [Fri Oct 28 17:06:10.066018 2016] [core:notice] [pid 25467:tid 139871631046528] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 28 17:06:56 node-1 apache2_error [Fri Oct 28 17:06:55.544769 2016] [mpm_worker:notice] [pid 25467:tid 139871631046528] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 17:06:56 node-1 apache2_error [Fri Oct 28 17:06:55.736977 2016] [mpm_worker:warn] [pid 25467:tid 139871631046528] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 17:06:56 node-1 apache2_error [Fri Oct 28 17:06:55.739704 2016] [mpm_worker:notice] [pid 25467:tid 139871631046528] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 17:06:56 node-1 apache2_error [Fri Oct 28 17:06:55.739719 2016] [core:notice] [pid 25467:tid 139871631046528] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 17:07:19 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 17:07:39 node-1 multipathd: uevent trigger error
<27>Oct 28 17:07:39 node-1 multipathd: uevent trigger error
<27>Oct 28 17:07:39 node-1 multipathd: uevent trigger error
<27>Oct 28 17:07:39 node-1 multipathd: uevent trigger error
<27>Oct 28 17:07:44 node-1 multipathd: uevent trigger error
<27>Oct 28 17:07:44 node-1 multipathd: uevent trigger error
<27>Oct 28 17:07:44 node-1 multipathd: uevent trigger error
<27>Oct 28 17:07:44 node-1 multipathd: uevent trigger error
<27>Oct 28 17:07:44 node-1 multipathd: uevent trigger error
<27>Oct 28 17:07:44 node-1 multipathd: uevent trigger error
<27>Oct 28 17:07:59 node-1 multipathd: uevent trigger error
<27>Oct 28 17:07:59 node-1 multipathd: uevent trigger error
<27>Oct 28 17:07:59 node-1 multipathd: uevent trigger error
<27>Oct 28 17:07:59 node-1 multipathd: uevent trigger error
<27>Oct 28 17:07:59 node-1 multipathd: uevent trigger error
<27>Oct 28 17:08:24 node-1 multipathd: uevent trigger error
<27>Oct 28 17:08:24 node-1 multipathd: uevent trigger error
<27>Oct 28 17:08:24 node-1 multipathd: uevent trigger error
<27>Oct 28 17:08:24 node-1 multipathd: uevent trigger error
<27>Oct 28 17:08:24 node-1 multipathd: uevent trigger error
<27>Oct 28 17:08:29 node-1 multipathd: uevent trigger error
<27>Oct 28 17:08:29 node-1 multipathd: uevent trigger error
<27>Oct 28 17:08:29 node-1 multipathd: uevent trigger error
<27>Oct 28 17:08:29 node-1 multipathd: uevent trigger error
<27>Oct 28 17:08:29 node-1 multipathd: uevent trigger error
<27>Oct 28 17:08:29 node-1 multipathd: uevent trigger error
<27>Oct 28 17:09:14 node-1 multipathd: uevent trigger error
<27>Oct 28 17:09:14 node-1 multipathd: uevent trigger error
<27>Oct 28 17:09:14 node-1 multipathd: uevent trigger error
<27>Oct 28 17:09:14 node-1 multipathd: uevent trigger error
<27>Oct 28 17:09:14 node-1 multipathd: uevent trigger error
<27>Oct 28 17:09:14 node-1 multipathd: uevent trigger error
<27>Oct 28 17:09:28 node-1 multipathd: uevent trigger error
<27>Oct 28 17:09:28 node-1 multipathd: uevent trigger error
<27>Oct 28 17:09:28 node-1 multipathd: uevent trigger error
<27>Oct 28 17:09:28 node-1 multipathd: uevent trigger error
<27>Oct 28 17:09:28 node-1 multipathd: uevent trigger error
<27>Oct 28 17:10:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:10:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:10:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:10:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:10:24 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 17:11:28 node-1 multipathd: uevent trigger error
<27>Oct 28 17:11:28 node-1 multipathd: uevent trigger error
<27>Oct 28 17:11:28 node-1 multipathd: uevent trigger error
<27>Oct 28 17:11:28 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:27 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:27 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:27 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:27 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:27 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:27 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:59 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:59 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:59 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:59 node-1 multipathd: uevent trigger error
<27>Oct 28 17:12:59 node-1 multipathd: uevent trigger error
<27>Oct 28 17:13:26 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 17:15:29 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:29 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:29 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:29 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:29 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:48 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:48 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:48 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:48 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:48 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:48 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:59 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:59 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:59 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:59 node-1 multipathd: uevent trigger error
<27>Oct 28 17:15:59 node-1 multipathd: uevent trigger error
<27>Oct 28 17:16:20 node-1 multipathd: uevent trigger error
<27>Oct 28 17:16:20 node-1 multipathd: uevent trigger error
<27>Oct 28 17:16:20 node-1 multipathd: uevent trigger error
<27>Oct 28 17:16:20 node-1 multipathd: uevent trigger error
<27>Oct 28 17:16:20 node-1 multipathd: uevent trigger error
<27>Oct 28 17:16:20 node-1 multipathd: uevent trigger error
<27>Oct 28 17:16:27 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 17:17:02 node-1 multipathd: uevent trigger error
<27>Oct 28 17:17:03 node-1 multipathd: uevent trigger error
<27>Oct 28 17:17:03 node-1 multipathd: uevent trigger error
<27>Oct 28 17:17:03 node-1 multipathd: uevent trigger error
<27>Oct 28 17:17:03 node-1 multipathd: uevent trigger error
<27>Oct 28 17:17:51 node-1 multipathd: uevent trigger error
<27>Oct 28 17:17:51 node-1 multipathd: uevent trigger error
<27>Oct 28 17:17:52 node-1 multipathd: uevent trigger error
<27>Oct 28 17:17:52 node-1 multipathd: uevent trigger error
<27>Oct 28 17:17:52 node-1 multipathd: uevent trigger error
<27>Oct 28 17:17:52 node-1 multipathd: uevent trigger error
<27>Oct 28 17:18:07 node-1 multipathd: uevent trigger error
<27>Oct 28 17:18:07 node-1 multipathd: uevent trigger error
<27>Oct 28 17:18:07 node-1 multipathd: uevent trigger error
<27>Oct 28 17:18:07 node-1 multipathd: uevent trigger error
<27>Oct 28 17:18:07 node-1 multipathd: uevent trigger error
<27>Oct 28 17:18:07 node-1 multipathd: uevent trigger error
<27>Oct 28 17:18:24 node-1 multipathd: uevent trigger error
<27>Oct 28 17:18:24 node-1 multipathd: uevent trigger error
<27>Oct 28 17:18:24 node-1 multipathd: uevent trigger error
<27>Oct 28 17:18:24 node-1 multipathd: uevent trigger error
<27>Oct 28 17:18:24 node-1 multipathd: uevent trigger error
<27>Oct 28 17:19:29 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 17:20:45 node-1 multipathd: uevent trigger error
<27>Oct 28 17:20:45 node-1 multipathd: uevent trigger error
<27>Oct 28 17:20:45 node-1 multipathd: uevent trigger error
<27>Oct 28 17:20:45 node-1 multipathd: uevent trigger error
<27>Oct 28 17:20:46 node-1 multipathd: uevent trigger error
<27>Oct 28 17:21:12 node-1 multipathd: uevent trigger error
<27>Oct 28 17:21:12 node-1 multipathd: uevent trigger error
<27>Oct 28 17:21:12 node-1 multipathd: uevent trigger error
<27>Oct 28 17:21:12 node-1 multipathd: uevent trigger error
<27>Oct 28 17:21:12 node-1 multipathd: uevent trigger error
<27>Oct 28 17:21:17 node-1 multipathd: uevent trigger error
<27>Oct 28 17:21:17 node-1 multipathd: uevent trigger error
<27>Oct 28 17:21:17 node-1 multipathd: uevent trigger error
<27>Oct 28 17:21:17 node-1 multipathd: uevent trigger error
<27>Oct 28 17:21:17 node-1 multipathd: uevent trigger error
<27>Oct 28 17:21:57 node-1 multipathd: uevent trigger error
<27>Oct 28 17:21:57 node-1 multipathd: uevent trigger error
<27>Oct 28 17:21:57 node-1 multipathd: uevent trigger error
<27>Oct 28 17:21:57 node-1 multipathd: uevent trigger error
<27>Oct 28 17:21:57 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:01 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:01 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:01 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:01 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:05 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:05 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:05 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:05 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:05 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:17 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:17 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:17 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:17 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:17 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:23 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:23 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:23 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:23 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:23 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:30 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 28 17:22:57 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:57 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:58 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:58 node-1 multipathd: uevent trigger error
<27>Oct 28 17:22:58 node-1 multipathd: uevent trigger error
<27>Oct 28 17:24:08 node-1 multipathd: uevent trigger error
<27>Oct 28 17:24:08 node-1 multipathd: uevent trigger error
<27>Oct 28 17:24:08 node-1 multipathd: uevent trigger error
<27>Oct 28 17:24:09 node-1 multipathd: uevent trigger error
<27>Oct 28 17:24:09 node-1 multipathd: uevent trigger error
<27>Oct 28 17:24:25 node-1 multipathd: uevent trigger error
<27>Oct 28 17:24:25 node-1 multipathd: uevent trigger error
<27>Oct 28 17:24:25 node-1 multipathd: uevent trigger error
<27>Oct 28 17:24:25 node-1 multipathd: uevent trigger error
<27>Oct 28 17:24:25 node-1 multipathd: uevent trigger error
<11>Oct 28 17:24:37 node-1 liberasurecode[1155]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:37 node-1 liberasurecode[1155]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:37 node-1 liberasurecode[1155]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:37 node-1 liberasurecode[1155]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:37 node-1 liberasurecode[1179]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:37 node-1 liberasurecode[1179]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:37 node-1 liberasurecode[1179]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:37 node-1 liberasurecode[1179]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:39 node-1 liberasurecode[2326]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:39 node-1 liberasurecode[2326]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:39 node-1 liberasurecode[2326]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:39 node-1 liberasurecode[2326]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[3931]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[3931]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[3931]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[3931]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[3967]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[3967]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[3967]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[3967]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4010]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4010]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4010]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4010]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4094]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4094]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4094]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4094]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4109]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4109]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4109]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4109]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4121]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4121]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4121]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4121]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4133]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4133]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4133]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:43 node-1 liberasurecode[4133]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:52 node-1 liberasurecode[4550]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:52 node-1 liberasurecode[4550]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:52 node-1 liberasurecode[4550]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:24:52 node-1 liberasurecode[4550]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 28 17:25:00 node-1 multipathd: uevent trigger error
<27>Oct 28 17:25:00 node-1 multipathd: uevent trigger error
<27>Oct 28 17:25:00 node-1 multipathd: uevent trigger error
<27>Oct 28 17:25:00 node-1 multipathd: uevent trigger error
<27>Oct 28 17:25:00 node-1 multipathd: uevent trigger error
<11>Oct 28 17:25:01 node-1 liberasurecode[5998]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:25:01 node-1 liberasurecode[5998]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:25:01 node-1 liberasurecode[5998]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:25:01 node-1 liberasurecode[5998]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 28 17:25:32 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 28 17:25:47 node-1 apache2_error [Fri Oct 28 17:25:46.793352 2016] [mpm_worker:notice] [pid 25467:tid 139871631046528] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 17:25:47 node-1 apache2_error [Fri Oct 28 17:25:47.174996 2016] [mpm_worker:warn] [pid 25467:tid 139871631046528] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 17:25:47 node-1 apache2_error [Fri Oct 28 17:25:47.178142 2016] [mpm_worker:notice] [pid 25467:tid 139871631046528] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 17:25:47 node-1 apache2_error [Fri Oct 28 17:25:47.178160 2016] [core:notice] [pid 25467:tid 139871631046528] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 17:26:27 node-1 multipathd: uevent trigger error
<27>Oct 28 17:26:27 node-1 multipathd: uevent trigger error
<27>Oct 28 17:26:27 node-1 multipathd: uevent trigger error
<27>Oct 28 17:26:27 node-1 multipathd: uevent trigger error
<27>Oct 28 17:26:27 node-1 multipathd: uevent trigger error
<27>Oct 28 17:26:27 node-1 multipathd: uevent trigger error
<43>Oct 28 17:26:27 node-1 apache2_error [Fri Oct 28 17:26:23.968410 2016] [mpm_worker:notice] [pid 25467:tid 139871631046528] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 17:26:27 node-1 apache2_error [Fri Oct 28 17:26:24.164248 2016] [mpm_worker:warn] [pid 25467:tid 139871631046528] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 17:26:27 node-1 apache2_error [Fri Oct 28 17:26:24.168231 2016] [mpm_worker:notice] [pid 25467:tid 139871631046528] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 17:26:27 node-1 apache2_error [Fri Oct 28 17:26:24.168256 2016] [core:notice] [pid 25467:tid 139871631046528] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 17:26:35 node-1 multipathd: uevent trigger error
<27>Oct 28 17:26:35 node-1 multipathd: uevent trigger error
<27>Oct 28 17:26:35 node-1 multipathd: uevent trigger error
<27>Oct 28 17:26:35 node-1 multipathd: uevent trigger error
<27>Oct 28 17:26:35 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:12 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:12 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:12 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:12 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:12 node-1 multipathd: uevent trigger error
<43>Oct 28 17:27:18 node-1 apache2_error [Fri Oct 28 17:27:08.830208 2016] [mpm_worker:notice] [pid 25467:tid 139871631046528] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 28 17:27:18 node-1 apache2_error [Fri Oct 28 17:27:09.029222 2016] [mpm_worker:warn] [pid 25467:tid 139871631046528] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 28 17:27:18 node-1 apache2_error [Fri Oct 28 17:27:09.034536 2016] [mpm_worker:notice] [pid 25467:tid 139871631046528] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 28 17:27:18 node-1 apache2_error [Fri Oct 28 17:27:09.034558 2016] [core:notice] [pid 25467:tid 139871631046528] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 28 17:27:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:24 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:24 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:24 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:24 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:24 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:41 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:41 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:41 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:41 node-1 multipathd: uevent trigger error
<27>Oct 28 17:27:41 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:04 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:11 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:11 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:11 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:11 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:17 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 28 17:28:26 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:26 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:26 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:26 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:30 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:30 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:30 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:30 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:30 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:35 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:35 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:35 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:35 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:35 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:40 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:40 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:40 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:40 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:40 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:51 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:51 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:51 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:51 node-1 multipathd: uevent trigger error
<27>Oct 28 17:28:51 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:18 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:23 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:23 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:23 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:23 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:23 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:36 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:36 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:36 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:36 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:36 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:41 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:41 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:41 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:41 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:41 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:53 node-1 multipathd: uevent trigger error
<27>Oct 28 17:29:53 node-1 multipathd: uevent trigger error
<11>Oct 28 17:30:01 node-1 liberasurecode[6426]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:30:01 node-1 liberasurecode[6426]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:30:01 node-1 liberasurecode[6426]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 28 17:30:01 node-1 liberasurecode[6426]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 28 17:30:07 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:07 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:07 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:07 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:07 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:12 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:12 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:12 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:12 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:12 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:16 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:16 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:16 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:16 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:16 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:25 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:25 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:25 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:25 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:25 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:29 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:29 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:29 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:29 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:29 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:34 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:34 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:34 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:34 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:34 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:38 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:38 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:38 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:38 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:38 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:42 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:43 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:43 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:43 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:43 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:47 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:47 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:47 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:47 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:47 node-1 multipathd: uevent trigger error
<27>Oct 28 17:30:55 node-1 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct 28 17:30:55 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:30:55 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:30:55 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:30:55 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:30:55 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:30:56 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:30:57 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:30:58 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:30:59 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:00 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:01 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:02 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:03 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:04 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:05 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:09 node-1 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct 28 17:31:09 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:09 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:09 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:09 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:10 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:10 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:11 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:12 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:13 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:14 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:15 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:16 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:17 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:18 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:19 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:21 node-1 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct 28 17:31:21 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:21 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:21 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:21 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:22 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:22 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:23 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:24 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:25 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:26 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:27 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:28 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:29 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:30 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:32 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:33 node-1 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct 28 17:31:33 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:33 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:33 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:33 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:34 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:34 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:35 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:36 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:37 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:38 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:39 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:40 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:41 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:43 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:44 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:45 node-1 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct 28 17:31:45 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:45 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:45 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:46 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:46 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:46 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:47 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:48 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:49 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:50 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:51 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:53 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:54 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:55 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:56 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:57 node-1 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct 28 17:31:57 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:58 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:58 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:58 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:58 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:58 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:31:59 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:00 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:01 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:02 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:04 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:05 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:06 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:07 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:08 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:10 node-1 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct 28 17:32:10 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:10 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:10 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:10 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:10 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:11 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:11 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:12 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:14 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:15 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:16 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:17 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:18 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:19 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:20 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:22 node-1 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Oct 28 17:32:22 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:22 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:22 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:22 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:22 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:23 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:24 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:25 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
<27>Oct 28 17:32:26 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-58d83453-44" in table Interface
