Sep 17 16:49:58 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8420" x-info="http://www.rsyslog.com"] start
Sep 17 16:49:58 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 17 16:49:58 node-1 rsyslogd: rsyslogd's groupid changed to 104
Sep 17 16:49:58 node-1 rsyslogd: rsyslogd's userid changed to 101
Sep 17 16:49:58 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 17 16:49:58 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 17 16:49:58 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 17 16:49:58 node-1 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep 17 16:49:58 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=15de3b21-fe34-40ee-9087-2b7b9f7966da nomdmonddf nomdmonisw
Sep 17 16:49:58 node-1 kernel: [    0.000000] KERNEL supported cpus:
Sep 17 16:49:58 node-1 kernel: [    0.000000]   Intel GenuineIntel
Sep 17 16:49:58 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Sep 17 16:49:58 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Sep 17 16:49:58 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 17 16:49:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 17 16:49:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 17 16:49:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 17 16:49:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 17 16:49:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 17 16:49:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 17 16:49:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 17 16:49:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 17 16:49:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 17 16:49:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 17 16:49:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 17 16:49:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 17 16:49:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 17 16:49:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 17 16:49:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 17 16:49:58 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 17 16:49:58 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 17 16:49:58 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Sep 17 16:49:58 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 17 16:49:58 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 17 16:49:58 node-1 kernel: [    0.000000] No AGP bridge found
Sep 17 16:49:58 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 17 16:49:58 node-1 kernel: [    0.000000] MTRR default type: write-back
Sep 17 16:49:58 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 17 16:49:58 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Sep 17 16:49:58 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 17 16:49:58 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 17 16:49:58 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 17 16:49:58 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 17 16:49:58 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 17 16:49:58 node-1 kernel: [    0.000000]   2 disabled
Sep 17 16:49:58 node-1 kernel: [    0.000000]   3 disabled
Sep 17 16:49:58 node-1 kernel: [    0.000000]   4 disabled
Sep 17 16:49:58 node-1 kernel: [    0.000000]   5 disabled
Sep 17 16:49:58 node-1 kernel: [    0.000000]   6 disabled
Sep 17 16:49:58 node-1 kernel: [    0.000000]   7 disabled
Sep 17 16:49:58 node-1 kernel: [    0.000000]   8 disabled
Sep 17 16:49:58 node-1 kernel: [    0.000000]   9 disabled
Sep 17 16:49:58 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 17 16:49:58 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 17 16:49:58 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 17 16:49:58 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 17 16:49:58 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 17 16:49:58 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Sep 17 16:49:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 17 16:49:58 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 17 16:49:58 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 17 16:49:58 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 17 16:49:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 17 16:49:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 17 16:49:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 17 16:49:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 17 16:49:58 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 17 16:49:58 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 17 16:49:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 17 16:49:58 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 17 16:49:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 17 16:49:58 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 17 16:49:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 17 16:49:58 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 17 16:49:58 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 17 16:49:58 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 17 16:49:58 node-1 kernel: [    0.000000] Zone ranges:
Sep 17 16:49:58 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] Movable zone start for each node
Sep 17 16:49:58 node-1 kernel: [    0.000000] Early memory node ranges
Sep 17 16:49:58 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 17 16:49:58 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 17 16:49:58 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 17 16:49:58 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 17 16:49:58 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 17 16:49:58 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 17 16:49:58 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 17 16:49:58 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 17 16:49:58 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 17 16:49:58 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 17 16:49:58 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 17 16:49:58 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 17 16:49:58 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 17 16:49:58 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 17 16:49:58 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 17 16:49:58 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 17 16:49:58 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 17 16:49:58 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 17 16:49:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 17 16:49:58 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 17 16:49:58 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 17 16:49:58 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 17 16:49:58 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 17 16:49:58 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 17 16:49:58 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Sep 17 16:49:58 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 17 16:49:58 node-1 kernel: [    0.000000] Policy zone: Normal
Sep 17 16:49:58 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=15de3b21-fe34-40ee-9087-2b7b9f7966da nomdmonddf nomdmonisw
Sep 17 16:49:58 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 17 16:49:58 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 17 16:49:58 node-1 kernel: [    0.000000] Checking aperture...
Sep 17 16:49:58 node-1 kernel: [    0.000000] No AGP bridge found
Sep 17 16:49:58 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 17 16:49:58 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 17 16:49:58 node-1 kernel: [    0.000000] Memory: 32653320K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Sep 17 16:49:58 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 17 16:49:58 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 17 16:49:58 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 17 16:49:58 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 17 16:49:58 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 17 16:49:58 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 17 16:49:58 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 17 16:49:58 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 17 16:49:58 node-1 kernel: [    0.000000] console [tty0] enabled
Sep 17 16:49:58 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 17 16:49:58 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 17 16:49:58 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 17 16:49:58 node-1 kernel: [    0.000000] hpet clockevent registered
Sep 17 16:49:58 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 17 16:49:58 node-1 kernel: [    0.004000] tsc: Detected 3492.150 MHz processor
Sep 17 16:49:58 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.30 BogoMIPS (lpj=13968600)
Sep 17 16:49:58 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 17 16:49:58 node-1 kernel: [    0.000050] Security Framework initialized
Sep 17 16:49:58 node-1 kernel: [    0.000069] AppArmor: AppArmor initialized
Sep 17 16:49:58 node-1 kernel: [    0.000071] Yama: becoming mindful.
Sep 17 16:49:58 node-1 kernel: [    0.001462] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 17 16:49:58 node-1 kernel: [    0.006423] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 17 16:49:58 node-1 kernel: [    0.008350] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 17 16:49:58 node-1 kernel: [    0.008378] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 17 16:49:58 node-1 kernel: [    0.008669] Initializing cgroup subsys memory
Sep 17 16:49:58 node-1 kernel: [    0.008678] Initializing cgroup subsys devices
Sep 17 16:49:58 node-1 kernel: [    0.008679] Initializing cgroup subsys freezer
Sep 17 16:49:58 node-1 kernel: [    0.008681] Initializing cgroup subsys blkio
Sep 17 16:49:58 node-1 kernel: [    0.008683] Initializing cgroup subsys perf_event
Sep 17 16:49:58 node-1 kernel: [    0.008685] Initializing cgroup subsys hugetlb
Sep 17 16:49:58 node-1 kernel: [    0.008704] CPU: Physical Processor ID: 0
Sep 17 16:49:58 node-1 kernel: [    0.008705] CPU: Processor Core ID: 0
Sep 17 16:49:58 node-1 kernel: [    0.008709] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 17 16:49:58 node-1 kernel: [    0.008709] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 17 16:49:58 node-1 kernel: [    0.009403] mce: CPU supports 22 MCE banks
Sep 17 16:49:58 node-1 kernel: [    0.009431] CPU0: Thermal monitoring enabled (TM1)
Sep 17 16:49:58 node-1 kernel: [    0.009451] process: using mwait in idle threads
Sep 17 16:49:58 node-1 kernel: [    0.009454] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 17 16:49:58 node-1 kernel: [    0.009454] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 17 16:49:58 node-1 kernel: [    0.009454] tlb_flushall_shift: 6
Sep 17 16:49:58 node-1 kernel: [    0.009543] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 17 16:49:58 node-1 kernel: [    0.010268] ACPI: Core revision 20131115
Sep 17 16:49:58 node-1 kernel: [    0.022929] ACPI: All ACPI Tables successfully acquired
Sep 17 16:49:58 node-1 kernel: [    0.023079] ftrace: allocating 28617 entries in 112 pages
Sep 17 16:49:58 node-1 kernel: [    0.032058] dmar: Host address width 46
Sep 17 16:49:58 node-1 kernel: [    0.032060] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 17 16:49:58 node-1 kernel: [    0.032066] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 17 16:49:58 node-1 kernel: [    0.032068] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 17 16:49:58 node-1 kernel: [    0.032072] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 17 16:49:58 node-1 kernel: [    0.032073] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 17 16:49:58 node-1 kernel: [    0.032075] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 17 16:49:58 node-1 kernel: [    0.032076] dmar: ATSR flags: 0x0
Sep 17 16:49:58 node-1 kernel: [    0.032077] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 17 16:49:58 node-1 kernel: [    0.032078] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 17 16:49:58 node-1 kernel: [    0.032194] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 17 16:49:58 node-1 kernel: [    0.032195] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 17 16:49:58 node-1 kernel: [    0.032196] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 17 16:49:58 node-1 kernel: [    0.032197] HPET id 0 under DRHD base 0xc7ffc000
Sep 17 16:49:58 node-1 kernel: [    0.032199] Your BIOS is broken and requested that x2apic be disabled.
Sep 17 16:49:58 node-1 kernel: [    0.032199] This will slightly decrease performance.
Sep 17 16:49:58 node-1 kernel: [    0.032199] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 17 16:49:58 node-1 kernel: [    0.032630] Enabled IRQ remapping in xapic mode
Sep 17 16:49:58 node-1 kernel: [    0.032631] x2apic not enabled, IRQ remapping is in xapic mode
Sep 17 16:49:58 node-1 kernel: [    0.032635] Switched APIC routing to physical flat.
Sep 17 16:49:58 node-1 kernel: [    0.033260] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 17 16:49:58 node-1 kernel: [    0.072913] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 17 16:49:58 node-1 kernel: [    0.072918] TSC deadline timer enabled
Sep 17 16:49:58 node-1 kernel: [    0.072926] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 17 16:49:58 node-1 kernel: [    0.072932] ... version:                3
Sep 17 16:49:58 node-1 kernel: [    0.072933] ... bit width:              48
Sep 17 16:49:58 node-1 kernel: [    0.072934] ... generic registers:      4
Sep 17 16:49:58 node-1 kernel: [    0.072935] ... value mask:             0000ffffffffffff
Sep 17 16:49:58 node-1 kernel: [    0.072936] ... max period:             0000ffffffffffff
Sep 17 16:49:58 node-1 kernel: [    0.072937] ... fixed-purpose events:   3
Sep 17 16:49:58 node-1 kernel: [    0.072938] ... event mask:             000000070000000f
Sep 17 16:49:58 node-1 kernel: [    0.074353] x86: Booting SMP configuration:
Sep 17 16:49:58 node-1 kernel: [    0.088459] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 17 16:49:58 node-1 kernel: [    0.074355] .... node  #0, CPUs:        #1  #2  #3
Sep 17 16:49:58 node-1 kernel: [    0.116371] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 17 16:49:58 node-1 kernel: [    0.270530] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 17 16:49:58 node-1 kernel: [    0.326150] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 17 16:49:58 node-1 kernel: [    0.383212] x86: Booted up 2 nodes, 16 CPUs
Sep 17 16:49:58 node-1 kernel: [    0.383215] smpboot: Total of 16 processors activated (111760.95 BogoMIPS)
Sep 17 16:49:58 node-1 kernel: [    0.407272] devtmpfs: initialized
Sep 17 16:49:58 node-1 kernel: [    0.410403] EVM: security.selinux
Sep 17 16:49:58 node-1 kernel: [    0.410405] EVM: security.SMACK64
Sep 17 16:49:58 node-1 kernel: [    0.410406] EVM: security.ima
Sep 17 16:49:58 node-1 kernel: [    0.410406] EVM: security.capability
Sep 17 16:49:58 node-1 kernel: [    0.410458] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 17 16:49:58 node-1 kernel: [    0.411144] pinctrl core: initialized pinctrl subsystem
Sep 17 16:49:58 node-1 kernel: [    0.411208] regulator-dummy: no parameters
Sep 17 16:49:58 node-1 kernel: [    0.411241] RTC time: 16:49:22, date: 09/17/16
Sep 17 16:49:58 node-1 kernel: [    0.411275] NET: Registered protocol family 16
Sep 17 16:49:58 node-1 kernel: [    0.411360] cpuidle: using governor ladder
Sep 17 16:49:58 node-1 kernel: [    0.411361] cpuidle: using governor menu
Sep 17 16:49:58 node-1 kernel: [    0.411396] ACPI: bus type PCI registered
Sep 17 16:49:58 node-1 kernel: [    0.411398] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 17 16:49:58 node-1 kernel: [    0.411443] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 17 16:49:58 node-1 kernel: [    0.411445] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 17 16:49:58 node-1 kernel: [    0.425191] PCI: Using configuration type 1 for base access
Sep 17 16:49:58 node-1 kernel: [    0.426197] bio: create slab <bio-0> at 0
Sep 17 16:49:58 node-1 kernel: [    0.426485] ACPI: Added _OSI(Module Device)
Sep 17 16:49:58 node-1 kernel: [    0.426487] ACPI: Added _OSI(Processor Device)
Sep 17 16:49:58 node-1 kernel: [    0.426488] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 17 16:49:58 node-1 kernel: [    0.426489] ACPI: Added _OSI(Processor Aggregator Device)
Sep 17 16:49:58 node-1 kernel: [    0.439118] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 17 16:49:58 node-1 kernel: [    0.450614] ACPI: Interpreter enabled
Sep 17 16:49:58 node-1 kernel: [    0.450620] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 17 16:49:58 node-1 kernel: [    0.450624] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 17 16:49:58 node-1 kernel: [    0.450627] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 17 16:49:58 node-1 kernel: [    0.450634] ACPI: (supports S0 S4 S5)
Sep 17 16:49:58 node-1 kernel: [    0.450635] ACPI: Using IOAPIC for interrupt routing
Sep 17 16:49:58 node-1 kernel: [    0.450677] HEST: Table parsing has been initialized.
Sep 17 16:49:58 node-1 kernel: [    0.450680] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 17 16:49:58 node-1 kernel: [    0.451233] ACPI: No dock devices found.
Sep 17 16:49:58 node-1 kernel: [    0.462970] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 17 16:49:58 node-1 kernel: [    0.462975] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 17 16:49:58 node-1 kernel: [    0.462978] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 17 16:49:58 node-1 kernel: [    0.463005] PCI host bridge to bus 0000:ff
Sep 17 16:49:58 node-1 kernel: [    0.463007] pci_bus 0000:ff: root bus resource [bus ff]
Sep 17 16:49:58 node-1 kernel: [    0.463015] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463054] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 17 16:49:58 node-1 kernel: [    0.463084] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463120] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463149] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 17 16:49:58 node-1 kernel: [    0.463178] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 17 16:49:58 node-1 kernel: [    0.463209] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463238] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463267] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463295] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463322] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463348] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463377] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463404] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463431] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463458] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463486] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463514] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463541] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 17 16:49:58 node-1 kernel: [    0.463569] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463595] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 17 16:49:58 node-1 kernel: [    0.463621] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463647] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463677] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 17 16:49:58 node-1 kernel: [    0.463712] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463744] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463774] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463805] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463836] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463867] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463898] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463929] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463959] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.463992] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464025] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464058] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464091] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464122] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464150] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464181] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464214] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464253] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464288] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464321] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464352] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464381] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464412] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464445] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464478] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464509] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464541] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464572] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464601] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464631] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464661] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464692] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464724] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464781] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 17 16:49:58 node-1 kernel: [    0.464784] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 17 16:49:58 node-1 kernel: [    0.464787] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 17 16:49:58 node-1 kernel: [    0.464804] PCI host bridge to bus 0000:7f
Sep 17 16:49:58 node-1 kernel: [    0.464806] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 17 16:49:58 node-1 kernel: [    0.464811] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464838] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 17 16:49:58 node-1 kernel: [    0.464866] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464895] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464917] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 17 16:49:58 node-1 kernel: [    0.464946] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 17 16:49:58 node-1 kernel: [    0.464972] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.464998] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465022] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465046] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465069] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465092] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465116] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465138] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465161] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465186] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465208] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465231] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465253] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 17 16:49:58 node-1 kernel: [    0.465277] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465299] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 17 16:49:58 node-1 kernel: [    0.465321] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465345] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465371] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 17 16:49:58 node-1 kernel: [    0.465404] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465430] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465456] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465482] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465507] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465533] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465559] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465587] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465612] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465639] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465667] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465695] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465724] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465750] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465774] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465803] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465829] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465858] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465889] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465918] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465945] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.465973] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.466001] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.466030] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.466056] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.466083] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.466113] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.466139] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.466162] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.466188] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.466213] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.466242] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.466268] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.467511] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 17 16:49:58 node-1 kernel: [    0.467515] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 17 16:49:58 node-1 kernel: [    0.468632] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 17 16:49:58 node-1 kernel: [    0.469143] PCI host bridge to bus 0000:00
Sep 17 16:49:58 node-1 kernel: [    0.469145] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 17 16:49:58 node-1 kernel: [    0.469147] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 17 16:49:58 node-1 kernel: [    0.469148] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 17 16:49:58 node-1 kernel: [    0.469150] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 17 16:49:58 node-1 kernel: [    0.469151] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 17 16:49:58 node-1 kernel: [    0.469152] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 17 16:49:58 node-1 kernel: [    0.469154] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 17 16:49:58 node-1 kernel: [    0.469159] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 17 16:49:58 node-1 kernel: [    0.469243] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 17 16:49:58 node-1 kernel: [    0.469274] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 17 16:49:58 node-1 kernel: [    0.469316] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 17 16:49:58 node-1 kernel: [    0.469335] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 17 16:49:58 node-1 kernel: [    0.469365] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 17 16:49:58 node-1 kernel: [    0.469405] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 17 16:49:58 node-1 kernel: [    0.469423] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 17 16:49:58 node-1 kernel: [    0.469453] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 17 16:49:58 node-1 kernel: [    0.469493] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 17 16:49:58 node-1 kernel: [    0.469510] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.469580] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.469657] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.469732] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 17 16:49:58 node-1 kernel: [    0.469737] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 17 16:49:58 node-1 kernel: [    0.469823] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 17 16:49:58 node-1 kernel: [    0.469969] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 17 16:49:58 node-1 kernel: [    0.469987] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 17 16:49:58 node-1 kernel: [    0.470065] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 17 16:49:58 node-1 kernel: [    0.470120] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 17 16:49:58 node-1 kernel: [    0.470142] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 17 16:49:58 node-1 kernel: [    0.470197] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 17 16:49:58 node-1 kernel: [    0.470241] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 17 16:49:58 node-1 kernel: [    0.470269] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 17 16:49:58 node-1 kernel: [    0.470325] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 17 16:49:58 node-1 kernel: [    0.470368] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 17 16:49:58 node-1 kernel: [    0.470393] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 17 16:49:58 node-1 kernel: [    0.470411] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 17 16:49:58 node-1 kernel: [    0.470488] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 17 16:49:58 node-1 kernel: [    0.470538] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 17 16:49:58 node-1 kernel: [    0.470565] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 17 16:49:58 node-1 kernel: [    0.470813] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 17 16:49:58 node-1 kernel: [    0.470819] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 17 16:49:58 node-1 kernel: [    0.470825] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 17 16:49:58 node-1 kernel: [    0.470830] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 17 16:49:58 node-1 kernel: [    0.470838] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 17 16:49:58 node-1 kernel: [    0.470868] pci 0000:01:00.0: supports D1 D2
Sep 17 16:49:58 node-1 kernel: [    0.480944] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 17 16:49:58 node-1 kernel: [    0.480950] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 17 16:49:58 node-1 kernel: [    0.480954] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 17 16:49:58 node-1 kernel: [    0.481138] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 17 16:49:58 node-1 kernel: [    0.481171] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 17 16:49:58 node-1 kernel: [    0.488951] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 17 16:49:58 node-1 kernel: [    0.488957] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 17 16:49:58 node-1 kernel: [    0.488961] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 17 16:49:58 node-1 kernel: [    0.489054] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 17 16:49:58 node-1 kernel: [    0.489126] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 17 16:49:58 node-1 kernel: [    0.489202] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 17 16:49:58 node-1 kernel: [    0.489247] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 17 16:49:58 node-1 kernel: [    0.489251] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 17 16:49:58 node-1 kernel: [    0.489253] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 17 16:49:58 node-1 kernel: [    0.489305] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 17 16:49:58 node-1 kernel: [    0.489432] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 17 16:49:58 node-1 kernel: [    0.489486] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 17 16:49:58 node-1 kernel: [    0.489489] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 17 16:49:58 node-1 kernel: [    0.489491] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 17 16:49:58 node-1 kernel: [    0.489540] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 17 16:49:58 node-1 kernel: [    0.489659] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 17 16:49:58 node-1 kernel: [    0.489697] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 17 16:49:58 node-1 kernel: [    0.489819] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 17 16:49:58 node-1 kernel: [    0.489857] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 17 16:49:58 node-1 kernel: [    0.489977] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 17 16:49:58 node-1 kernel: [    0.490012] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 17 16:49:58 node-1 kernel: [    0.490151] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 17 16:49:58 node-1 kernel: [    0.490193] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 17 16:49:58 node-1 kernel: [    0.490196] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 17 16:49:58 node-1 kernel: [    0.490198] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 17 16:49:58 node-1 kernel: [    0.490258] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 17 16:49:58 node-1 kernel: [    0.490321] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 17 16:49:58 node-1 kernel: [    0.490373] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 17 16:49:58 node-1 kernel: [    0.490414] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 17 16:49:58 node-1 kernel: [    0.490496] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 17 16:49:58 node-1 kernel: [    0.490603] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 17 16:49:58 node-1 kernel: [    0.490605] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 17 16:49:58 node-1 kernel: [    0.490607] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 17 16:49:58 node-1 kernel: [    0.490663] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 17 16:49:58 node-1 kernel: [    0.490716] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 17 16:49:58 node-1 kernel: [    0.490765] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 17 16:49:58 node-1 kernel: [    0.490981] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 17 16:49:58 node-1 kernel: [    0.490985] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 17 16:49:58 node-1 kernel: [    0.491050] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 17 16:49:58 node-1 kernel: [    0.491118] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 17 16:49:58 node-1 kernel: [    0.491165] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 17 16:49:58 node-1 kernel: [    0.491376] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 17 16:49:58 node-1 kernel: [    0.491379] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 17 16:49:58 node-1 kernel: [    0.491442] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 17 16:49:58 node-1 kernel: [    0.491502] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 17 16:49:58 node-1 kernel: [    0.491555] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 17 16:49:58 node-1 kernel: [    0.491777] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 17 16:49:58 node-1 kernel: [    0.491781] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 17 16:49:58 node-1 kernel: [    0.491959] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 17 16:49:58 node-1 kernel: [    0.491997] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 17 16:49:58 node-1 kernel: [    0.492075] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 17 16:49:58 node-1 kernel: [    0.492094] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 17 16:49:58 node-1 kernel: [    0.492107] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 17 16:49:58 node-1 kernel: [    0.492120] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 17 16:49:58 node-1 kernel: [    0.492170] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 17 16:49:58 node-1 kernel: [    0.496958] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 17 16:49:58 node-1 kernel: [    0.496978] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 17 16:49:58 node-1 kernel: [    0.497010] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 17 16:49:58 node-1 kernel: [    0.497503] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 17 16:49:58 node-1 kernel: [    0.497506] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 17 16:49:58 node-1 kernel: [    0.497625] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 17 16:49:58 node-1 kernel: [    0.497734] PCI host bridge to bus 0000:80
Sep 17 16:49:58 node-1 kernel: [    0.497736] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 17 16:49:58 node-1 kernel: [    0.497738] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 17 16:49:58 node-1 kernel: [    0.497739] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 17 16:49:58 node-1 kernel: [    0.497747] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.497809] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.497878] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 17 16:49:58 node-1 kernel: [    0.497940] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 17 16:49:58 node-1 kernel: [    0.497946] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 17 16:49:58 node-1 kernel: [    0.498019] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 17 16:49:58 node-1 kernel: [    0.498317] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 17 16:49:58 node-1 kernel: [    0.498349] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 17 16:49:58 node-1 kernel: [    0.498379] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 17 16:49:58 node-1 kernel: [    0.498408] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 17 16:49:58 node-1 kernel: [    0.498437] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 17 16:49:58 node-1 kernel: [    0.498468] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 17 16:49:58 node-1 kernel: [    0.498498] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 17 16:49:58 node-1 kernel: [    0.498528] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 17 16:49:58 node-1 kernel: [    0.498613] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 17 16:49:58 node-1 kernel: [    0.498617] ACPI: \_SB_.UNC1: notify handler is installed
Sep 17 16:49:58 node-1 kernel: [    0.498618] ACPI: \_SB_.UNC0: notify handler is installed
Sep 17 16:49:58 node-1 kernel: [    0.498633] ACPI: \_SB_.PCI0: notify handler is installed
Sep 17 16:49:58 node-1 kernel: [    0.498686] ACPI: \_SB_.PCI1: notify handler is installed
Sep 17 16:49:58 node-1 kernel: [    0.498766] Found 4 acpi root devices
Sep 17 16:49:58 node-1 kernel: [    0.498876] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 17 16:49:58 node-1 kernel: [    0.498878] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 17 16:49:58 node-1 kernel: [    0.498879] vgaarb: loaded
Sep 17 16:49:58 node-1 kernel: [    0.498880] vgaarb: bridge control possible 0000:0c:00.0
Sep 17 16:49:58 node-1 kernel: [    0.498998] SCSI subsystem initialized
Sep 17 16:49:58 node-1 kernel: [    0.499064] libata version 3.00 loaded.
Sep 17 16:49:58 node-1 kernel: [    0.499078] ACPI: bus type USB registered
Sep 17 16:49:58 node-1 kernel: [    0.499089] usbcore: registered new interface driver usbfs
Sep 17 16:49:58 node-1 kernel: [    0.499094] usbcore: registered new interface driver hub
Sep 17 16:49:58 node-1 kernel: [    0.499118] usbcore: registered new device driver usb
Sep 17 16:49:58 node-1 kernel: [    0.499291] PCI: Using ACPI for IRQ routing
Sep 17 16:49:58 node-1 kernel: [    0.502874] PCI: pci_cache_line_size set to 64 bytes
Sep 17 16:49:58 node-1 kernel: [    0.503095] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 17 16:49:58 node-1 kernel: [    0.503096] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 17 16:49:58 node-1 kernel: [    0.503097] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 17 16:49:58 node-1 kernel: [    0.503162] NetLabel: Initializing
Sep 17 16:49:58 node-1 kernel: [    0.503163] NetLabel:  domain hash size = 128
Sep 17 16:49:58 node-1 kernel: [    0.503164] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 17 16:49:58 node-1 kernel: [    0.503174] NetLabel:  unlabeled traffic allowed by default
Sep 17 16:49:58 node-1 kernel: [    0.503231] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 17 16:49:58 node-1 kernel: [    0.503235] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 17 16:49:58 node-1 kernel: [    0.505306] Switched to clocksource hpet
Sep 17 16:49:58 node-1 kernel: [    0.509856] AppArmor: AppArmor Filesystem Enabled
Sep 17 16:49:58 node-1 kernel: [    0.509893] pnp: PnP ACPI init
Sep 17 16:49:58 node-1 kernel: [    0.509905] ACPI: bus type PNP registered
Sep 17 16:49:58 node-1 kernel: [    0.510085] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 17 16:49:58 node-1 kernel: [    0.510097] pnp 00:01: [dma 4]
Sep 17 16:49:58 node-1 kernel: [    0.510115] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 17 16:49:58 node-1 kernel: [    0.510149] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 17 16:49:58 node-1 kernel: [    0.510174] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 17 16:49:58 node-1 kernel: [    0.510195] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 17 16:49:58 node-1 kernel: [    0.510243] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 17 16:49:58 node-1 kernel: [    0.510354] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 17 16:49:58 node-1 kernel: [    0.510357] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 17 16:49:58 node-1 kernel: [    0.510358] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 17 16:49:58 node-1 kernel: [    0.510360] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 17 16:49:58 node-1 kernel: [    0.510362] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 17 16:49:58 node-1 kernel: [    0.510363] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 17 16:49:58 node-1 kernel: [    0.510367] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 17 16:49:58 node-1 kernel: [    0.510368] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 17 16:49:58 node-1 kernel: [    0.510370] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 17 16:49:58 node-1 kernel: [    0.510371] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 17 16:49:58 node-1 kernel: [    0.510373] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 17 16:49:58 node-1 kernel: [    0.510374] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 17 16:49:58 node-1 kernel: [    0.510376] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 17 16:49:58 node-1 kernel: [    0.510378] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 17 16:49:58 node-1 kernel: [    0.510479] pnp 00:07: [dma 0 disabled]
Sep 17 16:49:58 node-1 kernel: [    0.510511] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 17 16:49:58 node-1 kernel: [    0.510592] pnp 00:08: [dma 0 disabled]
Sep 17 16:49:58 node-1 kernel: [    0.510628] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 17 16:49:58 node-1 kernel: [    0.510687] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 17 16:49:58 node-1 kernel: [    0.511138] pnp: PnP ACPI: found 10 devices
Sep 17 16:49:58 node-1 kernel: [    0.511140] ACPI: bus type PNP unregistered
Sep 17 16:49:58 node-1 kernel: [    0.517195] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 17 16:49:58 node-1 kernel: [    0.517199] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 17 16:49:58 node-1 kernel: [    0.517202] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 17 16:49:58 node-1 kernel: [    0.517207] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 17 16:49:58 node-1 kernel: [    0.517209] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 17 16:49:58 node-1 kernel: [    0.517224] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 17 16:49:58 node-1 kernel: [    0.517253] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 17 16:49:58 node-1 kernel: [    0.517267] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 17 16:49:58 node-1 kernel: [    0.517299] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 17 16:49:58 node-1 kernel: [    0.517314] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 17 16:49:58 node-1 kernel: [    0.517343] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 17 16:49:58 node-1 kernel: [    0.517358] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 17 16:49:58 node-1 kernel: [    0.517387] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 17 16:49:58 node-1 kernel: [    0.517388] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 17 16:49:58 node-1 kernel: [    0.517403] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 17 16:49:58 node-1 kernel: [    0.517432] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 17 16:49:58 node-1 kernel: [    0.517434] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 17 16:49:58 node-1 kernel: [    0.517449] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 17 16:49:58 node-1 kernel: [    0.517478] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 17 16:49:58 node-1 kernel: [    0.517480] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 17 16:49:58 node-1 kernel: [    0.517483] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 17 16:49:58 node-1 kernel: [    0.517487] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 17 16:49:58 node-1 kernel: [    0.517489] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 17 16:49:58 node-1 kernel: [    0.517492] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 17 16:49:58 node-1 kernel: [    0.517496] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 17 16:49:58 node-1 kernel: [    0.517502] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 17 16:49:58 node-1 kernel: [    0.517511] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 17 16:49:58 node-1 kernel: [    0.517515] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 17 16:49:58 node-1 kernel: [    0.517522] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 17 16:49:58 node-1 kernel: [    0.517523] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 17 16:49:58 node-1 kernel: [    0.517523] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 17 16:49:58 node-1 kernel: [    0.517524] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 17 16:49:58 node-1 kernel: [    0.517525] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 17 16:49:58 node-1 kernel: [    0.517526] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 17 16:49:58 node-1 kernel: [    0.517527] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 17 16:49:58 node-1 kernel: [    0.517528] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 17 16:49:58 node-1 kernel: [    0.517529] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 17 16:49:58 node-1 kernel: [    0.517530] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 17 16:49:58 node-1 kernel: [    0.517531] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 17 16:49:58 node-1 kernel: [    0.517532] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 17 16:49:58 node-1 kernel: [    0.517533] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 17 16:49:58 node-1 kernel: [    0.517534] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 17 16:49:58 node-1 kernel: [    0.517535] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 17 16:49:58 node-1 kernel: [    0.517536] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 17 16:49:58 node-1 kernel: [    0.517537] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 17 16:49:58 node-1 kernel: [    0.517538] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 17 16:49:58 node-1 kernel: [    0.517539] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 17 16:49:58 node-1 kernel: [    0.517541] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 17 16:49:58 node-1 kernel: [    0.517542] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 17 16:49:58 node-1 kernel: [    0.517543] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 17 16:49:58 node-1 kernel: [    0.517545] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 17 16:49:58 node-1 kernel: [    0.517546] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 17 16:49:58 node-1 kernel: [    0.517585] NET: Registered protocol family 2
Sep 17 16:49:58 node-1 kernel: [    0.517882] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 17 16:49:58 node-1 kernel: [    0.518256] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 17 16:49:58 node-1 kernel: [    0.518424] TCP: Hash tables configured (established 262144 bind 65536)
Sep 17 16:49:58 node-1 kernel: [    0.518467] TCP: reno registered
Sep 17 16:49:58 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 17 16:49:58 node-1 kernel: [    0.518501] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 17 16:49:58 node-1 kernel: [    0.518616] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 17 16:49:58 node-1 kernel: [    0.518781] NET: Registered protocol family 1
Sep 17 16:49:58 node-1 kernel: [    0.557348] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 17 16:49:58 node-1 kernel: [    0.557356] PCI: CLS 64 bytes, default 64
Sep 17 16:49:58 node-1 kernel: [    0.557400] Trying to unpack rootfs image as initramfs...
Sep 17 16:49:58 node-1 kernel: [    0.779895] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Sep 17 16:49:58 node-1 kernel: [    0.779934] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 17 16:49:58 node-1 kernel: [    0.779937] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 17 16:49:58 node-1 kernel: [    0.780371] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 16:49:58 node-1 kernel: [    0.780384] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 16:49:58 node-1 kernel: [    0.780398] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 16:49:58 node-1 kernel: [    0.780410] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 16:49:58 node-1 kernel: [    0.780422] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 16:49:58 node-1 kernel: [    0.780430] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 16:49:58 node-1 kernel: [    0.780437] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 16:49:58 node-1 kernel: [    0.780442] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 16:49:58 node-1 kernel: [    0.780450] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 16:49:58 node-1 kernel: [    0.780461] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 16:49:58 node-1 kernel: [    0.780476] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 16:49:58 node-1 kernel: [    0.780488] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 16:49:58 node-1 kernel: [    0.780498] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 16:49:58 node-1 kernel: [    0.780505] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 16:49:58 node-1 kernel: [    0.780510] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 16:49:58 node-1 kernel: [    0.780516] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 17 16:49:58 node-1 kernel: [    0.780564] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 17 16:49:58 node-1 kernel: [    0.780566] Scanning for low memory corruption every 60 seconds
Sep 17 16:49:58 node-1 kernel: [    0.780861] Initialise system trusted keyring
Sep 17 16:49:58 node-1 kernel: [    0.780909] audit: initializing netlink socket (disabled)
Sep 17 16:49:58 node-1 kernel: [    0.780920] type=2000 audit(1474130962.732:1): initialized
Sep 17 16:49:58 node-1 kernel: [    0.798761] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 17 16:49:58 node-1 kernel: [    0.800219] zbud: loaded
Sep 17 16:49:58 node-1 kernel: [    0.800342] VFS: Disk quotas dquot_6.5.2
Sep 17 16:49:58 node-1 kernel: [    0.800381] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 17 16:49:58 node-1 kernel: [    0.800729] fuse init (API version 7.22)
Sep 17 16:49:58 node-1 kernel: [    0.800783] msgmni has been set to 32768
Sep 17 16:49:58 node-1 kernel: [    0.800829] Key type big_key registered
Sep 17 16:49:58 node-1 kernel: [    0.801344] Key type asymmetric registered
Sep 17 16:49:58 node-1 kernel: [    0.801346] Asymmetric key parser 'x509' registered
Sep 17 16:49:58 node-1 kernel: [    0.801368] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 17 16:49:58 node-1 kernel: [    0.801436] io scheduler noop registered
Sep 17 16:49:58 node-1 kernel: [    0.801438] io scheduler deadline registered (default)
Sep 17 16:49:58 node-1 kernel: [    0.801456] io scheduler cfq registered
Sep 17 16:49:58 node-1 kernel: [    0.801847] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    0.801977] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    0.802090] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    0.802200] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    0.802317] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    0.802411] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    0.802807] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 17 16:49:58 node-1 kernel: [    0.802833] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 17 16:49:58 node-1 kernel: [    0.802849] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 17 16:49:58 node-1 kernel: [    0.802861] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802863] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802865] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 17 16:49:58 node-1 kernel: [    0.802870] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802872] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802873] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802875] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802876] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802878] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802879] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802880] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802882] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802883] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802884] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802886] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802888] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 17 16:49:58 node-1 kernel: [    0.802899] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802901] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 17 16:49:58 node-1 kernel: [    0.802912] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802915] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 17 16:49:58 node-1 kernel: [    0.802925] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802927] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 17 16:49:58 node-1 kernel: [    0.802930] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 17 16:49:58 node-1 kernel: [    0.802968] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 17 16:49:58 node-1 kernel: [    0.802974] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 17 16:49:58 node-1 kernel: [    0.802978] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 17 16:49:58 node-1 kernel: [    0.802986] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 17 16:49:58 node-1 kernel: [    0.803022] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 17 16:49:58 node-1 kernel: [    0.803024] vesafb: scrolling: redraw
Sep 17 16:49:58 node-1 kernel: [    0.803025] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 17 16:49:58 node-1 kernel: [    0.824563] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 17 16:49:58 node-1 kernel: [    0.833060] Console: switching to colour frame buffer device 80x30
Sep 17 16:49:58 node-1 kernel: [    0.841720] fb0: VESA VGA frame buffer device
Sep 17 16:49:58 node-1 kernel: [    0.841920] intel_idle: MWAIT substates: 0x2120
Sep 17 16:49:58 node-1 kernel: [    0.841921] intel_idle: v0.4 model 0x3F
Sep 17 16:49:58 node-1 kernel: [    0.841922] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 17 16:49:58 node-1 kernel: [    0.842161] ipmi message handler version 39.2
Sep 17 16:49:58 node-1 kernel: [    0.842431] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 17 16:49:58 node-1 kernel: [    0.842864] ACPI: AC Adapter [P111] (on-line)
Sep 17 16:49:58 node-1 kernel: [    0.848087] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 17 16:49:58 node-1 kernel: [    0.859086] ACPI: Power Button [PWRB]
Sep 17 16:49:58 node-1 kernel: [    0.864846] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 17 16:49:58 node-1 kernel: [    0.876459] ACPI: Power Button [PWRF]
Sep 17 16:49:58 node-1 kernel: [    0.894926] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 17 16:49:58 node-1 kernel: [    0.906566] pstore: Registered erst as persistent store backend
Sep 17 16:49:58 node-1 kernel: [    0.912749] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 17 16:49:58 node-1 kernel: [    0.924692] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 17 16:49:58 node-1 kernel: [    0.951437] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 17 16:49:58 node-1 kernel: [    0.984894] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 17 16:49:58 node-1 kernel: [    0.999196] Linux agpgart interface v0.103
Sep 17 16:49:58 node-1 kernel: [    1.006915] brd: module loaded
Sep 17 16:49:58 node-1 kernel: [    1.014053] loop: module loaded
Sep 17 16:49:58 node-1 kernel: [    1.020880] libphy: Fixed MDIO Bus: probed
Sep 17 16:49:58 node-1 kernel: [    1.027440] tun: Universal TUN/TAP device driver, 1.6
Sep 17 16:49:58 node-1 kernel: [    1.033997] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 17 16:49:58 node-1 kernel: [    1.040590] PPP generic driver version 2.4.2
Sep 17 16:49:58 node-1 kernel: [    1.047067] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 17 16:49:58 node-1 kernel: [    1.053574] ehci-pci: EHCI PCI platform driver
Sep 17 16:49:58 node-1 kernel: [    1.060185] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 17 16:49:58 node-1 kernel: [    1.066669] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 17 16:49:58 node-1 kernel: [    1.079247] ehci-pci 0000:00:1a.0: debug port 2
Sep 17 16:49:58 node-1 kernel: [    1.089473] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 17 16:49:58 node-1 kernel: [    1.089492] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 17 16:49:58 node-1 kernel: [    1.104789] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 17 16:49:58 node-1 kernel: [    1.110900] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 17 16:49:58 node-1 kernel: [    1.117105] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 17 16:49:58 node-1 kernel: [    1.129062] usb usb1: Product: EHCI Host Controller
Sep 17 16:49:58 node-1 kernel: [    1.135113] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 17 16:49:58 node-1 kernel: [    1.141213] usb usb1: SerialNumber: 0000:00:1a.0
Sep 17 16:49:58 node-1 kernel: [    1.147238] hub 1-0:1.0: USB hub found
Sep 17 16:49:58 node-1 kernel: [    1.153079] hub 1-0:1.0: 2 ports detected
Sep 17 16:49:58 node-1 kernel: [    1.158957] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 17 16:49:58 node-1 kernel: [    1.164619] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 17 16:49:58 node-1 kernel: [    1.175593] ehci-pci 0000:00:1d.0: debug port 2
Sep 17 16:49:58 node-1 kernel: [    1.184967] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 17 16:49:58 node-1 kernel: [    1.184970] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 17 16:49:58 node-1 kernel: [    1.200708] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 17 16:49:58 node-1 kernel: [    1.205915] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 17 16:49:58 node-1 kernel: [    1.211224] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 17 16:49:58 node-1 kernel: [    1.221812] usb usb2: Product: EHCI Host Controller
Sep 17 16:49:58 node-1 kernel: [    1.227282] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 17 16:49:58 node-1 kernel: [    1.232826] usb usb2: SerialNumber: 0000:00:1d.0
Sep 17 16:49:58 node-1 kernel: [    1.238347] hub 2-0:1.0: USB hub found
Sep 17 16:49:58 node-1 kernel: [    1.243704] hub 2-0:1.0: 2 ports detected
Sep 17 16:49:58 node-1 kernel: [    1.249026] ehci-platform: EHCI generic platform driver
Sep 17 16:49:58 node-1 kernel: [    1.254270] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 17 16:49:58 node-1 kernel: [    1.259591] ohci-pci: OHCI PCI platform driver
Sep 17 16:49:58 node-1 kernel: [    1.264899] ohci-platform: OHCI generic platform driver
Sep 17 16:49:58 node-1 kernel: [    1.270102] uhci_hcd: USB Universal Host Controller Interface driver
Sep 17 16:49:58 node-1 kernel: [    1.275445] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 17 16:49:58 node-1 kernel: [    1.468487] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 17 16:49:58 node-1 kernel: [    1.776279] tsc: Refined TSC clocksource calibration: 3491.914 MHz
Sep 17 16:49:58 node-1 kernel: [    1.792559] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 17 16:49:58 node-1 kernel: [    1.798167] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 17 16:49:58 node-1 kernel: [    1.803959] hub 1-1:1.0: USB hub found
Sep 17 16:49:58 node-1 kernel: [    1.809546] hub 1-1:1.0: 6 ports detected
Sep 17 16:49:58 node-1 kernel: [    1.924122] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 17 16:49:58 node-1 kernel: [    2.314552] i8042: No controller found
Sep 17 16:49:58 node-1 kernel: [    2.320099] mousedev: PS/2 mouse device common for all mice
Sep 17 16:49:58 node-1 kernel: [    2.325860] rtc_cmos 00:02: RTC can wake from S4
Sep 17 16:49:58 node-1 kernel: [    2.328546] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 17 16:49:58 node-1 kernel: [    2.328547] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 17 16:49:58 node-1 kernel: [    2.328935] hub 2-1:1.0: USB hub found
Sep 17 16:49:58 node-1 kernel: [    2.329173] hub 2-1:1.0: 8 ports detected
Sep 17 16:49:58 node-1 kernel: [    2.354155] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 17 16:49:58 node-1 kernel: [    2.359909] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 17 16:49:58 node-1 kernel: [    2.371208] device-mapper: uevent: version 1.0.3
Sep 17 16:49:58 node-1 kernel: [    2.376981] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 17 16:49:58 node-1 kernel: [    2.388404] ledtrig-cpu: registered to indicate activity on CPUs
Sep 17 16:49:58 node-1 kernel: [    2.394425] TCP: cubic registered
Sep 17 16:49:58 node-1 kernel: [    2.400341] NET: Registered protocol family 10
Sep 17 16:49:58 node-1 kernel: [    2.406454] NET: Registered protocol family 17
Sep 17 16:49:58 node-1 kernel: [    2.412245] Key type dns_resolver registered
Sep 17 16:49:58 node-1 kernel: [    2.418311] Loading compiled-in X.509 certificates
Sep 17 16:49:58 node-1 kernel: [    2.424531] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 17 16:49:58 node-1 kernel: [    2.436182] registered taskstats version 1
Sep 17 16:49:58 node-1 kernel: [    2.444311] Key type trusted registered
Sep 17 16:49:58 node-1 kernel: [    2.452097] Key type encrypted registered
Sep 17 16:49:58 node-1 kernel: [    2.457603] AppArmor: AppArmor sha1 policy hashing enabled
Sep 17 16:49:58 node-1 kernel: [    2.463112] IMA: No TPM chip found, activating TPM-bypass!
Sep 17 16:49:58 node-1 kernel: [    2.469180] regulator-dummy: disabling
Sep 17 16:49:58 node-1 kernel: [    2.474677]   Magic number: 0:780:843
Sep 17 16:49:58 node-1 kernel: [    2.480246] acpi device:c4: hash matches
Sep 17 16:49:58 node-1 kernel: [    2.485885] rtc_cmos 00:02: setting system clock to 2016-09-17 16:49:24 UTC (1474130964)
Sep 17 16:49:58 node-1 kernel: [    2.498408] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 17 16:49:58 node-1 kernel: [    2.504026] EDD information not available.
Sep 17 16:49:58 node-1 kernel: [    2.509570] PM: Hibernation image not present or could not be loaded.
Sep 17 16:49:58 node-1 kernel: [    2.510382] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 17 16:49:58 node-1 kernel: [    2.521670] Write protecting the kernel read-only data: 12288k
Sep 17 16:49:58 node-1 kernel: [    2.528005] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 17 16:49:58 node-1 kernel: [    2.540786] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 17 16:49:58 node-1 kernel: [    2.573818] device-mapper: multipath: version 1.6.0 loaded
Sep 17 16:49:58 node-1 kernel: [    2.581592] systemd-udevd[216]: starting version 204
Sep 17 16:49:58 node-1 kernel: [    2.601921] md: linear personality registered for level -1
Sep 17 16:49:58 node-1 kernel: [    2.603883] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 17 16:49:58 node-1 kernel: [    2.622366] md: multipath personality registered for level -4
Sep 17 16:49:58 node-1 kernel: [    2.630421] md: raid0 personality registered for level 0
Sep 17 16:49:58 node-1 kernel: [    2.638695] md: raid1 personality registered for level 1
Sep 17 16:49:58 node-1 kernel: [    2.647493] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 17 16:49:58 node-1 kernel: [    2.653710] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 17 16:49:58 node-1 kernel: [    2.659922] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 17 16:49:58 node-1 kernel: [    2.661323] megasas: FW now in Ready state
Sep 17 16:49:58 node-1 kernel: [    2.661600] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.661710] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.661822] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.661908] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.662017] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.662055] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.662185] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.662317] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.662424] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.662513] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.662623] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.662681] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.662822] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.662964] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.663085] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.663236] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.664128] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 17 16:49:58 node-1 kernel: [    2.693522] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Sep 17 16:49:58 node-1 kernel: [    2.706686] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 17 16:49:58 node-1 kernel: [    2.711459] raid6: sse2x1    7379 MB/s
Sep 17 16:49:58 node-1 kernel: [    2.727289] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 17 16:49:58 node-1 kernel: [    2.734316] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.734322] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.734326] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.734331] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.734377] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 17 16:49:58 node-1 kernel: [    2.738085] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 17 16:49:58 node-1 kernel: [    2.738086] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 17 16:49:58 node-1 kernel: [    2.738087] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 17 16:49:58 node-1 kernel: [    2.738087] usb 2-1.4: Manufacturer: Avocent
Sep 17 16:49:58 node-1 kernel: [    2.738088] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 17 16:49:58 node-1 kernel: [    2.779603] raid6: sse2x2    4789 MB/s
Sep 17 16:49:58 node-1 kernel: [    2.847309] raid6: sse2x4    8854 MB/s
Sep 17 16:49:58 node-1 kernel: [    2.919264] raid6: avx2x1   14956 MB/s
Sep 17 16:49:58 node-1 kernel: [    2.991194] raid6: avx2x2   18898 MB/s
Sep 17 16:49:58 node-1 kernel: [    3.063144] raid6: avx2x4   21221 MB/s
Sep 17 16:49:58 node-1 kernel: [    3.068694] raid6: using algorithm avx2x4 (21221 MB/s)
Sep 17 16:49:58 node-1 kernel: [    3.074173] raid6: using avx2x2 recovery algorithm
Sep 17 16:49:58 node-1 kernel: [    3.079552] megasas:IOC Init cmd success
Sep 17 16:49:58 node-1 kernel: [    3.079554] Switched to clocksource tsc
Sep 17 16:49:58 node-1 kernel: [    3.090348] hidraw: raw HID events driver (C) Jiri Kosina
Sep 17 16:49:58 node-1 kernel: [    3.095779] xor: automatically using best checksumming function:
Sep 17 16:49:58 node-1 kernel: [    3.101114] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Sep 17 16:49:58 node-1 kernel: [    3.101115] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Sep 17 16:49:58 node-1 kernel: [    3.101116] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 17 16:49:58 node-1 kernel: [    3.101179] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.101221] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.101230] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.101266] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.101304] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.101345] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.101442] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.114325] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Sep 17 16:49:58 node-1 kernel: [    3.114326] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 17 16:49:58 node-1 kernel: [    3.114327] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 17 16:49:58 node-1 kernel: [    3.114382] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.114413] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.114444] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.114480] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.114542] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.115180] megasas: INIT adapter done
Sep 17 16:49:58 node-1 kernel: [    3.126213] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Sep 17 16:49:58 node-1 kernel: [    3.126214] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 17 16:49:58 node-1 kernel: [    3.126215] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 17 16:49:58 node-1 kernel: [    3.126274] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.126314] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.126350] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.126381] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.126450] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 17 16:49:58 node-1 kernel: [    3.187100] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 17 16:49:58 node-1 kernel: [    3.187521] scsi0 : LSI SAS based MegaRAID driver
Sep 17 16:49:58 node-1 kernel: [    3.194792] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 17 16:49:58 node-1 kernel: [    3.206129] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 17 16:49:58 node-1 kernel: [    3.210254] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 17 16:49:58 node-1 kernel: [    3.210337] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 17 16:49:58 node-1 kernel: [    3.210640] sd 0:2:0:0: [sda] Write Protect is off
Sep 17 16:49:58 node-1 kernel: [    3.210641] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 17 16:49:58 node-1 kernel: [    3.210710] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 17 16:49:58 node-1 kernel: [    3.242579]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Sep 17 16:49:58 node-1 kernel: [    3.243168] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 17 16:49:58 node-1 kernel: [    3.318808] usbcore: registered new interface driver usbhid
Sep 17 16:49:58 node-1 kernel: [    3.325400] usbhid: USB HID core driver
Sep 17 16:49:58 node-1 kernel: [    3.332816] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Sep 17 16:49:58 node-1 kernel: [    3.345912] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Sep 17 16:49:58 node-1 kernel: [    3.355527]    avx       : 37711.000 MB/sec
Sep 17 16:49:58 node-1 kernel: [    3.366147] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Sep 17 16:49:58 node-1 kernel: [    3.380095] async_tx: api initialized (async)
Sep 17 16:49:58 node-1 kernel: [    3.380117] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Sep 17 16:49:58 node-1 kernel: [    3.380174] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Sep 17 16:49:58 node-1 kernel: [    3.380263] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Sep 17 16:49:58 node-1 kernel: [    3.432515] md: raid6 personality registered for level 6
Sep 17 16:49:58 node-1 kernel: [    3.439714] md: raid5 personality registered for level 5
Sep 17 16:49:58 node-1 kernel: [    3.446757] md: raid4 personality registered for level 4
Sep 17 16:49:58 node-1 kernel: [    3.456715] md: raid10 personality registered for level 10
Sep 17 16:49:58 node-1 kernel: [    3.472452] random: lvm urandom read with 33 bits of entropy available
Sep 17 16:49:58 node-1 kernel: [    3.526066] multipathd (369): /proc/369/oom_adj is deprecated, please use /proc/369/oom_score_adj instead.
Sep 17 16:49:58 node-1 kernel: [    3.610962] bio: create slab <bio-1> at 1
Sep 17 16:49:58 node-1 kernel: [    4.521408] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Sep 17 16:49:58 node-1 kernel: [    5.137721] random: nonblocking pool is initialized
Sep 17 16:49:58 node-1 kernel: [    5.228466] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Sep 17 16:49:58 node-1 kernel: [    5.288160] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 17 16:49:58 node-1 kernel: [    5.469997] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 17 16:49:58 node-1 kernel: [    5.499923] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 17 16:49:58 node-1 kernel: [    5.557595] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 17 16:49:58 node-1 kernel: [    5.732260] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 17 16:49:58 node-1 kernel: [    5.776835] XFS (dm-1): Mounting Filesystem
Sep 17 16:49:58 node-1 kernel: [    6.020048] XFS (dm-1): Ending clean mount
Sep 17 16:49:58 node-1 kernel: [    6.084566] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 17 16:49:58 node-1 kernel: [    6.128261] XFS (dm-2): Mounting Filesystem
Sep 17 16:49:58 node-1 kernel: [    6.248649] XFS (dm-2): Ending clean mount
Sep 17 16:49:58 node-1 kernel: [    6.327343] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Sep 17 16:49:58 node-1 kernel: [    8.087833] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 17 16:49:58 node-1 kernel: [    8.114008] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 17 16:49:58 node-1 kernel: [    8.238381] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 17 16:49:58 node-1 kernel: [    8.238387] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 17 16:49:58 node-1 kernel: [    8.238392] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 17 16:49:58 node-1 kernel: [    8.238396] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 17 16:49:58 node-1 kernel: [    8.271981] systemd-udevd[803]: starting version 204
Sep 17 16:49:58 node-1 kernel: [    8.531452] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 17 16:49:58 node-1 kernel: [    8.535281] power_meter ACPI000D:00: Found ACPI power meter.
Sep 17 16:49:58 node-1 kernel: [    8.535290] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 17 16:49:58 node-1 kernel: [    8.543024] wmi: Mapper loaded
Sep 17 16:49:58 node-1 kernel: [    8.543742] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 17 16:49:58 node-1 kernel: [    8.543747] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 17 16:49:58 node-1 kernel: [    8.543749] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 17 16:49:58 node-1 kernel: [    8.543751] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 17 16:49:58 node-1 kernel: [    8.543764] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 17 16:49:58 node-1 kernel: [    8.549781] IPMI System Interface driver.
Sep 17 16:49:58 node-1 kernel: [    8.549816] ipmi_si: probing via ACPI
Sep 17 16:49:58 node-1 kernel: [    8.549827] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 17 16:49:58 node-1 kernel: [    8.549828] ipmi_si: Adding ACPI-specified kcs state machine
Sep 17 16:49:58 node-1 kernel: [    8.549836] ipmi_si: probing via SMBIOS
Sep 17 16:49:58 node-1 kernel: [    8.549837] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 17 16:49:58 node-1 kernel: [    8.549837] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 17 16:49:58 node-1 kernel: [    8.549839] ipmi_si: probing via SPMI
Sep 17 16:49:58 node-1 kernel: [    8.549839] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 17 16:49:58 node-1 kernel: [    8.549840] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 17 16:49:58 node-1 kernel: [    8.549841] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 17 16:49:58 node-1 kernel: [    8.614899] systemd-udevd[833]: renamed network interface eth1 to enp7s0
Sep 17 16:49:58 node-1 kernel: [    8.638780] systemd-udevd[845]: renamed network interface eth2 to enp8s0
Sep 17 16:49:58 node-1 kernel: [    8.670751] systemd-udevd[825]: renamed network interface eth0 to enp6s0
Sep 17 16:49:58 node-1 kernel: [    8.706749] systemd-udevd[821]: renamed network interface eth3 to enp9s0
Sep 17 16:49:58 node-1 kernel: [    8.739544] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 17 16:49:58 node-1 kernel: [    8.739550] ipmi_si 00:09: IPMI kcs interface initialized
Sep 17 16:49:58 node-1 kernel: [    8.982506] type=1400 audit(1474130970.999:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1091 comm="apparmor_parser"
Sep 17 16:49:58 node-1 kernel: [    8.982561] type=1400 audit(1474130970.999:3): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1096 comm="apparmor_parser"
Sep 17 16:49:58 node-1 kernel: [    8.982659] type=1400 audit(1474130970.999:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1091 comm="apparmor_parser"
Sep 17 16:49:58 node-1 kernel: [    8.982707] type=1400 audit(1474130970.999:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1096 comm="apparmor_parser"
Sep 17 16:49:58 node-1 kernel: [    8.982794] type=1400 audit(1474130970.999:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1091 comm="apparmor_parser"
Sep 17 16:49:58 node-1 kernel: [    8.982837] type=1400 audit(1474130970.999:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1096 comm="apparmor_parser"
Sep 17 16:49:58 node-1 kernel: [    8.996080] type=1400 audit(1474130971.011:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1094 comm="apparmor_parser"
Sep 17 16:49:58 node-1 kernel: [    8.996235] type=1400 audit(1474130971.011:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1094 comm="apparmor_parser"
Sep 17 16:49:58 node-1 kernel: [    8.996355] type=1400 audit(1474130971.011:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1094 comm="apparmor_parser"
Sep 17 16:49:58 node-1 kernel: [    9.001549] type=1400 audit(1474130971.015:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1088 comm="apparmor_parser"
Sep 17 16:49:58 node-1 kernel: [    9.533387] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 17 16:49:58 node-1 kernel: [    9.538352] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 17 16:49:58 node-1 kernel: [    9.740545] enic 0000:06:00.0 enp6s0: Link UP
Sep 17 16:49:58 node-1 kernel: [    9.741078] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 17 16:49:58 node-1 kernel: [    9.741088] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 17 16:49:58 node-1 kernel: [   19.571890] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 17 16:50:00 node-1 failsafe: Failsafe of 120 seconds reached.
Sep 17 16:50:00 node-1 kernel: [   37.791108] init: failsafe main process (8447) killed by TERM signal
Sep 17 16:50:00 node-1 dbus[8493]: [system] AppArmor D-Bus mediation is enabled
Sep 17 16:50:00 node-1 kernel: [   38.086253] audit_printk_skb: 30 callbacks suppressed
Sep 17 16:50:00 node-1 kernel: [   38.086254] type=1400 audit(1474131000.412:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8572 comm="apparmor_parser"
Sep 17 16:50:00 node-1 kernel: [   38.086258] type=1400 audit(1474131000.412:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8572 comm="apparmor_parser"
Sep 17 16:50:00 node-1 kernel: [   38.086260] type=1400 audit(1474131000.412:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8572 comm="apparmor_parser"
Sep 17 16:50:00 node-1 kernel: [   38.086479] type=1400 audit(1474131000.412:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8572 comm="apparmor_parser"
Sep 17 16:50:00 node-1 kernel: [   38.086481] type=1400 audit(1474131000.412:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8572 comm="apparmor_parser"
Sep 17 16:50:00 node-1 kernel: [   38.086593] type=1400 audit(1474131000.412:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8572 comm="apparmor_parser"
Sep 17 16:50:00 node-1 kernel: [   38.089372] type=1400 audit(1474131000.416:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8573 comm="apparmor_parser"
Sep 17 16:50:00 node-1 kernel: [   38.170431] type=1400 audit(1474131000.496:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8575 comm="apparmor_parser"
Sep 17 16:50:00 node-1 anacron[8623]: Anacron 2.3 started on 2016-09-17
Sep 17 16:50:00 node-1 anacron[8623]: Will run job `cron.daily' in 5 min.
Sep 17 16:50:00 node-1 anacron[8623]: Will run job `cron.weekly' in 10 min.
Sep 17 16:50:00 node-1 anacron[8623]: Will run job `cron.monthly' in 15 min.
Sep 17 16:50:00 node-1 anacron[8623]: Jobs will be executed sequentially
Sep 17 16:50:00 node-1 cron[8605]: (CRON) INFO (pidfile fd = 3)
Sep 17 16:50:00 node-1 multipathd: path checkers start up
Sep 17 16:50:00 node-1 cron[8678]: (CRON) STARTUP (fork ok)
Sep 17 16:50:00 node-1 cron[8678]: (CRON) INFO (Running @reboot jobs)
Sep 17 16:50:01 node-1 postfix/master[8784]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 17 16:50:04 node-1 puppet-agent[8969]: Reopening log files
Sep 17 16:50:06 node-1 puppet-agent[8969]: Could not request certificate: Connection refused - connect(2)
Sep 17 16:50:18 node-1 puppet-user[9177]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 17 16:50:18 node-1 puppet-user[9177]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 17 16:50:19 node-1 puppet-user[9177]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 17 16:50:19 node-1 puppet-user[9177]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 17 16:50:19 node-1 puppet-user[9177]: Finished catalog run in 0.97 seconds
Sep 17 16:50:21 node-1 multipathd: uevent trigger error
Sep 17 16:50:21 node-1 puppet-user[9612]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 17 16:50:21 node-1 puppet-user[9612]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Sep 17 16:50:21 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 17 16:50:21 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 17 16:50:21 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Sep 17 16:50:21 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 17 16:50:21 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 17 16:50:21 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 17 16:50:21 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 17 16:50:21 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 17 16:50:21 node-1 puppet-user[9612]: Finished catalog run in 0.06 seconds
Sep 17 16:50:22 node-1 puppet-user[10075]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 17 16:50:22 node-1 puppet-user[10075]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Sep 17 16:50:23 node-1 puppet-user[10075]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 17 16:50:23 node-1 puppet-user[10075]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 17 16:50:23 node-1 puppet-user[10075]: Finished catalog run in 0.03 seconds
Sep 17 16:50:24 node-1 puppet-user[10540]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 17 16:50:24 node-1 puppet-user[10540]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 17 16:50:25 node-1 puppet-user[10540]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 17 16:50:25 node-1 puppet-user[10540]: Finished catalog run in 0.06 seconds
Sep 17 16:50:26 node-1 puppet-user[10994]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 17 16:50:26 node-1 puppet-user[10994]: Compiled catalog for node-1.domain.tld in environment production in 0.21 seconds
Sep 17 16:50:26 node-1 puppet-user[10994]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 17 16:50:27 node-1 puppet-user[10994]: (/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
Sep 17 16:50:27 node-1 puppet-user[10994]: Finished catalog run in 0.43 seconds
Sep 17 16:50:28 node-1 puppet-user[11657]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 17 16:50:28 node-1 puppet-user[11657]: Compiled catalog for node-1.domain.tld in environment production in 0.22 seconds
Sep 17 16:50:28 node-1 puppet-user[11657]: (/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
Sep 17 16:50:28 node-1 puppet-user[11657]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 17 16:50:28 node-1 puppet-user[11657]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 17 16:50:28 node-1 puppet-user[11657]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 17 16:50:28 node-1 puppet-user[11657]: Finished catalog run in 0.27 seconds
Sep 17 16:50:30 node-1 puppet-user[12132]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 17 16:50:30 node-1 puppet-user[12132]: Compiled catalog for node-1.domain.tld in environment production in 0.16 seconds
Sep 17 16:50:30 node-1 puppet-user[12132]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 17 16:50:30 node-1 kernel: [   68.282090] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 17 16:50:30 node-1 kernel: [   68.282144] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Sep 17 16:50:30 node-1 puppet-user[12132]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Sep 17 16:50:30 node-1 puppet-user[12132]: Finished catalog run in 0.07 seconds
Sep 17 16:50:32 node-1 puppet-user[12591]: (Scope(Class[main])) MODULAR: sync_time
Sep 17 16:50:32 node-1 puppet-user[12591]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 17 16:50:32 node-1 ntpdate[13009]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 17 16:50:38 node-1 ntpdate[13009]: adjust time server 10.20.0.2 offset -0.140348 sec
Sep 17 16:50:38 node-1 puppet-user[12591]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 17 16:50:38 node-1 puppet-user[12591]: Finished catalog run in 6.19 seconds
Sep 17 16:50:38 node-1 kernel: [   76.514016] init: plymouth-upstart-bridge main process ended, respawning
Sep 17 16:50:39 node-1 puppet-agent[8969]: Could not run: SIGTERM
Sep 17 16:50:39 node-1 kernel: [   76.784318] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 17 16:50:39 node-1 ec2: 
Sep 17 16:50:39 node-1 ec2: #############################################################
Sep 17 16:50:39 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 17 16:50:39 node-1 ec2: 1024 89:86:04:53:35:bb:40:db:df:91:bd:87:25:9c:5b:fb  root@node-1.domain.tld (DSA)
Sep 17 16:50:39 node-1 ec2: 256 2c:5c:a4:b0:07:37:33:5d:bb:9d:e4:05:a8:3f:b1:41  root@node-1.domain.tld (ECDSA)
Sep 17 16:50:39 node-1 ec2: 256 85:fa:9a:77:b7:27:14:d8:b6:4c:84:34:bc:97:37:8c  root@node-1.domain.tld (ED25519)
Sep 17 16:50:39 node-1 ec2: 2048 ae:b2:99:d8:e0:12:97:8c:71:e3:57:d8:39:e2:11:06  root@node-1.domain.tld (RSA)
Sep 17 16:50:39 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 17 16:50:39 node-1 ec2: #############################################################
Sep 17 16:50:44 node-1 puppet-user[13382]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 17 16:50:44 node-1 puppet-user[13382]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Sep 17 16:50:44 node-1 puppet-user[13382]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 17 16:50:44 node-1 puppet-user[13382]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs"]'
Sep 17 16:50:44 node-1 puppet-user[13382]: Finished catalog run in 0.07 seconds
Sep 17 16:50:46 node-1 puppet-user[13851]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 17 16:50:46 node-1 puppet-user[13851]: Compiled catalog for node-1.domain.tld in environment production in 0.54 seconds
Sep 17 16:50:47 node-1 puppet-user[13851]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Sep 17 16:50:47 node-1 puppet-user[13851]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Sep 17 16:50:47 node-1 puppet-user[13851]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Sep 17 16:50:47 node-1 puppet-user[13851]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Sep 17 16:50:47 node-1 puppet-user[13851]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 17 16:50:47 node-1 puppet-user[13851]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep 17 16:50:47 node-1 puppet-user[13851]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 17 16:50:47 node-1 puppet-user[13851]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep 17 16:50:47 node-1 puppet-user[13851]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Sep 17 16:50:47 node-1 puppet-user[13851]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep 17 16:50:47 node-1 puppet-user[13851]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 17 16:50:47 node-1 puppet-user[13851]: Finished catalog run in 0.82 seconds
Sep 17 16:50:49 node-1 puppet-user[14363]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 17 16:50:49 node-1 puppet-user[14363]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Sep 17 16:50:53 node-1 puppet-user[14363]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 17 16:51:01 node-1 CRON[16197]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep 17 16:51:03 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 17 16:51:03 node-1 nailgun-agent: I, [2016-09-17T16:51:03.056013 #16200]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 17 16:51:15 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 17 16:51:16 node-1 nailgun-agent: I, [2016-09-17T16:51:16.082148 #16200]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep 17 16:51:24 node-1 puppet-user[14363]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 17 16:51:24 node-1 puppet-user[14363]: Finished catalog run in 34.74 seconds
Sep 17 16:51:26 node-1 puppet-user[17591]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 17 16:51:26 node-1 puppet-user[17591]: Compiled catalog for node-1.domain.tld in environment production in 0.60 seconds
Sep 17 16:51:27 node-1 puppet-user[17591]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 17 16:51:27 node-1 puppet-user[17591]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 17 16:51:27 node-1 puppet-user[17591]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 17 16:51:27 node-1 puppet-user[17591]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 17 16:51:27 node-1 puppet-user[17591]: Finished catalog run in 0.14 seconds
Sep 17 16:51:28 node-1 puppet-user[18056]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 17 16:51:29 node-1 puppet-user[18056]: Compiled catalog for node-1.domain.tld in environment production in 0.95 seconds
Sep 17 16:51:30 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 17 16:51:30 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 17 16:51:30 node-1 crontab[18498]: (root) LIST (root)
Sep 17 16:51:30 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 17 16:51:30 node-1 crontab[18499]: (root) REPLACE (root)
Sep 17 16:51:31 node-1 puppet-user[18056]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 17 16:51:32 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 17 16:51:33 node-1 puppet-user[18056]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep 17 16:51:33 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8420" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 17 16:51:33 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 17 16:51:35 node-1 multipathd: uevent trigger error
<27>Sep 17 16:51:35 node-1 multipathd: uevent trigger error
<27>Sep 17 16:51:35 node-1 multipathd: uevent trigger error
<27>Sep 17 16:51:35 node-1 multipathd: uevent trigger error
<27>Sep 17 16:51:35 node-1 multipathd: uevent trigger error
<27>Sep 17 16:51:49 node-1 multipathd: uevent trigger error
<27>Sep 17 16:51:49 node-1 multipathd: uevent trigger error
<27>Sep 17 16:51:49 node-1 multipathd: uevent trigger error
<27>Sep 17 16:51:49 node-1 multipathd: uevent trigger error
<27>Sep 17 16:51:49 node-1 multipathd: uevent trigger error
<27>Sep 17 16:51:49 node-1 multipathd: uevent trigger error
<27>Sep 17 16:51:49 node-1 multipathd: uevent trigger error
<27>Sep 17 16:52:39 node-1 ntpdate[28521]: no servers can be used, exiting
<27>Sep 17 16:52:39 node-1 ntpdate[28684]: no servers can be used, exiting
<27>Sep 17 16:52:39 node-1 ntpdate[28929]: no servers can be used, exiting
<27>Sep 17 16:53:11 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:11 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:11 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:11 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:11 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:14 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:14 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:14 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:14 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:14 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:24 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:24 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:24 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:24 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:25 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:25 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:28 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:28 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:28 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:28 node-1 multipathd: uevent trigger error
<27>Sep 17 16:53:28 node-1 multipathd: uevent trigger error
<27>Sep 17 16:54:25 node-1 multipathd: uevent trigger error
<27>Sep 17 16:54:25 node-1 multipathd: uevent trigger error
<27>Sep 17 16:54:25 node-1 multipathd: uevent trigger error
<27>Sep 17 16:54:25 node-1 multipathd: uevent trigger error
<27>Sep 17 16:54:25 node-1 multipathd: uevent trigger error
<27>Sep 17 16:54:25 node-1 multipathd: uevent trigger error
<27>Sep 17 16:54:34 node-1 multipathd: uevent trigger error
<27>Sep 17 16:54:34 node-1 multipathd: uevent trigger error
<27>Sep 17 16:54:34 node-1 multipathd: uevent trigger error
<27>Sep 17 16:54:34 node-1 multipathd: uevent trigger error
<27>Sep 17 16:54:34 node-1 multipathd: uevent trigger error
<27>Sep 17 16:54:34 node-1 multipathd: uevent trigger error
<27>Sep 17 16:54:36 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 17 16:54:36 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 17 16:54:42 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 17 16:54:42 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 17 16:54:48 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 17 16:54:53 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 17 16:54:53 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 17 16:55:01 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:01 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:01 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:01 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:01 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:14 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:14 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:14 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:14 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:14 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:14 node-1 multipathd: uevent trigger error
<129>Sep 17 16:55:16 node-1 haproxy[17448]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:17 node-1 haproxy[17452]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:17 node-1 haproxy[17452]: 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>Sep 17 16:55:17 node-1 haproxy[17452]: proxy mysqld has no server available!
<27>Sep 17 16:55:19 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:19 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:19 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:19 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:19 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:19 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:19 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:19 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:19 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:23 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:23 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:23 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:23 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:23 node-1 multipathd: uevent trigger error
<129>Sep 17 16:55:25 node-1 haproxy[20338]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:25 node-1 haproxy[20338]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:26 node-1 haproxy[20342]: 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>Sep 17 16:55:26 node-1 haproxy[20342]: proxy mysqld has no server available!
<129>Sep 17 16:55:26 node-1 haproxy[20342]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:26 node-1 haproxy[20342]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:27 node-1 haproxy[20342]: 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>Sep 17 16:55:27 node-1 haproxy[20342]: proxy object-storage has no server available!
<27>Sep 17 16:55:28 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:28 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:28 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:28 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:28 node-1 multipathd: uevent trigger error
<129>Sep 17 16:55:30 node-1 haproxy[21735]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:31 node-1 haproxy[21739]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:31 node-1 haproxy[21739]: 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>Sep 17 16:55:31 node-1 haproxy[21739]: proxy neutron has no server available!
<129>Sep 17 16:55:31 node-1 haproxy[21739]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:31 node-1 haproxy[21739]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:31 node-1 haproxy[21739]: 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>Sep 17 16:55:31 node-1 haproxy[21739]: proxy mysqld has no server available!
<129>Sep 17 16:55:32 node-1 haproxy[21739]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:32 node-1 haproxy[21739]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:32 node-1 haproxy[21739]: 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>Sep 17 16:55:32 node-1 haproxy[21739]: proxy object-storage has no server available!
<27>Sep 17 16:55:33 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:34 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:34 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:34 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:34 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:34 node-1 multipathd: uevent trigger error
<129>Sep 17 16:55:36 node-1 haproxy[23324]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:36 node-1 haproxy[23324]: 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>Sep 17 16:55:36 node-1 haproxy[23324]: 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>Sep 17 16:55:36 node-1 haproxy[23324]: proxy keystone-1 has no server available!
<129>Sep 17 16:55:36 node-1 haproxy[23324]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:36 node-1 haproxy[23324]: 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>Sep 17 16:55:36 node-1 haproxy[23324]: 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>Sep 17 16:55:36 node-1 haproxy[23324]: proxy keystone-2 has no server available!
<129>Sep 17 16:55:37 node-1 haproxy[23330]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:37 node-1 haproxy[23330]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:37 node-1 haproxy[23330]: 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>Sep 17 16:55:37 node-1 haproxy[23330]: proxy neutron has no server available!
<129>Sep 17 16:55:37 node-1 haproxy[23330]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:37 node-1 haproxy[23330]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:37 node-1 haproxy[23330]: 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>Sep 17 16:55:37 node-1 haproxy[23330]: proxy mysqld has no server available!
<129>Sep 17 16:55:37 node-1 haproxy[23330]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:38 node-1 haproxy[23330]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:38 node-1 haproxy[23330]: 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>Sep 17 16:55:38 node-1 haproxy[23330]: proxy object-storage has no server available!
<27>Sep 17 16:55:39 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:39 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:39 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:39 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:39 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:39 node-1 multipathd: uevent trigger error
<129>Sep 17 16:55:41 node-1 haproxy[24750]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:41 node-1 haproxy[24750]: 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>Sep 17 16:55:41 node-1 haproxy[24750]: 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>Sep 17 16:55:41 node-1 haproxy[24750]: proxy keystone-1 has no server available!
<129>Sep 17 16:55:42 node-1 haproxy[24754]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:42 node-1 haproxy[24754]: 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>Sep 17 16:55:42 node-1 haproxy[24754]: 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>Sep 17 16:55:42 node-1 haproxy[24754]: proxy keystone-2 has no server available!
<129>Sep 17 16:55:42 node-1 haproxy[24754]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:42 node-1 haproxy[24754]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:42 node-1 haproxy[24754]: 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>Sep 17 16:55:42 node-1 haproxy[24754]: proxy neutron has no server available!
<129>Sep 17 16:55:42 node-1 haproxy[24754]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:42 node-1 haproxy[24754]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:42 node-1 haproxy[24754]: 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>Sep 17 16:55:42 node-1 haproxy[24754]: proxy mysqld has no server available!
<129>Sep 17 16:55:43 node-1 haproxy[24754]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:43 node-1 haproxy[24754]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:43 node-1 haproxy[24754]: 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>Sep 17 16:55:43 node-1 haproxy[24754]: proxy object-storage has no server available!
<129>Sep 17 16:55:43 node-1 haproxy[24754]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:43 node-1 haproxy[24754]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:43 node-1 haproxy[24754]: 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>Sep 17 16:55:43 node-1 haproxy[24754]: proxy aodh has no server available!
<27>Sep 17 16:55:45 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:45 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:45 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:45 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:45 node-1 multipathd: uevent trigger error
<129>Sep 17 16:55:47 node-1 haproxy[26185]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:47 node-1 haproxy[26185]: 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>Sep 17 16:55:47 node-1 haproxy[26185]: 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>Sep 17 16:55:47 node-1 haproxy[26185]: proxy keystone-1 has no server available!
<129>Sep 17 16:55:47 node-1 haproxy[26185]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:47 node-1 haproxy[26185]: 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>Sep 17 16:55:47 node-1 haproxy[26185]: 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>Sep 17 16:55:47 node-1 haproxy[26185]: proxy keystone-2 has no server available!
<129>Sep 17 16:55:47 node-1 haproxy[26185]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:48 node-1 haproxy[26189]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:48 node-1 haproxy[26189]: 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>Sep 17 16:55:48 node-1 haproxy[26189]: proxy neutron has no server available!
<129>Sep 17 16:55:48 node-1 haproxy[26189]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:48 node-1 haproxy[26189]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:48 node-1 haproxy[26189]: 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>Sep 17 16:55:48 node-1 haproxy[26189]: proxy mysqld has no server available!
<129>Sep 17 16:55:48 node-1 haproxy[26189]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:48 node-1 haproxy[26189]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:48 node-1 haproxy[26189]: 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>Sep 17 16:55:48 node-1 haproxy[26189]: proxy object-storage has no server available!
<129>Sep 17 16:55:48 node-1 haproxy[26189]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:48 node-1 haproxy[26189]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:49 node-1 haproxy[26189]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 17 16:55:49 node-1 haproxy[26189]: proxy aodh has no server available!
<129>Sep 17 16:55:49 node-1 haproxy[26189]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:49 node-1 haproxy[26189]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:49 node-1 haproxy[26189]: 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>Sep 17 16:55:49 node-1 haproxy[26189]: proxy ceilometer has no server available!
<27>Sep 17 16:55:50 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:50 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:50 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:50 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:50 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:50 node-1 multipathd: uevent trigger error
<129>Sep 17 16:55:53 node-1 haproxy[27583]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:53 node-1 haproxy[27583]: 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>Sep 17 16:55:53 node-1 haproxy[27583]: 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>Sep 17 16:55:53 node-1 haproxy[27583]: proxy keystone-1 has no server available!
<129>Sep 17 16:55:53 node-1 haproxy[27583]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:53 node-1 haproxy[27583]: 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>Sep 17 16:55:53 node-1 haproxy[27583]: 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>Sep 17 16:55:53 node-1 haproxy[27583]: proxy keystone-2 has no server available!
<129>Sep 17 16:55:53 node-1 haproxy[27583]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:53 node-1 haproxy[27583]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:53 node-1 haproxy[27583]: 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>Sep 17 16:55:53 node-1 haproxy[27583]: proxy neutron has no server available!
<129>Sep 17 16:55:53 node-1 haproxy[27583]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:53 node-1 haproxy[27583]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:54 node-1 haproxy[27587]: 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>Sep 17 16:55:54 node-1 haproxy[27587]: proxy mysqld has no server available!
<129>Sep 17 16:55:54 node-1 haproxy[27587]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:54 node-1 haproxy[27587]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:54 node-1 haproxy[27587]: 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>Sep 17 16:55:54 node-1 haproxy[27587]: proxy object-storage has no server available!
<129>Sep 17 16:55:54 node-1 haproxy[27587]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:54 node-1 haproxy[27587]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:54 node-1 haproxy[27587]: 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>Sep 17 16:55:54 node-1 haproxy[27587]: proxy aodh has no server available!
<129>Sep 17 16:55:54 node-1 haproxy[27587]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:54 node-1 haproxy[27587]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:54 node-1 haproxy[27587]: 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>Sep 17 16:55:54 node-1 haproxy[27587]: proxy ceilometer has no server available!
<27>Sep 17 16:55:56 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:56 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:56 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:56 node-1 multipathd: uevent trigger error
<27>Sep 17 16:55:56 node-1 multipathd: uevent trigger error
<129>Sep 17 16:55:58 node-1 haproxy[28980]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:58 node-1 haproxy[28980]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:58 node-1 haproxy[28980]: 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>Sep 17 16:55:58 node-1 haproxy[28980]: 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>Sep 17 16:55:58 node-1 haproxy[28980]: proxy keystone-1 has no server available!
<129>Sep 17 16:55:58 node-1 haproxy[28980]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:59 node-1 haproxy[28987]: 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>Sep 17 16:55:59 node-1 haproxy[28987]: 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>Sep 17 16:55:59 node-1 haproxy[28987]: proxy keystone-2 has no server available!
<129>Sep 17 16:55:59 node-1 haproxy[28987]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:59 node-1 haproxy[28987]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:59 node-1 haproxy[28987]: 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>Sep 17 16:55:59 node-1 haproxy[28987]: proxy neutron has no server available!
<129>Sep 17 16:55:59 node-1 haproxy[28987]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:59 node-1 haproxy[28987]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:59 node-1 haproxy[28987]: 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>Sep 17 16:55:59 node-1 haproxy[28987]: proxy mysqld has no server available!
<129>Sep 17 16:55:59 node-1 haproxy[28987]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:59 node-1 haproxy[28987]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:55:59 node-1 haproxy[28987]: 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>Sep 17 16:55:59 node-1 haproxy[28987]: proxy object-storage has no server available!
<129>Sep 17 16:55:59 node-1 haproxy[28987]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:00 node-1 haproxy[28987]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:00 node-1 haproxy[28987]: 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>Sep 17 16:56:00 node-1 haproxy[28987]: proxy aodh has no server available!
<129>Sep 17 16:56:00 node-1 haproxy[28987]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:00 node-1 haproxy[28987]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:00 node-1 haproxy[28987]: 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>Sep 17 16:56:00 node-1 haproxy[28987]: proxy ceilometer has no server available!
<27>Sep 17 16:56:01 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:01 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:01 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:01 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:01 node-1 multipathd: uevent trigger error
<129>Sep 17 16:56:04 node-1 haproxy[30444]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:04 node-1 haproxy[30444]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:04 node-1 haproxy[30444]: 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>Sep 17 16:56:04 node-1 haproxy[30444]: 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>Sep 17 16:56:04 node-1 haproxy[30444]: proxy keystone-1 has no server available!
<129>Sep 17 16:56:04 node-1 haproxy[30444]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:04 node-1 haproxy[30444]: 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>Sep 17 16:56:04 node-1 haproxy[30444]: 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>Sep 17 16:56:04 node-1 haproxy[30444]: proxy keystone-2 has no server available!
<129>Sep 17 16:56:04 node-1 haproxy[30444]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:05 node-1 haproxy[30448]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:05 node-1 haproxy[30448]: 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>Sep 17 16:56:05 node-1 haproxy[30448]: proxy glance-api has no server available!
<129>Sep 17 16:56:05 node-1 haproxy[30448]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:05 node-1 haproxy[30448]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:05 node-1 haproxy[30448]: 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>Sep 17 16:56:05 node-1 haproxy[30448]: proxy glance-glare has no server available!
<129>Sep 17 16:56:05 node-1 haproxy[30448]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:05 node-1 haproxy[30448]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:05 node-1 haproxy[30448]: 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>Sep 17 16:56:05 node-1 haproxy[30448]: proxy neutron has no server available!
<129>Sep 17 16:56:05 node-1 haproxy[30448]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:05 node-1 haproxy[30448]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:05 node-1 haproxy[30448]: 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>Sep 17 16:56:05 node-1 haproxy[30448]: proxy glance-registry has no server available!
<129>Sep 17 16:56:05 node-1 haproxy[30448]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:05 node-1 haproxy[30448]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:05 node-1 haproxy[30448]: 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>Sep 17 16:56:05 node-1 haproxy[30448]: proxy mysqld has no server available!
<129>Sep 17 16:56:05 node-1 haproxy[30448]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:05 node-1 haproxy[30448]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:06 node-1 haproxy[30448]: 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>Sep 17 16:56:06 node-1 haproxy[30448]: proxy object-storage has no server available!
<129>Sep 17 16:56:06 node-1 haproxy[30448]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:06 node-1 haproxy[30448]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:06 node-1 haproxy[30448]: 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>Sep 17 16:56:06 node-1 haproxy[30448]: proxy aodh has no server available!
<129>Sep 17 16:56:06 node-1 haproxy[30448]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:06 node-1 haproxy[30448]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:06 node-1 haproxy[30448]: 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>Sep 17 16:56:06 node-1 haproxy[30448]: proxy ceilometer has no server available!
<27>Sep 17 16:56:07 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:07 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:07 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:07 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:07 node-1 multipathd: uevent trigger error
<129>Sep 17 16:56:10 node-1 haproxy[31898]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:10 node-1 haproxy[31898]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:10 node-1 haproxy[31898]: 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>Sep 17 16:56:10 node-1 haproxy[31898]: 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>Sep 17 16:56:10 node-1 haproxy[31898]: proxy keystone-1 has no server available!
<129>Sep 17 16:56:10 node-1 haproxy[31898]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:10 node-1 haproxy[31898]: 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>Sep 17 16:56:10 node-1 haproxy[31898]: 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>Sep 17 16:56:10 node-1 haproxy[31898]: proxy keystone-2 has no server available!
<129>Sep 17 16:56:10 node-1 haproxy[31898]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:10 node-1 haproxy[31898]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:10 node-1 haproxy[31898]: 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>Sep 17 16:56:10 node-1 haproxy[31898]: proxy nova-api has no server available!
<129>Sep 17 16:56:11 node-1 haproxy[31902]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:11 node-1 haproxy[31902]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:11 node-1 haproxy[31902]: 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>Sep 17 16:56:11 node-1 haproxy[31902]: proxy nova-metadata-api has no server available!
<129>Sep 17 16:56:11 node-1 haproxy[31902]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:11 node-1 haproxy[31902]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:11 node-1 haproxy[31902]: 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>Sep 17 16:56:11 node-1 haproxy[31902]: proxy glance-api has no server available!
<129>Sep 17 16:56:11 node-1 haproxy[31902]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:11 node-1 haproxy[31902]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:11 node-1 haproxy[31902]: 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>Sep 17 16:56:11 node-1 haproxy[31902]: proxy glance-glare has no server available!
<129>Sep 17 16:56:11 node-1 haproxy[31902]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:11 node-1 haproxy[31902]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:11 node-1 haproxy[31902]: 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>Sep 17 16:56:11 node-1 haproxy[31902]: proxy neutron has no server available!
<129>Sep 17 16:56:11 node-1 haproxy[31902]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:11 node-1 haproxy[31902]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:11 node-1 haproxy[31902]: 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>Sep 17 16:56:11 node-1 haproxy[31902]: proxy glance-registry has no server available!
<129>Sep 17 16:56:11 node-1 haproxy[31902]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:11 node-1 haproxy[31902]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:11 node-1 haproxy[31902]: 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>Sep 17 16:56:11 node-1 haproxy[31902]: proxy mysqld has no server available!
<129>Sep 17 16:56:11 node-1 haproxy[31902]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:11 node-1 haproxy[31902]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:11 node-1 haproxy[31902]: 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>Sep 17 16:56:11 node-1 haproxy[31902]: proxy object-storage has no server available!
<129>Sep 17 16:56:12 node-1 haproxy[31902]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:12 node-1 haproxy[31902]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:12 node-1 haproxy[31902]: 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>Sep 17 16:56:12 node-1 haproxy[31902]: proxy aodh has no server available!
<129>Sep 17 16:56:12 node-1 haproxy[31902]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:12 node-1 haproxy[31902]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:12 node-1 haproxy[31902]: 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>Sep 17 16:56:12 node-1 haproxy[31902]: proxy ceilometer has no server available!
<129>Sep 17 16:56:12 node-1 haproxy[31902]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:12 node-1 haproxy[31902]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:12 node-1 haproxy[31902]: 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>Sep 17 16:56:12 node-1 haproxy[31902]: proxy nova-novncproxy has no server available!
<27>Sep 17 16:56:13 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:13 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:13 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:13 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:13 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:13 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:13 node-1 multipathd: uevent trigger error
<129>Sep 17 16:56:16 node-1 haproxy[879]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:16 node-1 haproxy[879]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:16 node-1 haproxy[879]: 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>Sep 17 16:56:16 node-1 haproxy[879]: 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>Sep 17 16:56:16 node-1 haproxy[879]: proxy keystone-1 has no server available!
<129>Sep 17 16:56:16 node-1 haproxy[879]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:16 node-1 haproxy[879]: 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>Sep 17 16:56:16 node-1 haproxy[879]: 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>Sep 17 16:56:16 node-1 haproxy[879]: proxy keystone-2 has no server available!
<129>Sep 17 16:56:16 node-1 haproxy[879]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:16 node-1 haproxy[879]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:16 node-1 haproxy[879]: 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>Sep 17 16:56:16 node-1 haproxy[879]: proxy nova-api has no server available!
<129>Sep 17 16:56:16 node-1 haproxy[879]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:16 node-1 haproxy[879]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:16 node-1 haproxy[879]: 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>Sep 17 16:56:16 node-1 haproxy[879]: proxy nova-metadata-api has no server available!
<129>Sep 17 16:56:16 node-1 haproxy[879]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:16 node-1 haproxy[879]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:16 node-1 haproxy[879]: 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>Sep 17 16:56:16 node-1 haproxy[879]: proxy cinder-api has no server available!
<129>Sep 17 16:56:16 node-1 haproxy[879]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:16 node-1 haproxy[879]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:17 node-1 haproxy[885]: 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>Sep 17 16:56:17 node-1 haproxy[885]: proxy glance-api has no server available!
<129>Sep 17 16:56:17 node-1 haproxy[885]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:17 node-1 haproxy[885]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:17 node-1 haproxy[885]: 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>Sep 17 16:56:17 node-1 haproxy[885]: proxy glance-glare has no server available!
<129>Sep 17 16:56:17 node-1 haproxy[885]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:17 node-1 haproxy[885]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:17 node-1 haproxy[885]: 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>Sep 17 16:56:17 node-1 haproxy[885]: proxy neutron has no server available!
<129>Sep 17 16:56:17 node-1 haproxy[885]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:17 node-1 haproxy[885]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:17 node-1 haproxy[885]: 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>Sep 17 16:56:17 node-1 haproxy[885]: proxy glance-registry has no server available!
<129>Sep 17 16:56:17 node-1 haproxy[885]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:17 node-1 haproxy[885]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:17 node-1 haproxy[885]: 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>Sep 17 16:56:17 node-1 haproxy[885]: proxy mysqld has no server available!
<129>Sep 17 16:56:17 node-1 haproxy[885]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:17 node-1 haproxy[885]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:17 node-1 haproxy[885]: 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>Sep 17 16:56:17 node-1 haproxy[885]: proxy object-storage has no server available!
<129>Sep 17 16:56:17 node-1 haproxy[885]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:17 node-1 haproxy[885]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:17 node-1 haproxy[885]: 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>Sep 17 16:56:17 node-1 haproxy[885]: proxy aodh has no server available!
<129>Sep 17 16:56:17 node-1 haproxy[885]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:17 node-1 haproxy[885]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:17 node-1 haproxy[885]: 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>Sep 17 16:56:17 node-1 haproxy[885]: proxy ceilometer has no server available!
<129>Sep 17 16:56:18 node-1 haproxy[885]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:18 node-1 haproxy[885]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:18 node-1 haproxy[885]: 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>Sep 17 16:56:18 node-1 haproxy[885]: proxy nova-novncproxy has no server available!
<27>Sep 17 16:56:19 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:19 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:19 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:19 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:19 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:19 node-1 multipathd: uevent trigger error
<129>Sep 17 16:56:22 node-1 haproxy[2452]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:22 node-1 haproxy[2452]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:22 node-1 haproxy[2452]: 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>Sep 17 16:56:22 node-1 haproxy[2452]: 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>Sep 17 16:56:22 node-1 haproxy[2452]: proxy keystone-1 has no server available!
<129>Sep 17 16:56:22 node-1 haproxy[2452]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:22 node-1 haproxy[2452]: 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>Sep 17 16:56:22 node-1 haproxy[2452]: 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>Sep 17 16:56:22 node-1 haproxy[2452]: proxy keystone-2 has no server available!
<129>Sep 17 16:56:22 node-1 haproxy[2452]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:22 node-1 haproxy[2452]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:22 node-1 haproxy[2452]: 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>Sep 17 16:56:22 node-1 haproxy[2452]: proxy nova-api has no server available!
<129>Sep 17 16:56:22 node-1 haproxy[2452]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:22 node-1 haproxy[2452]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:22 node-1 haproxy[2452]: 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>Sep 17 16:56:22 node-1 haproxy[2452]: proxy nova-metadata-api has no server available!
<129>Sep 17 16:56:22 node-1 haproxy[2452]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:22 node-1 haproxy[2452]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:22 node-1 haproxy[2452]: 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>Sep 17 16:56:22 node-1 haproxy[2452]: proxy cinder-api has no server available!
<129>Sep 17 16:56:22 node-1 haproxy[2452]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:22 node-1 haproxy[2452]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:22 node-1 haproxy[2452]: 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>Sep 17 16:56:22 node-1 haproxy[2452]: proxy glance-api has no server available!
<129>Sep 17 16:56:22 node-1 haproxy[2452]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:22 node-1 haproxy[2452]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:22 node-1 haproxy[2452]: 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>Sep 17 16:56:22 node-1 haproxy[2452]: proxy glance-glare has no server available!
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: 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>Sep 17 16:56:23 node-1 haproxy[2462]: proxy neutron has no server available!
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: 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>Sep 17 16:56:23 node-1 haproxy[2462]: proxy glance-registry has no server available!
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: 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>Sep 17 16:56:23 node-1 haproxy[2462]: proxy mysqld has no server available!
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: 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>Sep 17 16:56:23 node-1 haproxy[2462]: proxy object-storage has no server available!
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: 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>Sep 17 16:56:23 node-1 haproxy[2462]: proxy aodh has no server available!
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: 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>Sep 17 16:56:23 node-1 haproxy[2462]: proxy ceilometer has no server available!
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server heat-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: 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>Sep 17 16:56:23 node-1 haproxy[2462]: proxy heat-api has no server available!
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: 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>Sep 17 16:56:23 node-1 haproxy[2462]: proxy heat-api-cfn has no server available!
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:23 node-1 haproxy[2462]: 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>Sep 17 16:56:23 node-1 haproxy[2462]: proxy heat-api-cloudwatch has no server available!
<129>Sep 17 16:56:24 node-1 haproxy[2462]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:24 node-1 haproxy[2462]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 17 16:56:24 node-1 haproxy[2462]: 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>Sep 17 16:56:24 node-1 haproxy[2462]: proxy nova-novncproxy has no server available!
<27>Sep 17 16:56:25 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:25 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:25 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:25 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:25 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:25 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:29 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:29 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:29 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:29 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:29 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:29 node-1 multipathd: uevent trigger error
<27>Sep 17 16:56:36 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 17 16:56:58 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 16:57:01 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Sep 17 16:57:03 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 17 16:57:34 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 17 16:58:00 node-1 multipathd: uevent trigger error
<27>Sep 17 16:58:00 node-1 multipathd: uevent trigger error
<27>Sep 17 16:58:00 node-1 multipathd: uevent trigger error
<27>Sep 17 16:58:00 node-1 multipathd: uevent trigger error
<27>Sep 17 16:58:00 node-1 multipathd: uevent trigger error
<27>Sep 17 16:58:00 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:01 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 17:00:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:17 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:17 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:17 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:17 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:17 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:17 node-1 multipathd: uevent trigger error
<43>Sep 17 17:00:34 node-1 apache2_error [Sat Sep 17 17:00:29.420745 2016] [mpm_event:notice] [pid 9521:tid 140062634956672] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 17 17:00:34 node-1 apache2_error [Sat Sep 17 17:00:29.420837 2016] [core:notice] [pid 9521:tid 140062634956672] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 17 17:00:34 node-1 apache2_error [Sat Sep 17 17:00:31.402365 2016] [mpm_event:notice] [pid 9521:tid 140062634956672] AH00491: caught SIGTERM, shutting down
<43>Sep 17 17:00:34 node-1 apache2_error [Sat Sep 17 17:00:32.486036 2016] [mpm_worker:notice] [pid 10736:tid 140661648770944] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 17 17:00:34 node-1 apache2_error [Sat Sep 17 17:00:32.486078 2016] [core:notice] [pid 10736:tid 140661648770944] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 17 17:00:37 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:37 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:37 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:37 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:37 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:37 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:42 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:42 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:42 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:42 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:42 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:45 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:45 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:45 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:45 node-1 multipathd: uevent trigger error
<27>Sep 17 17:00:45 node-1 multipathd: uevent trigger error
<43>Sep 17 17:02:04 node-1 apache2_error [Sat Sep 17 17:01:55.022691 2016] [mpm_worker:notice] [pid 10736:tid 140661648770944] AH00295: caught SIGTERM, shutting down
<43>Sep 17 17:02:04 node-1 apache2_error [Sat Sep 17 17:01:55.786111 2016] [mpm_worker:notice] [pid 25334:tid 140080962746240] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 17 17:02:04 node-1 apache2_error [Sat Sep 17 17:01:55.786147 2016] [core:notice] [pid 25334:tid 140080962746240] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 17 17:02:44 node-1 apache2_error [Sat Sep 17 17:02:41.901395 2016] [mpm_worker:notice] [pid 25334:tid 140080962746240] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 17 17:02:44 node-1 apache2_error [Sat Sep 17 17:02:42.097606 2016] [mpm_worker:warn] [pid 25334:tid 140080962746240] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 17 17:02:44 node-1 apache2_error [Sat Sep 17 17:02:42.101323 2016] [mpm_worker:notice] [pid 25334:tid 140080962746240] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 17 17:02:44 node-1 apache2_error [Sat Sep 17 17:02:42.101342 2016] [core:notice] [pid 25334:tid 140080962746240] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 17 17:03:14 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 17:03:26 node-1 multipathd: uevent trigger error
<27>Sep 17 17:03:26 node-1 multipathd: uevent trigger error
<27>Sep 17 17:03:26 node-1 multipathd: uevent trigger error
<27>Sep 17 17:03:26 node-1 multipathd: uevent trigger error
<27>Sep 17 17:03:26 node-1 multipathd: uevent trigger error
<27>Sep 17 17:03:31 node-1 multipathd: uevent trigger error
<27>Sep 17 17:03:31 node-1 multipathd: uevent trigger error
<27>Sep 17 17:03:31 node-1 multipathd: uevent trigger error
<27>Sep 17 17:03:31 node-1 multipathd: uevent trigger error
<27>Sep 17 17:03:31 node-1 multipathd: uevent trigger error
<27>Sep 17 17:03:46 node-1 multipathd: uevent trigger error
<27>Sep 17 17:03:46 node-1 multipathd: uevent trigger error
<27>Sep 17 17:03:46 node-1 multipathd: uevent trigger error
<27>Sep 17 17:03:46 node-1 multipathd: uevent trigger error
<27>Sep 17 17:04:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:04:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:04:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:04:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:04:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:04:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:04:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:04:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:04:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:04:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:04:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:05:02 node-1 multipathd: uevent trigger error
<27>Sep 17 17:05:02 node-1 multipathd: uevent trigger error
<27>Sep 17 17:05:02 node-1 multipathd: uevent trigger error
<27>Sep 17 17:05:02 node-1 multipathd: uevent trigger error
<27>Sep 17 17:05:02 node-1 multipathd: uevent trigger error
<27>Sep 17 17:05:20 node-1 multipathd: uevent trigger error
<27>Sep 17 17:05:20 node-1 multipathd: uevent trigger error
<27>Sep 17 17:05:20 node-1 multipathd: uevent trigger error
<27>Sep 17 17:05:20 node-1 multipathd: uevent trigger error
<27>Sep 17 17:05:20 node-1 multipathd: uevent trigger error
<27>Sep 17 17:05:20 node-1 multipathd: uevent trigger error
<27>Sep 17 17:05:20 node-1 multipathd: uevent trigger error
<27>Sep 17 17:06:16 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 17:06:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:06:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:06:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:06:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:06:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:06:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:06:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:07:29 node-1 multipathd: uevent trigger error
<27>Sep 17 17:07:29 node-1 multipathd: uevent trigger error
<27>Sep 17 17:07:29 node-1 multipathd: uevent trigger error
<27>Sep 17 17:07:29 node-1 multipathd: uevent trigger error
<27>Sep 17 17:07:29 node-1 multipathd: uevent trigger error
<27>Sep 17 17:07:29 node-1 multipathd: uevent trigger error
<27>Sep 17 17:08:30 node-1 multipathd: uevent trigger error
<27>Sep 17 17:08:30 node-1 multipathd: uevent trigger error
<27>Sep 17 17:08:30 node-1 multipathd: uevent trigger error
<27>Sep 17 17:08:30 node-1 multipathd: uevent trigger error
<27>Sep 17 17:08:30 node-1 multipathd: uevent trigger error
<27>Sep 17 17:08:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:08:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:08:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:08:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:08:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:08:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:08:58 node-1 multipathd: uevent trigger error
<27>Sep 17 17:08:58 node-1 multipathd: uevent trigger error
<27>Sep 17 17:08:58 node-1 multipathd: uevent trigger error
<27>Sep 17 17:08:58 node-1 multipathd: uevent trigger error
<27>Sep 17 17:08:58 node-1 multipathd: uevent trigger error
<27>Sep 17 17:09:17 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 17:11:30 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:30 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:30 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:30 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:30 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:46 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:46 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:46 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:46 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:46 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:46 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:46 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:11:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:12:19 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 17:12:34 node-1 multipathd: uevent trigger error
<27>Sep 17 17:12:34 node-1 multipathd: uevent trigger error
<27>Sep 17 17:12:34 node-1 multipathd: uevent trigger error
<27>Sep 17 17:12:34 node-1 multipathd: uevent trigger error
<27>Sep 17 17:12:34 node-1 multipathd: uevent trigger error
<27>Sep 17 17:12:34 node-1 multipathd: uevent trigger error
<27>Sep 17 17:12:34 node-1 multipathd: uevent trigger error
<27>Sep 17 17:12:40 node-1 multipathd: uevent trigger error
<27>Sep 17 17:12:40 node-1 multipathd: uevent trigger error
<27>Sep 17 17:12:40 node-1 multipathd: uevent trigger error
<27>Sep 17 17:12:40 node-1 multipathd: uevent trigger error
<27>Sep 17 17:12:40 node-1 multipathd: uevent trigger error
<27>Sep 17 17:13:01 node-1 multipathd: uevent trigger error
<27>Sep 17 17:13:01 node-1 multipathd: uevent trigger error
<27>Sep 17 17:13:01 node-1 multipathd: uevent trigger error
<27>Sep 17 17:13:01 node-1 multipathd: uevent trigger error
<27>Sep 17 17:13:01 node-1 multipathd: uevent trigger error
<27>Sep 17 17:13:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:13:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:13:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:13:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:13:52 node-1 multipathd: uevent trigger error
<27>Sep 17 17:13:59 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-prv" in table Interface
<27>Sep 17 17:13:59 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-prv" in table Port
<27>Sep 17 17:13:59 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-prv" in table Port
<27>Sep 17 17:14:00 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Sep 17 17:14:00 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Sep 17 17:14:00 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Sep 17 17:14:01 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:01 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:01 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:01 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:01 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:14 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:14 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:14 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:14 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:14 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:14 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:28 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:28 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:28 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:28 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:28 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:28 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:45 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:45 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:45 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:45 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:45 node-1 multipathd: uevent trigger error
<27>Sep 17 17:14:45 node-1 multipathd: uevent trigger error
<27>Sep 17 17:15:20 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 17:17:04 node-1 multipathd: uevent trigger error
<27>Sep 17 17:17:04 node-1 multipathd: uevent trigger error
<27>Sep 17 17:17:04 node-1 multipathd: uevent trigger error
<27>Sep 17 17:17:04 node-1 multipathd: uevent trigger error
<27>Sep 17 17:17:04 node-1 multipathd: uevent trigger error
<27>Sep 17 17:17:04 node-1 multipathd: uevent trigger error
<27>Sep 17 17:17:33 node-1 multipathd: uevent trigger error
<27>Sep 17 17:17:33 node-1 multipathd: uevent trigger error
<27>Sep 17 17:17:33 node-1 multipathd: uevent trigger error
<27>Sep 17 17:17:33 node-1 multipathd: uevent trigger error
<27>Sep 17 17:17:33 node-1 multipathd: uevent trigger error
<27>Sep 17 17:17:33 node-1 multipathd: uevent trigger error
<27>Sep 17 17:17:39 node-1 multipathd: uevent trigger error
<27>Sep 17 17:17:39 node-1 multipathd: uevent trigger error
<27>Sep 17 17:17:39 node-1 multipathd: uevent trigger error
<27>Sep 17 17:17:39 node-1 multipathd: uevent trigger error
<27>Sep 17 17:17:39 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:10 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:10 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:10 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:10 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:10 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:14 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:14 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:14 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:14 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:14 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:19 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:19 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:19 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:19 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:19 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:22 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 17:18:31 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:31 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:31 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:31 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:31 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:31 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:37 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:37 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:37 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:37 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:37 node-1 multipathd: uevent trigger error
<27>Sep 17 17:18:37 node-1 multipathd: uevent trigger error
<27>Sep 17 17:19:24 node-1 multipathd: uevent trigger error
<27>Sep 17 17:19:24 node-1 multipathd: uevent trigger error
<27>Sep 17 17:19:24 node-1 multipathd: uevent trigger error
<27>Sep 17 17:19:24 node-1 multipathd: uevent trigger error
<27>Sep 17 17:19:24 node-1 multipathd: uevent trigger error
<27>Sep 17 17:20:28 node-1 multipathd: uevent trigger error
<27>Sep 17 17:20:28 node-1 multipathd: uevent trigger error
<27>Sep 17 17:20:28 node-1 multipathd: uevent trigger error
<27>Sep 17 17:20:28 node-1 multipathd: uevent trigger error
<27>Sep 17 17:20:28 node-1 multipathd: uevent trigger error
<27>Sep 17 17:20:44 node-1 multipathd: uevent trigger error
<27>Sep 17 17:20:44 node-1 multipathd: uevent trigger error
<27>Sep 17 17:20:44 node-1 multipathd: uevent trigger error
<27>Sep 17 17:20:44 node-1 multipathd: uevent trigger error
<27>Sep 17 17:20:44 node-1 multipathd: uevent trigger error
<11>Sep 17 17:20:58 node-1 liberasurecode[25189]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:20:58 node-1 liberasurecode[25189]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:20:58 node-1 liberasurecode[25189]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:20:58 node-1 liberasurecode[25189]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 17:20:58 node-1 liberasurecode[25253]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:20:58 node-1 liberasurecode[25253]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:20:58 node-1 liberasurecode[25253]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:20:58 node-1 liberasurecode[25253]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 17:20:59 node-1 liberasurecode[26071]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:20:59 node-1 liberasurecode[26071]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:20:59 node-1 liberasurecode[26071]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:20:59 node-1 liberasurecode[26071]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26817]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26817]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26817]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26817]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26858]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26858]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26858]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26858]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26902]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26902]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26902]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26902]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26960]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26960]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26960]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26960]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26975]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26975]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26975]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[26975]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[27009]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[27009]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[27009]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:04 node-1 liberasurecode[27009]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:05 node-1 liberasurecode[27021]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:05 node-1 liberasurecode[27021]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:05 node-1 liberasurecode[27021]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:05 node-1 liberasurecode[27021]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:21 node-1 liberasurecode[27891]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:21 node-1 liberasurecode[27891]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:21 node-1 liberasurecode[27891]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:21:21 node-1 liberasurecode[27891]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 17 17:21:23 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 17:21:29 node-1 multipathd: uevent trigger error
<27>Sep 17 17:21:29 node-1 multipathd: uevent trigger error
<27>Sep 17 17:21:29 node-1 multipathd: uevent trigger error
<27>Sep 17 17:21:29 node-1 multipathd: uevent trigger error
<27>Sep 17 17:21:29 node-1 multipathd: uevent trigger error
<43>Sep 17 17:22:26 node-1 apache2_error [Sat Sep 17 17:22:16.222605 2016] [mpm_worker:notice] [pid 25334:tid 140080962746240] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 17 17:22:26 node-1 apache2_error [Sat Sep 17 17:22:16.602963 2016] [mpm_worker:warn] [pid 25334:tid 140080962746240] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 17 17:22:26 node-1 apache2_error [Sat Sep 17 17:22:16.606005 2016] [mpm_worker:notice] [pid 25334:tid 140080962746240] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 17 17:22:26 node-1 apache2_error [Sat Sep 17 17:22:16.606022 2016] [core:notice] [pid 25334:tid 140080962746240] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 17 17:22:56 node-1 apache2_error [Sat Sep 17 17:22:53.716313 2016] [mpm_worker:notice] [pid 25334:tid 140080962746240] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 17 17:22:56 node-1 apache2_error [Sat Sep 17 17:22:55.226558 2016] [mpm_worker:warn] [pid 25334:tid 140080962746240] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 17 17:22:56 node-1 apache2_error [Sat Sep 17 17:22:55.239714 2016] [mpm_worker:notice] [pid 25334:tid 140080962746240] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 17 17:22:56 node-1 apache2_error [Sat Sep 17 17:22:55.239751 2016] [core:notice] [pid 25334:tid 140080962746240] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 17 17:22:57 node-1 multipathd: uevent trigger error
<27>Sep 17 17:22:57 node-1 multipathd: uevent trigger error
<27>Sep 17 17:22:57 node-1 multipathd: uevent trigger error
<27>Sep 17 17:22:57 node-1 multipathd: uevent trigger error
<27>Sep 17 17:22:57 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:05 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:05 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:05 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:05 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:05 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:44 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:44 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:44 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:44 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:44 node-1 multipathd: uevent trigger error
<43>Sep 17 17:23:46 node-1 apache2_error [Sat Sep 17 17:23:39.910575 2016] [mpm_worker:notice] [pid 25334:tid 140080962746240] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 17 17:23:46 node-1 apache2_error [Sat Sep 17 17:23:40.105557 2016] [mpm_worker:warn] [pid 25334:tid 140080962746240] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 17 17:23:46 node-1 apache2_error [Sat Sep 17 17:23:40.115507 2016] [mpm_worker:notice] [pid 25334:tid 140080962746240] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 17 17:23:46 node-1 apache2_error [Sat Sep 17 17:23:40.115541 2016] [core:notice] [pid 25334:tid 140080962746240] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 17 17:23:51 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:51 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:51 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:51 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:51 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:56 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:56 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:56 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:57 node-1 multipathd: uevent trigger error
<27>Sep 17 17:23:57 node-1 multipathd: uevent trigger error
<27>Sep 17 17:24:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:24:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:24:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:24:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:24:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:24:25 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 17 17:24:38 node-1 multipathd: uevent trigger error
<27>Sep 17 17:24:45 node-1 multipathd: uevent trigger error
<27>Sep 17 17:24:45 node-1 multipathd: uevent trigger error
<27>Sep 17 17:24:45 node-1 multipathd: uevent trigger error
<27>Sep 17 17:24:45 node-1 multipathd: uevent trigger error
<27>Sep 17 17:24:45 node-1 multipathd: uevent trigger error
<27>Sep 17 17:24:52 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 17 17:25:01 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:01 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:01 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:01 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:01 node-1 multipathd: uevent trigger error
<11>Sep 17 17:25:01 node-1 liberasurecode[11870]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:25:01 node-1 liberasurecode[11870]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:25:01 node-1 liberasurecode[11870]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 17 17:25:01 node-1 liberasurecode[11870]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 17 17:25:06 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:06 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:06 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:06 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:06 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:11 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:16 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:27 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:27 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:27 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:27 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:27 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:28 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 17 17:25:55 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:55 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:55 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:55 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:55 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:59 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:59 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:59 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:59 node-1 multipathd: uevent trigger error
<27>Sep 17 17:25:59 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:13 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:13 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:13 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:13 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:13 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:13 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:20 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:20 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:20 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:20 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:20 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:24 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:24 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:24 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:24 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:25 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:38 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:38 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:38 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:38 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:38 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:43 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:43 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:43 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:43 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:43 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:47 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:47 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:47 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:47 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:47 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:53 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:53 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:53 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:53 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:53 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:53 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:57 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:57 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:57 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:57 node-1 multipathd: uevent trigger error
<27>Sep 17 17:26:58 node-1 multipathd: uevent trigger error
<27>Sep 17 17:27:02 node-1 multipathd: uevent trigger error
<27>Sep 17 17:27:02 node-1 multipathd: uevent trigger error
<27>Sep 17 17:27:02 node-1 multipathd: uevent trigger error
<27>Sep 17 17:27:02 node-1 multipathd: uevent trigger error
<27>Sep 17 17:27:02 node-1 multipathd: uevent trigger error
<27>Sep 17 17:27:07 node-1 multipathd: uevent trigger error
<27>Sep 17 17:27:07 node-1 multipathd: uevent trigger error
<27>Sep 17 17:27:07 node-1 multipathd: uevent trigger error
<27>Sep 17 17:27:07 node-1 multipathd: uevent trigger error
<27>Sep 17 17:27:07 node-1 multipathd: uevent trigger error
<27>Sep 17 17:27:07 node-1 multipathd: uevent trigger error
