Sep 20 19:07:02 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8416" x-info="http://www.rsyslog.com"] start
Sep 20 19:07:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 20 19:07:02 node-1 rsyslogd: rsyslogd's groupid changed to 104
Sep 20 19:07:02 node-1 rsyslogd: rsyslogd's userid changed to 101
Sep 20 19:07:02 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 20 19:07:02 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 20 19:07:02 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 20 19:07:02 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 20 19:07:02 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=5b5312c3-e37a-4814-a55d-5c924eca8d43 nomdmonddf nomdmonisw
Sep 20 19:07:02 node-1 kernel: [    0.000000] KERNEL supported cpus:
Sep 20 19:07:02 node-1 kernel: [    0.000000]   Intel GenuineIntel
Sep 20 19:07:02 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Sep 20 19:07:02 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Sep 20 19:07:02 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 20 19:07:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 20 19:07:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 20 19:07:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 20 19:07:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 20 19:07:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 20 19:07:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 20 19:07:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 20 19:07:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 20 19:07:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 20 19:07:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 20 19:07:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 20 19:07:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 20 19:07:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 20 19:07:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 20 19:07:02 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 20 19:07:02 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 20 19:07:02 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 20 19:07:02 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 20 19:07:02 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 20 19:07:02 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 20 19:07:02 node-1 kernel: [    0.000000] No AGP bridge found
Sep 20 19:07:02 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 20 19:07:02 node-1 kernel: [    0.000000] MTRR default type: write-back
Sep 20 19:07:02 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 20 19:07:02 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Sep 20 19:07:02 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 20 19:07:02 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 20 19:07:02 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 20 19:07:02 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 20 19:07:02 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 20 19:07:02 node-1 kernel: [    0.000000]   2 disabled
Sep 20 19:07:02 node-1 kernel: [    0.000000]   3 disabled
Sep 20 19:07:02 node-1 kernel: [    0.000000]   4 disabled
Sep 20 19:07:02 node-1 kernel: [    0.000000]   5 disabled
Sep 20 19:07:02 node-1 kernel: [    0.000000]   6 disabled
Sep 20 19:07:02 node-1 kernel: [    0.000000]   7 disabled
Sep 20 19:07:02 node-1 kernel: [    0.000000]   8 disabled
Sep 20 19:07:02 node-1 kernel: [    0.000000]   9 disabled
Sep 20 19:07:02 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 20 19:07:02 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 20 19:07:02 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 20 19:07:02 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 20 19:07:02 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 20 19:07:02 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Sep 20 19:07:02 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 20 19:07:02 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 20 19:07:02 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 20 19:07:02 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 20 19:07:02 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 20 19:07:02 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 20 19:07:02 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 20 19:07:02 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 20 19:07:02 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 20 19:07:02 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 20 19:07:02 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 20 19:07:02 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 20 19:07:02 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 20 19:07:02 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 20 19:07:02 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 20 19:07:02 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 20 19:07:02 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 20 19:07:02 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 20 19:07:02 node-1 kernel: [    0.000000] Zone ranges:
Sep 20 19:07:02 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] Movable zone start for each node
Sep 20 19:07:02 node-1 kernel: [    0.000000] Early memory node ranges
Sep 20 19:07:02 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 20 19:07:02 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 20 19:07:02 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 20 19:07:02 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 20 19:07:02 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 20 19:07:02 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 20 19:07:02 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 20 19:07:02 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 20 19:07:02 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 20 19:07:02 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 20 19:07:02 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 20 19:07:02 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 20 19:07:02 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 20 19:07:02 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 20 19:07:02 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 20 19:07:02 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 20 19:07:02 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 20 19:07:02 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 20 19:07:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 20 19:07:02 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 20 19:07:02 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 20 19:07:02 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 20 19:07:02 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 20 19:07:02 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 20 19:07:02 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 20 19:07:02 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 20 19:07:02 node-1 kernel: [    0.000000] Policy zone: Normal
Sep 20 19:07:02 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=5b5312c3-e37a-4814-a55d-5c924eca8d43 nomdmonddf nomdmonisw
Sep 20 19:07:02 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 20 19:07:02 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 20 19:07:02 node-1 kernel: [    0.000000] Checking aperture...
Sep 20 19:07:02 node-1 kernel: [    0.000000] No AGP bridge found
Sep 20 19:07:02 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 20 19:07:02 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 20 19:07:02 node-1 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Sep 20 19:07:02 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 20 19:07:02 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 20 19:07:02 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 20 19:07:02 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 20 19:07:02 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 20 19:07:02 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 20 19:07:02 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 20 19:07:02 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 20 19:07:02 node-1 kernel: [    0.000000] console [tty0] enabled
Sep 20 19:07:02 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 20 19:07:02 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 20 19:07:02 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 20 19:07:02 node-1 kernel: [    0.000000] hpet clockevent registered
Sep 20 19:07:02 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 20 19:07:02 node-1 kernel: [    0.004000] tsc: Detected 3491.910 MHz processor
Sep 20 19:07:02 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.82 BogoMIPS (lpj=13967640)
Sep 20 19:07:02 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 20 19:07:02 node-1 kernel: [    0.000045] Security Framework initialized
Sep 20 19:07:02 node-1 kernel: [    0.000063] AppArmor: AppArmor initialized
Sep 20 19:07:02 node-1 kernel: [    0.000065] Yama: becoming mindful.
Sep 20 19:07:02 node-1 kernel: [    0.001461] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 20 19:07:02 node-1 kernel: [    0.006390] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 20 19:07:02 node-1 kernel: [    0.008313] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 20 19:07:02 node-1 kernel: [    0.008342] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 20 19:07:02 node-1 kernel: [    0.008633] Initializing cgroup subsys memory
Sep 20 19:07:02 node-1 kernel: [    0.008642] Initializing cgroup subsys devices
Sep 20 19:07:02 node-1 kernel: [    0.008643] Initializing cgroup subsys freezer
Sep 20 19:07:02 node-1 kernel: [    0.008645] Initializing cgroup subsys blkio
Sep 20 19:07:02 node-1 kernel: [    0.008647] Initializing cgroup subsys perf_event
Sep 20 19:07:02 node-1 kernel: [    0.008649] Initializing cgroup subsys hugetlb
Sep 20 19:07:02 node-1 kernel: [    0.008669] CPU: Physical Processor ID: 0
Sep 20 19:07:02 node-1 kernel: [    0.008670] CPU: Processor Core ID: 0
Sep 20 19:07:02 node-1 kernel: [    0.008674] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 20 19:07:02 node-1 kernel: [    0.008674] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 20 19:07:02 node-1 kernel: [    0.009368] mce: CPU supports 22 MCE banks
Sep 20 19:07:02 node-1 kernel: [    0.009395] CPU0: Thermal monitoring enabled (TM1)
Sep 20 19:07:02 node-1 kernel: [    0.009416] process: using mwait in idle threads
Sep 20 19:07:02 node-1 kernel: [    0.009419] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 20 19:07:02 node-1 kernel: [    0.009419] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 20 19:07:02 node-1 kernel: [    0.009419] tlb_flushall_shift: 6
Sep 20 19:07:02 node-1 kernel: [    0.009508] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 20 19:07:02 node-1 kernel: [    0.010231] ACPI: Core revision 20131115
Sep 20 19:07:02 node-1 kernel: [    0.022898] ACPI: All ACPI Tables successfully acquired
Sep 20 19:07:02 node-1 kernel: [    0.023059] ftrace: allocating 28617 entries in 112 pages
Sep 20 19:07:02 node-1 kernel: [    0.032020] dmar: Host address width 46
Sep 20 19:07:02 node-1 kernel: [    0.032022] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 20 19:07:02 node-1 kernel: [    0.032028] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 20 19:07:02 node-1 kernel: [    0.032030] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 20 19:07:02 node-1 kernel: [    0.032034] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 20 19:07:02 node-1 kernel: [    0.032035] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 20 19:07:02 node-1 kernel: [    0.032036] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 20 19:07:02 node-1 kernel: [    0.032037] dmar: ATSR flags: 0x0
Sep 20 19:07:02 node-1 kernel: [    0.032038] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 20 19:07:02 node-1 kernel: [    0.032040] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 20 19:07:02 node-1 kernel: [    0.032155] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 20 19:07:02 node-1 kernel: [    0.032156] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 20 19:07:02 node-1 kernel: [    0.032157] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 20 19:07:02 node-1 kernel: [    0.032158] HPET id 0 under DRHD base 0xc7ffc000
Sep 20 19:07:02 node-1 kernel: [    0.032159] Your BIOS is broken and requested that x2apic be disabled.
Sep 20 19:07:02 node-1 kernel: [    0.032159] This will slightly decrease performance.
Sep 20 19:07:02 node-1 kernel: [    0.032159] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 20 19:07:02 node-1 kernel: [    0.032592] Enabled IRQ remapping in xapic mode
Sep 20 19:07:02 node-1 kernel: [    0.032593] x2apic not enabled, IRQ remapping is in xapic mode
Sep 20 19:07:02 node-1 kernel: [    0.032597] Switched APIC routing to physical flat.
Sep 20 19:07:02 node-1 kernel: [    0.033221] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 20 19:07:02 node-1 kernel: [    0.072871] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 20 19:07:02 node-1 kernel: [    0.072876] TSC deadline timer enabled
Sep 20 19:07:02 node-1 kernel: [    0.072883] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 20 19:07:02 node-1 kernel: [    0.072890] ... version:                3
Sep 20 19:07:02 node-1 kernel: [    0.072890] ... bit width:              48
Sep 20 19:07:02 node-1 kernel: [    0.072891] ... generic registers:      4
Sep 20 19:07:02 node-1 kernel: [    0.072892] ... value mask:             0000ffffffffffff
Sep 20 19:07:02 node-1 kernel: [    0.072893] ... max period:             0000ffffffffffff
Sep 20 19:07:02 node-1 kernel: [    0.072894] ... fixed-purpose events:   3
Sep 20 19:07:02 node-1 kernel: [    0.072895] ... event mask:             000000070000000f
Sep 20 19:07:02 node-1 kernel: [    0.074276] x86: Booting SMP configuration:
Sep 20 19:07:02 node-1 kernel: [    0.088380] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 20 19:07:02 node-1 kernel: [    0.074278] .... node  #0, CPUs:        #1  #2  #3
Sep 20 19:07:02 node-1 kernel: [    0.116285] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 20 19:07:02 node-1 kernel: [    0.270436] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 20 19:07:02 node-1 kernel: [    0.326049] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 20 19:07:02 node-1 kernel: [    0.382905] x86: Booted up 2 nodes, 16 CPUs
Sep 20 19:07:02 node-1 kernel: [    0.382909] smpboot: Total of 16 processors activated (111753.30 BogoMIPS)
Sep 20 19:07:02 node-1 kernel: [    0.406437] devtmpfs: initialized
Sep 20 19:07:02 node-1 kernel: [    0.409541] EVM: security.selinux
Sep 20 19:07:02 node-1 kernel: [    0.409543] EVM: security.SMACK64
Sep 20 19:07:02 node-1 kernel: [    0.409544] EVM: security.ima
Sep 20 19:07:02 node-1 kernel: [    0.409545] EVM: security.capability
Sep 20 19:07:02 node-1 kernel: [    0.409596] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 20 19:07:02 node-1 kernel: [    0.410275] pinctrl core: initialized pinctrl subsystem
Sep 20 19:07:02 node-1 kernel: [    0.410339] regulator-dummy: no parameters
Sep 20 19:07:02 node-1 kernel: [    0.410371] RTC time: 19:06:25, date: 09/20/16
Sep 20 19:07:02 node-1 kernel: [    0.410406] NET: Registered protocol family 16
Sep 20 19:07:02 node-1 kernel: [    0.410492] cpuidle: using governor ladder
Sep 20 19:07:02 node-1 kernel: [    0.410494] cpuidle: using governor menu
Sep 20 19:07:02 node-1 kernel: [    0.410528] ACPI: bus type PCI registered
Sep 20 19:07:02 node-1 kernel: [    0.410530] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 20 19:07:02 node-1 kernel: [    0.410575] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 20 19:07:02 node-1 kernel: [    0.410577] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 20 19:07:02 node-1 kernel: [    0.424304] PCI: Using configuration type 1 for base access
Sep 20 19:07:02 node-1 kernel: [    0.425306] bio: create slab <bio-0> at 0
Sep 20 19:07:02 node-1 kernel: [    0.425581] ACPI: Added _OSI(Module Device)
Sep 20 19:07:02 node-1 kernel: [    0.425583] ACPI: Added _OSI(Processor Device)
Sep 20 19:07:02 node-1 kernel: [    0.425584] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 20 19:07:02 node-1 kernel: [    0.425585] ACPI: Added _OSI(Processor Aggregator Device)
Sep 20 19:07:02 node-1 kernel: [    0.438203] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 20 19:07:02 node-1 kernel: [    0.449902] ACPI: Interpreter enabled
Sep 20 19:07:02 node-1 kernel: [    0.449908] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 20 19:07:02 node-1 kernel: [    0.449911] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 20 19:07:02 node-1 kernel: [    0.449914] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 20 19:07:02 node-1 kernel: [    0.449921] ACPI: (supports S0 S4 S5)
Sep 20 19:07:02 node-1 kernel: [    0.449922] ACPI: Using IOAPIC for interrupt routing
Sep 20 19:07:02 node-1 kernel: [    0.449962] HEST: Table parsing has been initialized.
Sep 20 19:07:02 node-1 kernel: [    0.449965] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 20 19:07:02 node-1 kernel: [    0.450518] ACPI: No dock devices found.
Sep 20 19:07:02 node-1 kernel: [    0.462237] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 20 19:07:02 node-1 kernel: [    0.462242] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 20 19:07:02 node-1 kernel: [    0.462245] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 20 19:07:02 node-1 kernel: [    0.462274] PCI host bridge to bus 0000:ff
Sep 20 19:07:02 node-1 kernel: [    0.462276] pci_bus 0000:ff: root bus resource [bus ff]
Sep 20 19:07:02 node-1 kernel: [    0.462284] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462323] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 20 19:07:02 node-1 kernel: [    0.462354] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462389] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462419] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 20 19:07:02 node-1 kernel: [    0.462450] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 20 19:07:02 node-1 kernel: [    0.462481] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462509] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462537] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462565] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462592] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462618] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462647] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462673] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462699] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462726] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462755] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462783] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462810] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 20 19:07:02 node-1 kernel: [    0.462838] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462864] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 20 19:07:02 node-1 kernel: [    0.462890] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462916] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.462946] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 20 19:07:02 node-1 kernel: [    0.462981] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463012] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463042] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463073] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463104] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463135] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463167] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463198] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463228] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463262] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463295] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463329] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463363] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 20 19:07:02 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 20 19:07:02 node-1 kernel: [    0.463393] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463421] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463453] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463486] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463525] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463561] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463594] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463625] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463657] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463687] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463718] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463752] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463784] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463816] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463847] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463877] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463907] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463936] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.463968] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464000] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464061] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 20 19:07:02 node-1 kernel: [    0.464064] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 20 19:07:02 node-1 kernel: [    0.464067] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 20 19:07:02 node-1 kernel: [    0.464084] PCI host bridge to bus 0000:7f
Sep 20 19:07:02 node-1 kernel: [    0.464086] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 20 19:07:02 node-1 kernel: [    0.464091] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464118] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 20 19:07:02 node-1 kernel: [    0.464146] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464175] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464197] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 20 19:07:02 node-1 kernel: [    0.464221] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 20 19:07:02 node-1 kernel: [    0.464247] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464273] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464295] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464318] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464340] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464362] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464386] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464408] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464432] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464457] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464479] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464502] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464526] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 20 19:07:02 node-1 kernel: [    0.464549] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464572] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 20 19:07:02 node-1 kernel: [    0.464596] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464621] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464648] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 20 19:07:02 node-1 kernel: [    0.464681] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464707] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464734] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464760] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464785] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464811] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464837] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464864] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464890] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464918] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464946] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.464974] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465002] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465027] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465051] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465079] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465105] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465131] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465161] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465189] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465214] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465239] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465264] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465291] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465318] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465344] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465374] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465399] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465422] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465447] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465473] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465502] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.465529] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.466770] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 20 19:07:02 node-1 kernel: [    0.466773] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 20 19:07:02 node-1 kernel: [    0.467892] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 20 19:07:02 node-1 kernel: [    0.468403] PCI host bridge to bus 0000:00
Sep 20 19:07:02 node-1 kernel: [    0.468406] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 20 19:07:02 node-1 kernel: [    0.468407] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 20 19:07:02 node-1 kernel: [    0.468409] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 20 19:07:02 node-1 kernel: [    0.468410] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 20 19:07:02 node-1 kernel: [    0.468411] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 20 19:07:02 node-1 kernel: [    0.468413] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 20 19:07:02 node-1 kernel: [    0.468414] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 20 19:07:02 node-1 kernel: [    0.468420] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 20 19:07:02 node-1 kernel: [    0.468502] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 20 19:07:02 node-1 kernel: [    0.468533] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 20 19:07:02 node-1 kernel: [    0.468575] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 20 19:07:02 node-1 kernel: [    0.468594] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 20 19:07:02 node-1 kernel: [    0.468623] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 20 19:07:02 node-1 kernel: [    0.468666] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 20 19:07:02 node-1 kernel: [    0.468684] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 20 19:07:02 node-1 kernel: [    0.468714] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 20 19:07:02 node-1 kernel: [    0.468754] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 20 19:07:02 node-1 kernel: [    0.468770] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.468840] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.468916] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.468991] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 20 19:07:02 node-1 kernel: [    0.468995] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 20 19:07:02 node-1 kernel: [    0.469080] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 20 19:07:02 node-1 kernel: [    0.469227] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 20 19:07:02 node-1 kernel: [    0.469245] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 20 19:07:02 node-1 kernel: [    0.469323] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 20 19:07:02 node-1 kernel: [    0.469377] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 20 19:07:02 node-1 kernel: [    0.469398] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 20 19:07:02 node-1 kernel: [    0.469454] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 20 19:07:02 node-1 kernel: [    0.469497] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 20 19:07:02 node-1 kernel: [    0.469524] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 20 19:07:02 node-1 kernel: [    0.469580] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 20 19:07:02 node-1 kernel: [    0.469622] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 20 19:07:02 node-1 kernel: [    0.469646] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 20 19:07:02 node-1 kernel: [    0.469664] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 20 19:07:02 node-1 kernel: [    0.469742] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 20 19:07:02 node-1 kernel: [    0.469792] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 20 19:07:02 node-1 kernel: [    0.469819] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 20 19:07:02 node-1 kernel: [    0.470067] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 20 19:07:02 node-1 kernel: [    0.470073] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 20 19:07:02 node-1 kernel: [    0.470079] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 20 19:07:02 node-1 kernel: [    0.470085] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 20 19:07:02 node-1 kernel: [    0.470092] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 20 19:07:02 node-1 kernel: [    0.470122] pci 0000:01:00.0: supports D1 D2
Sep 20 19:07:02 node-1 kernel: [    0.476026] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 20 19:07:02 node-1 kernel: [    0.476033] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 20 19:07:02 node-1 kernel: [    0.476037] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 20 19:07:02 node-1 kernel: [    0.476265] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 20 19:07:02 node-1 kernel: [    0.476298] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 20 19:07:02 node-1 kernel: [    0.484024] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 20 19:07:02 node-1 kernel: [    0.484030] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 20 19:07:02 node-1 kernel: [    0.484034] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 20 19:07:02 node-1 kernel: [    0.484126] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 20 19:07:02 node-1 kernel: [    0.484194] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 20 19:07:02 node-1 kernel: [    0.484273] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 20 19:07:02 node-1 kernel: [    0.484319] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 20 19:07:02 node-1 kernel: [    0.484322] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 20 19:07:02 node-1 kernel: [    0.484324] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 20 19:07:02 node-1 kernel: [    0.484377] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 20 19:07:02 node-1 kernel: [    0.484499] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 20 19:07:02 node-1 kernel: [    0.484553] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 20 19:07:02 node-1 kernel: [    0.484556] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 20 19:07:02 node-1 kernel: [    0.484558] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 20 19:07:02 node-1 kernel: [    0.484607] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 20 19:07:02 node-1 kernel: [    0.484726] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 20 19:07:02 node-1 kernel: [    0.484766] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 20 19:07:02 node-1 kernel: [    0.484885] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 20 19:07:02 node-1 kernel: [    0.484921] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 20 19:07:02 node-1 kernel: [    0.485061] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 20 19:07:02 node-1 kernel: [    0.485097] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 20 19:07:02 node-1 kernel: [    0.485218] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 20 19:07:02 node-1 kernel: [    0.485260] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 20 19:07:02 node-1 kernel: [    0.485262] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 20 19:07:02 node-1 kernel: [    0.485264] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 20 19:07:02 node-1 kernel: [    0.485324] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 20 19:07:02 node-1 kernel: [    0.485387] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 20 19:07:02 node-1 kernel: [    0.485439] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 20 19:07:02 node-1 kernel: [    0.485481] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 20 19:07:02 node-1 kernel: [    0.485562] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 20 19:07:02 node-1 kernel: [    0.485668] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 20 19:07:02 node-1 kernel: [    0.485671] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 20 19:07:02 node-1 kernel: [    0.485673] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 20 19:07:02 node-1 kernel: [    0.485729] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 20 19:07:02 node-1 kernel: [    0.485784] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 20 19:07:02 node-1 kernel: [    0.485833] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 20 19:07:02 node-1 kernel: [    0.486067] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 20 19:07:02 node-1 kernel: [    0.486071] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 20 19:07:02 node-1 kernel: [    0.486137] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 20 19:07:02 node-1 kernel: [    0.486193] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 20 19:07:02 node-1 kernel: [    0.486242] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 20 19:07:02 node-1 kernel: [    0.486455] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 20 19:07:02 node-1 kernel: [    0.486458] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 20 19:07:02 node-1 kernel: [    0.486517] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 20 19:07:02 node-1 kernel: [    0.486577] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 20 19:07:02 node-1 kernel: [    0.486629] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 20 19:07:02 node-1 kernel: [    0.486852] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 20 19:07:02 node-1 kernel: [    0.486855] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 20 19:07:02 node-1 kernel: [    0.487030] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 20 19:07:02 node-1 kernel: [    0.487068] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 20 19:07:02 node-1 kernel: [    0.487143] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 20 19:07:02 node-1 kernel: [    0.487162] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 20 19:07:02 node-1 kernel: [    0.487175] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 20 19:07:02 node-1 kernel: [    0.487188] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 20 19:07:02 node-1 kernel: [    0.487238] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 20 19:07:02 node-1 kernel: [    0.492028] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 20 19:07:02 node-1 kernel: [    0.492033] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 20 19:07:02 node-1 kernel: [    0.492065] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 20 19:07:02 node-1 kernel: [    0.492556] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 20 19:07:02 node-1 kernel: [    0.492559] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 20 19:07:02 node-1 kernel: [    0.492683] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 20 19:07:02 node-1 kernel: [    0.492788] PCI host bridge to bus 0000:80
Sep 20 19:07:02 node-1 kernel: [    0.492790] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 20 19:07:02 node-1 kernel: [    0.492792] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 20 19:07:02 node-1 kernel: [    0.492793] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 20 19:07:02 node-1 kernel: [    0.492801] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.492864] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.492931] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 20 19:07:02 node-1 kernel: [    0.492992] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 20 19:07:02 node-1 kernel: [    0.492998] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 20 19:07:02 node-1 kernel: [    0.493070] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 20 19:07:02 node-1 kernel: [    0.493371] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 20 19:07:02 node-1 kernel: [    0.493403] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 20 19:07:02 node-1 kernel: [    0.493433] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 20 19:07:02 node-1 kernel: [    0.493462] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 20 19:07:02 node-1 kernel: [    0.493492] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 20 19:07:02 node-1 kernel: [    0.493522] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 20 19:07:02 node-1 kernel: [    0.493552] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 20 19:07:02 node-1 kernel: [    0.493581] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 20 19:07:02 node-1 kernel: [    0.493666] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 20 19:07:02 node-1 kernel: [    0.493670] ACPI: \_SB_.UNC1: notify handler is installed
Sep 20 19:07:02 node-1 kernel: [    0.493671] ACPI: \_SB_.UNC0: notify handler is installed
Sep 20 19:07:02 node-1 kernel: [    0.493686] ACPI: \_SB_.PCI0: notify handler is installed
Sep 20 19:07:02 node-1 kernel: [    0.493739] ACPI: \_SB_.PCI1: notify handler is installed
Sep 20 19:07:02 node-1 kernel: [    0.493818] Found 4 acpi root devices
Sep 20 19:07:02 node-1 kernel: [    0.493933] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 20 19:07:02 node-1 kernel: [    0.493935] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 20 19:07:02 node-1 kernel: [    0.493937] vgaarb: loaded
Sep 20 19:07:02 node-1 kernel: [    0.493938] vgaarb: bridge control possible 0000:0c:00.0
Sep 20 19:07:02 node-1 kernel: [    0.494053] SCSI subsystem initialized
Sep 20 19:07:02 node-1 kernel: [    0.494117] libata version 3.00 loaded.
Sep 20 19:07:02 node-1 kernel: [    0.494131] ACPI: bus type USB registered
Sep 20 19:07:02 node-1 kernel: [    0.494141] usbcore: registered new interface driver usbfs
Sep 20 19:07:02 node-1 kernel: [    0.494146] usbcore: registered new interface driver hub
Sep 20 19:07:02 node-1 kernel: [    0.494168] usbcore: registered new device driver usb
Sep 20 19:07:02 node-1 kernel: [    0.494327] PCI: Using ACPI for IRQ routing
Sep 20 19:07:02 node-1 kernel: [    0.497923] PCI: pci_cache_line_size set to 64 bytes
Sep 20 19:07:02 node-1 kernel: [    0.498130] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 20 19:07:02 node-1 kernel: [    0.498131] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 20 19:07:02 node-1 kernel: [    0.498132] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 20 19:07:02 node-1 kernel: [    0.498196] NetLabel: Initializing
Sep 20 19:07:02 node-1 kernel: [    0.498197] NetLabel:  domain hash size = 128
Sep 20 19:07:02 node-1 kernel: [    0.498198] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 20 19:07:02 node-1 kernel: [    0.498207] NetLabel:  unlabeled traffic allowed by default
Sep 20 19:07:02 node-1 kernel: [    0.498262] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 20 19:07:02 node-1 kernel: [    0.498267] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 20 19:07:02 node-1 kernel: [    0.500335] Switched to clocksource hpet
Sep 20 19:07:02 node-1 kernel: [    0.504839] AppArmor: AppArmor Filesystem Enabled
Sep 20 19:07:02 node-1 kernel: [    0.504877] pnp: PnP ACPI init
Sep 20 19:07:02 node-1 kernel: [    0.504889] ACPI: bus type PNP registered
Sep 20 19:07:02 node-1 kernel: [    0.505071] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 20 19:07:02 node-1 kernel: [    0.505082] pnp 00:01: [dma 4]
Sep 20 19:07:02 node-1 kernel: [    0.505100] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 20 19:07:02 node-1 kernel: [    0.505135] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 20 19:07:02 node-1 kernel: [    0.505160] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 20 19:07:02 node-1 kernel: [    0.505182] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 20 19:07:02 node-1 kernel: [    0.505229] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 20 19:07:02 node-1 kernel: [    0.505341] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 20 19:07:02 node-1 kernel: [    0.505343] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 20 19:07:02 node-1 kernel: [    0.505345] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 20 19:07:02 node-1 kernel: [    0.505347] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 20 19:07:02 node-1 kernel: [    0.505348] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 20 19:07:02 node-1 kernel: [    0.505350] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 20 19:07:02 node-1 kernel: [    0.505353] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 20 19:07:02 node-1 kernel: [    0.505355] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 20 19:07:02 node-1 kernel: [    0.505356] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 20 19:07:02 node-1 kernel: [    0.505358] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 20 19:07:02 node-1 kernel: [    0.505359] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 20 19:07:02 node-1 kernel: [    0.505361] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 20 19:07:02 node-1 kernel: [    0.505362] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 20 19:07:02 node-1 kernel: [    0.505365] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 20 19:07:02 node-1 kernel: [    0.505467] pnp 00:07: [dma 0 disabled]
Sep 20 19:07:02 node-1 kernel: [    0.505499] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 20 19:07:02 node-1 kernel: [    0.505581] pnp 00:08: [dma 0 disabled]
Sep 20 19:07:02 node-1 kernel: [    0.505619] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 20 19:07:02 node-1 kernel: [    0.505679] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 20 19:07:02 node-1 kernel: [    0.506123] pnp: PnP ACPI: found 10 devices
Sep 20 19:07:02 node-1 kernel: [    0.506125] ACPI: bus type PNP unregistered
Sep 20 19:07:02 node-1 kernel: [    0.512161] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 20 19:07:02 node-1 kernel: [    0.512165] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 20 19:07:02 node-1 kernel: [    0.512167] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 20 19:07:02 node-1 kernel: [    0.512173] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 20 19:07:02 node-1 kernel: [    0.512175] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 20 19:07:02 node-1 kernel: [    0.512189] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 20 19:07:02 node-1 kernel: [    0.512219] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 20 19:07:02 node-1 kernel: [    0.512233] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 20 19:07:02 node-1 kernel: [    0.512262] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 20 19:07:02 node-1 kernel: [    0.512277] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 20 19:07:02 node-1 kernel: [    0.512306] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 20 19:07:02 node-1 kernel: [    0.512325] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 20 19:07:02 node-1 kernel: [    0.512354] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 20 19:07:02 node-1 kernel: [    0.512356] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 20 19:07:02 node-1 kernel: [    0.512371] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 20 19:07:02 node-1 kernel: [    0.512400] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 20 19:07:02 node-1 kernel: [    0.512402] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 20 19:07:02 node-1 kernel: [    0.512416] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 20 19:07:02 node-1 kernel: [    0.512449] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 20 19:07:02 node-1 kernel: [    0.512450] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 20 19:07:02 node-1 kernel: [    0.512453] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 20 19:07:02 node-1 kernel: [    0.512458] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 20 19:07:02 node-1 kernel: [    0.512460] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 20 19:07:02 node-1 kernel: [    0.512463] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 20 19:07:02 node-1 kernel: [    0.512467] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 20 19:07:02 node-1 kernel: [    0.512473] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 20 19:07:02 node-1 kernel: [    0.512482] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 20 19:07:02 node-1 kernel: [    0.512485] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 20 19:07:02 node-1 kernel: [    0.512493] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 20 19:07:02 node-1 kernel: [    0.512494] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 20 19:07:02 node-1 kernel: [    0.512494] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 20 19:07:02 node-1 kernel: [    0.512495] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 20 19:07:02 node-1 kernel: [    0.512496] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 20 19:07:02 node-1 kernel: [    0.512497] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 20 19:07:02 node-1 kernel: [    0.512498] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 20 19:07:02 node-1 kernel: [    0.512499] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 20 19:07:02 node-1 kernel: [    0.512500] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 20 19:07:02 node-1 kernel: [    0.512501] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 20 19:07:02 node-1 kernel: [    0.512502] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 20 19:07:02 node-1 kernel: [    0.512503] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 20 19:07:02 node-1 kernel: [    0.512504] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 20 19:07:02 node-1 kernel: [    0.512505] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 20 19:07:02 node-1 kernel: [    0.512506] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 20 19:07:02 node-1 kernel: [    0.512507] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 20 19:07:02 node-1 kernel: [    0.512508] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 20 19:07:02 node-1 kernel: [    0.512509] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 20 19:07:02 node-1 kernel: [    0.512510] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 20 19:07:02 node-1 kernel: [    0.512511] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 20 19:07:02 node-1 kernel: [    0.512512] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 20 19:07:02 node-1 kernel: [    0.512514] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 20 19:07:02 node-1 kernel: [    0.512516] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 20 19:07:02 node-1 kernel: [    0.512517] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 20 19:07:02 node-1 kernel: [    0.512557] NET: Registered protocol family 2
Sep 20 19:07:02 node-1 kernel: [    0.512852] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 20 19:07:02 node-1 kernel: [    0.513219] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 20 19:07:02 node-1 kernel: [    0.513386] TCP: Hash tables configured (established 262144 bind 65536)
Sep 20 19:07:02 node-1 kernel: [    0.513431] TCP: reno registered
Sep 20 19:07:02 node-1 kernel: [    0.513462] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 20 19:07:02 node-1 kernel: [    0.513568] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 20 19:07:02 node-1 kernel: [    0.513730] NET: Registered protocol family 1
Sep 20 19:07:02 node-1 kernel: [    0.552428] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 20 19:07:02 node-1 kernel: [    0.552443] PCI: CLS 64 bytes, default 64
Sep 20 19:07:02 node-1 kernel: [    0.552527] Trying to unpack rootfs image as initramfs...
Sep 20 19:07:02 node-1 kernel: [    0.774813] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Sep 20 19:07:02 node-1 kernel: [    0.774857] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 20 19:07:02 node-1 kernel: [    0.774859] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 20 19:07:02 node-1 kernel: [    0.775288] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 20 19:07:02 node-1 kernel: [    0.775302] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 20 19:07:02 node-1 kernel: [    0.775316] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 20 19:07:02 node-1 kernel: [    0.775329] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 20 19:07:02 node-1 kernel: [    0.775354] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 20 19:07:02 node-1 kernel: [    0.775361] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 20 19:07:02 node-1 kernel: [    0.775366] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 20 19:07:02 node-1 kernel: [    0.775372] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 20 19:07:02 node-1 kernel: [    0.775379] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 20 19:07:02 node-1 kernel: [    0.775386] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 20 19:07:02 node-1 kernel: [    0.775396] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 20 19:07:02 node-1 kernel: [    0.775403] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 20 19:07:02 node-1 kernel: [    0.775409] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 20 19:07:02 node-1 kernel: [    0.775416] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 20 19:07:02 node-1 kernel: [    0.775422] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 20 19:07:02 node-1 kernel: [    0.775428] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 20 19:07:02 node-1 kernel: [    0.775474] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 20 19:07:02 node-1 kernel: [    0.775477] Scanning for low memory corruption every 60 seconds
Sep 20 19:07:02 node-1 kernel: [    0.775789] Initialise system trusted keyring
Sep 20 19:07:02 node-1 kernel: [    0.775840] audit: initializing netlink socket (disabled)
Sep 20 19:07:02 node-1 kernel: [    0.775856] type=2000 audit(1474398385.728:1): initialized
Sep 20 19:07:02 node-1 kernel: [    0.793699] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 20 19:07:02 node-1 kernel: [    0.795174] zbud: loaded
Sep 20 19:07:02 node-1 kernel: [    0.795319] VFS: Disk quotas dquot_6.5.2
Sep 20 19:07:02 node-1 kernel: [    0.795359] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 20 19:07:02 node-1 kernel: [    0.795726] fuse init (API version 7.22)
Sep 20 19:07:02 node-1 kernel: [    0.795779] msgmni has been set to 32768
Sep 20 19:07:02 node-1 kernel: [    0.795825] Key type big_key registered
Sep 20 19:07:02 node-1 kernel: [    0.796358] Key type asymmetric registered
Sep 20 19:07:02 node-1 kernel: [    0.796366] Asymmetric key parser 'x509' registered
Sep 20 19:07:02 node-1 kernel: [    0.796390] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 20 19:07:02 node-1 kernel: [    0.796459] io scheduler noop registered
Sep 20 19:07:02 node-1 kernel: [    0.796461] io scheduler deadline registered (default)
Sep 20 19:07:02 node-1 kernel: [    0.796480] io scheduler cfq registered
Sep 20 19:07:02 node-1 kernel: [    0.796926] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    0.797053] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    0.797172] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    0.797290] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    0.797410] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    0.797503] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    0.797944] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 20 19:07:02 node-1 kernel: [    0.797983] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 20 19:07:02 node-1 kernel: [    0.798010] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 20 19:07:02 node-1 kernel: [    0.798032] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798037] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798043] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 20 19:07:02 node-1 kernel: [    0.798053] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798057] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798061] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798064] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798068] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798072] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798075] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798079] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798083] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798086] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798102] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798104] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798107] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 20 19:07:02 node-1 kernel: [    0.798118] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798120] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 20 19:07:02 node-1 kernel: [    0.798131] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798134] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 20 19:07:02 node-1 kernel: [    0.798144] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798146] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 20 19:07:02 node-1 kernel: [    0.798149] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 20 19:07:02 node-1 kernel: [    0.798175] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 20 19:07:02 node-1 kernel: [    0.798181] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 20 19:07:02 node-1 kernel: [    0.798185] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 20 19:07:02 node-1 kernel: [    0.798194] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 20 19:07:02 node-1 kernel: [    0.798229] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 20 19:07:02 node-1 kernel: [    0.798231] vesafb: scrolling: redraw
Sep 20 19:07:02 node-1 kernel: [    0.798233] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 20 19:07:02 node-1 kernel: [    0.818550] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 20 19:07:02 node-1 kernel: [    0.827043] Console: switching to colour frame buffer device 80x30
Sep 20 19:07:02 node-1 kernel: [    0.835715] fb0: VESA VGA frame buffer device
Sep 20 19:07:02 node-1 kernel: [    0.835915] intel_idle: MWAIT substates: 0x2120
Sep 20 19:07:02 node-1 kernel: [    0.835916] intel_idle: v0.4 model 0x3F
Sep 20 19:07:02 node-1 kernel: [    0.835917] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 20 19:07:02 node-1 kernel: [    0.836190] ipmi message handler version 39.2
Sep 20 19:07:02 node-1 kernel: [    0.836463] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 20 19:07:02 node-1 kernel: [    0.836895] ACPI: AC Adapter [P111] (on-line)
Sep 20 19:07:02 node-1 kernel: [    0.842142] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 20 19:07:02 node-1 kernel: [    0.853184] ACPI: Power Button [PWRB]
Sep 20 19:07:02 node-1 kernel: [    0.859000] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 20 19:07:02 node-1 kernel: [    0.870678] ACPI: Power Button [PWRF]
Sep 20 19:07:02 node-1 kernel: [    0.893903] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 20 19:07:02 node-1 kernel: [    0.905624] pstore: Registered erst as persistent store backend
Sep 20 19:07:02 node-1 kernel: [    0.911909] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 20 19:07:02 node-1 kernel: [    0.924011] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 20 19:07:02 node-1 kernel: [    0.950882] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 20 19:07:02 node-1 kernel: [    0.984341] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 20 19:07:02 node-1 kernel: [    0.998588] Linux agpgart interface v0.103
Sep 20 19:07:02 node-1 kernel: [    1.006384] brd: module loaded
Sep 20 19:07:02 node-1 kernel: [    1.013524] loop: module loaded
Sep 20 19:07:02 node-1 kernel: [    1.020298] libphy: Fixed MDIO Bus: probed
Sep 20 19:07:02 node-1 kernel: [    1.026849] tun: Universal TUN/TAP device driver, 1.6
Sep 20 19:07:02 node-1 kernel: [    1.033474] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 20 19:07:02 node-1 kernel: [    1.040013] PPP generic driver version 2.4.2
Sep 20 19:07:02 node-1 kernel: [    1.046431] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 20 19:07:02 node-1 kernel: [    1.052952] ehci-pci: EHCI PCI platform driver
Sep 20 19:07:02 node-1 kernel: [    1.059572] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 20 19:07:02 node-1 kernel: [    1.065985] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 20 19:07:02 node-1 kernel: [    1.078513] ehci-pci 0000:00:1a.0: debug port 2
Sep 20 19:07:02 node-1 kernel: [    1.088705] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 20 19:07:02 node-1 kernel: [    1.088723] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 20 19:07:02 node-1 kernel: [    1.103815] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 20 19:07:02 node-1 kernel: [    1.109882] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 20 19:07:02 node-1 kernel: [    1.116049] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 20 19:07:02 node-1 kernel: [    1.127943] usb usb1: Product: EHCI Host Controller
Sep 20 19:07:02 node-1 kernel: [    1.133955] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 20 19:07:02 node-1 kernel: [    1.139986] usb usb1: SerialNumber: 0000:00:1a.0
Sep 20 19:07:02 node-1 kernel: [    1.145926] hub 1-0:1.0: USB hub found
Sep 20 19:07:02 node-1 kernel: [    1.151690] hub 1-0:1.0: 2 ports detected
Sep 20 19:07:02 node-1 kernel: [    1.157463] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 20 19:07:02 node-1 kernel: [    1.163036] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 20 19:07:02 node-1 kernel: [    1.173911] ehci-pci 0000:00:1d.0: debug port 2
Sep 20 19:07:02 node-1 kernel: [    1.183196] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 20 19:07:02 node-1 kernel: [    1.183202] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 20 19:07:02 node-1 kernel: [    1.199733] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 20 19:07:02 node-1 kernel: [    1.204930] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 20 19:07:02 node-1 kernel: [    1.210305] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 20 19:07:02 node-1 kernel: [    1.220940] usb usb2: Product: EHCI Host Controller
Sep 20 19:07:02 node-1 kernel: [    1.226419] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 20 19:07:02 node-1 kernel: [    1.231980] usb usb2: SerialNumber: 0000:00:1d.0
Sep 20 19:07:02 node-1 kernel: [    1.237515] hub 2-0:1.0: USB hub found
Sep 20 19:07:02 node-1 kernel: [    1.242877] hub 2-0:1.0: 2 ports detected
Sep 20 19:07:02 node-1 kernel: [    1.248184] ehci-platform: EHCI generic platform driver
Sep 20 19:07:02 node-1 kernel: [    1.253431] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 20 19:07:02 node-1 kernel: [    1.258759] ohci-pci: OHCI PCI platform driver
Sep 20 19:07:02 node-1 kernel: [    1.264075] ohci-platform: OHCI generic platform driver
Sep 20 19:07:02 node-1 kernel: [    1.269293] uhci_hcd: USB Universal Host Controller Interface driver
Sep 20 19:07:02 node-1 kernel: [    1.274663] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 20 19:07:02 node-1 kernel: [    1.467512] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 20 19:07:02 node-1 kernel: [    1.631747] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 20 19:07:02 node-1 kernel: [    1.637269] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 20 19:07:02 node-1 kernel: [    1.643014] hub 1-1:1.0: USB hub found
Sep 20 19:07:02 node-1 kernel: [    1.648482] hub 1-1:1.0: 6 ports detected
Sep 20 19:07:02 node-1 kernel: [    1.767247] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 20 19:07:02 node-1 kernel: [    2.031407] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 20 19:07:02 node-1 kernel: [    2.036839] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 20 19:07:02 node-1 kernel: [    2.042551] hub 2-1:1.0: USB hub found
Sep 20 19:07:02 node-1 kernel: [    2.048143] hub 2-1:1.0: 8 ports detected
Sep 20 19:07:02 node-1 kernel: [    2.315343] i8042: No controller found
Sep 20 19:07:02 node-1 kernel: [    2.320730] tsc: Refined TSC clocksource calibration: 3491.912 MHz
Sep 20 19:07:02 node-1 kernel: [    2.322083] mousedev: PS/2 mouse device common for all mice
Sep 20 19:07:02 node-1 kernel: [    2.322876] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 20 19:07:02 node-1 kernel: [    2.324153] rtc_cmos 00:02: RTC can wake from S4
Sep 20 19:07:02 node-1 kernel: [    2.325824] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 20 19:07:02 node-1 kernel: [    2.326312] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 20 19:07:02 node-1 kernel: [    2.327345] device-mapper: uevent: version 1.0.3
Sep 20 19:07:02 node-1 kernel: [    2.328439] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 20 19:07:02 node-1 kernel: [    2.328614] ledtrig-cpu: registered to indicate activity on CPUs
Sep 20 19:07:02 node-1 kernel: [    2.330478] TCP: cubic registered
Sep 20 19:07:02 node-1 kernel: [    2.331733] NET: Registered protocol family 10
Sep 20 19:07:02 node-1 kernel: [    2.334317] NET: Registered protocol family 17
Sep 20 19:07:02 node-1 kernel: [    2.334523] Key type dns_resolver registered
Sep 20 19:07:02 node-1 kernel: [    2.341118] Loading compiled-in X.509 certificates
Sep 20 19:07:02 node-1 kernel: [    2.343231] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 20 19:07:02 node-1 kernel: [    2.343501] registered taskstats version 1
Sep 20 19:07:02 node-1 kernel: [    2.383704] Key type trusted registered
Sep 20 19:07:02 node-1 kernel: [    2.409577] Key type encrypted registered
Sep 20 19:07:02 node-1 kernel: [    2.409626] AppArmor: AppArmor sha1 policy hashing enabled
Sep 20 19:07:02 node-1 kernel: [    2.409658] IMA: No TPM chip found, activating TPM-bypass!
Sep 20 19:07:02 node-1 kernel: [    2.418877] regulator-dummy: disabling
Sep 20 19:07:02 node-1 kernel: [    2.419778]   Magic number: 0:602:142
Sep 20 19:07:02 node-1 kernel: [    2.419901] block ram7: hash matches
Sep 20 19:07:02 node-1 kernel: [    2.421680] acpi device:13: hash matches
Sep 20 19:07:02 node-1 kernel: [    2.456542] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 20 19:07:02 node-1 kernel: [    2.456542] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 20 19:07:02 node-1 kernel: [    2.456544] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 20 19:07:02 node-1 kernel: [    2.456544] usb 2-1.4: Manufacturer: Avocent
Sep 20 19:07:02 node-1 kernel: [    2.456545] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 20 19:07:02 node-1 kernel: [    2.503778] rtc_cmos 00:02: setting system clock to 2016-09-20 19:06:27 UTC (1474398387)
Sep 20 19:07:02 node-1 kernel: [    2.516016] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 20 19:07:02 node-1 kernel: [    2.521504] EDD information not available.
Sep 20 19:07:02 node-1 kernel: [    2.526980] PM: Hibernation image not present or could not be loaded.
Sep 20 19:07:02 node-1 kernel: [    2.527840] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 20 19:07:02 node-1 kernel: [    2.538781] Write protecting the kernel read-only data: 12288k
Sep 20 19:07:02 node-1 kernel: [    2.544782] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 20 19:07:02 node-1 kernel: [    2.556990] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 20 19:07:02 node-1 kernel: [    2.589893] device-mapper: multipath: version 1.6.0 loaded
Sep 20 19:07:02 node-1 kernel: [    2.597942] systemd-udevd[216]: starting version 204
Sep 20 19:07:02 node-1 kernel: [    2.618226] md: linear personality registered for level -1
Sep 20 19:07:02 node-1 kernel: [    2.632836] md: multipath personality registered for level -4
Sep 20 19:07:02 node-1 kernel: [    2.640899] md: raid0 personality registered for level 0
Sep 20 19:07:02 node-1 kernel: [    2.649334] md: raid1 personality registered for level 1
Sep 20 19:07:02 node-1 kernel: [    2.655547] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 20 19:07:02 node-1 kernel: [    2.661834] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 20 19:07:02 node-1 kernel: [    2.670350] hidraw: raw HID events driver (C) Jiri Kosina
Sep 20 19:07:02 node-1 kernel: [    2.670692] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Sep 20 19:07:02 node-1 kernel: [    2.670693] 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 20 19:07:02 node-1 kernel: [    2.670695] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 20 19:07:02 node-1 kernel: [    2.670765] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.670803] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.670843] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.670886] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.670967] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.672190] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 20 19:07:02 node-1 kernel: [    2.672727] megasas: FW now in Ready state
Sep 20 19:07:02 node-1 kernel: [    2.672795] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.672832] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.672867] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.672905] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.672945] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.672984] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.673019] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.673055] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.673091] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.673122] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.673158] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.673196] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.673234] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.673271] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.673307] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.673344] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.673497] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 20 19:07:02 node-1 kernel: [    2.682378] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Sep 20 19:07:02 node-1 kernel: [    2.682379] 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 20 19:07:02 node-1 kernel: [    2.682380] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 20 19:07:02 node-1 kernel: [    2.682498] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.682528] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.682567] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.682603] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.682640] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.682679] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.682757] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.695464] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Sep 20 19:07:02 node-1 kernel: [    2.695465] 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 20 19:07:02 node-1 kernel: [    2.695466] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 20 19:07:02 node-1 kernel: [    2.695582] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.695620] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.695656] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.695690] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.695762] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.705431] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Sep 20 19:07:02 node-1 kernel: [    2.705432] 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 20 19:07:02 node-1 kernel: [    2.705433] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 20 19:07:02 node-1 kernel: [    2.705493] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.705526] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.705539] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.705574] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.705666] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 20 19:07:02 node-1 kernel: [    2.734523] raid6: sse2x1     604 MB/s
Sep 20 19:07:02 node-1 kernel: [    2.802471] raid6: sse2x2     794 MB/s
Sep 20 19:07:02 node-1 kernel: [    2.870427] raid6: sse2x4    1209 MB/s
Sep 20 19:07:02 node-1 kernel: [    2.916453] usbcore: registered new interface driver usbhid
Sep 20 19:07:02 node-1 kernel: [    2.922996] usbhid: USB HID core driver
Sep 20 19:07:02 node-1 kernel: [    2.930885] 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 20 19:07:02 node-1 kernel: [    2.938307] raid6: avx2x1    8204 MB/s
Sep 20 19:07:02 node-1 kernel: [    2.950538] 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 20 19:07:02 node-1 kernel: [    2.963632] 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 20 19:07:02 node-1 kernel: [    2.976691] 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 20 19:07:02 node-1 kernel: [    2.990068] 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 20 19:07:02 node-1 kernel: [    3.003717] 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 20 19:07:02 node-1 kernel: [    3.006270] raid6: avx2x2   25271 MB/s
Sep 20 19:07:02 node-1 kernel: [    3.030177] megasas:IOC Init cmd success
Sep 20 19:07:02 node-1 kernel: [    3.058159] megasas: INIT adapter done
Sep 20 19:07:02 node-1 kernel: [    3.074154] raid6: avx2x4   30492 MB/s
Sep 20 19:07:02 node-1 kernel: [    3.080659] raid6: using algorithm avx2x4 (30492 MB/s)
Sep 20 19:07:02 node-1 kernel: [    3.087102] raid6: using avx2x2 recovery algorithm
Sep 20 19:07:02 node-1 kernel: [    3.094265] xor: automatically using best checksumming function:
Sep 20 19:07:02 node-1 kernel: [    3.138081]    avx       : 35701.000 MB/sec
Sep 20 19:07:02 node-1 kernel: [    3.144963] async_tx: api initialized (async)
Sep 20 19:07:02 node-1 kernel: [    3.155230] md: raid6 personality registered for level 6
Sep 20 19:07:02 node-1 kernel: [    3.161421] md: raid5 personality registered for level 5
Sep 20 19:07:02 node-1 kernel: [    3.162110] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 20 19:07:02 node-1 kernel: [    3.162486] scsi0 : LSI SAS based MegaRAID driver
Sep 20 19:07:02 node-1 kernel: [    3.169783] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 20 19:07:02 node-1 kernel: [    3.184810] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 20 19:07:02 node-1 kernel: [    3.189948] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 20 19:07:02 node-1 kernel: [    3.190162] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 20 19:07:02 node-1 kernel: [    3.190808] sd 0:2:0:0: [sda] Write Protect is off
Sep 20 19:07:02 node-1 kernel: [    3.190809] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 20 19:07:02 node-1 kernel: [    3.190909] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 20 19:07:02 node-1 kernel: [    3.222488]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Sep 20 19:07:02 node-1 kernel: [    3.225235] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 20 19:07:02 node-1 kernel: [    3.253861] md: raid4 personality registered for level 4
Sep 20 19:07:02 node-1 kernel: [    3.263403] md: raid10 personality registered for level 10
Sep 20 19:07:02 node-1 kernel: [    3.312605] multipathd (359): /proc/359/oom_adj is deprecated, please use /proc/359/oom_score_adj instead.
Sep 20 19:07:02 node-1 kernel: [    3.387393] random: lvm urandom read with 28 bits of entropy available
Sep 20 19:07:02 node-1 kernel: [    3.496597] bio: create slab <bio-1> at 1
Sep 20 19:07:02 node-1 kernel: [    3.502898] Switched to clocksource tsc
Sep 20 19:07:02 node-1 kernel: [    4.276477] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Sep 20 19:07:02 node-1 kernel: [    5.062848] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Sep 20 19:07:02 node-1 kernel: [    5.131679] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 20 19:07:02 node-1 kernel: [    5.238612] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 20 19:07:02 node-1 kernel: [    5.262156] random: nonblocking pool is initialized
Sep 20 19:07:02 node-1 kernel: [    5.286524] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 20 19:07:02 node-1 kernel: [    5.362098] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 20 19:07:02 node-1 kernel: [    5.521095] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 20 19:07:02 node-1 kernel: [    5.571130] XFS (dm-1): Mounting Filesystem
Sep 20 19:07:02 node-1 kernel: [    5.738794] XFS (dm-1): Ending clean mount
Sep 20 19:07:02 node-1 kernel: [    5.799337] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 20 19:07:02 node-1 kernel: [    5.826817] XFS (dm-2): Mounting Filesystem
Sep 20 19:07:02 node-1 kernel: [    5.987949] XFS (dm-2): Ending clean mount
Sep 20 19:07:02 node-1 kernel: [    6.131832] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Sep 20 19:07:02 node-1 kernel: [    8.104682] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 20 19:07:02 node-1 kernel: [    8.127930] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 20 19:07:02 node-1 kernel: [    8.258261] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 20 19:07:02 node-1 kernel: [    8.258266] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 20 19:07:02 node-1 kernel: [    8.258270] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 20 19:07:02 node-1 kernel: [    8.258273] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 20 19:07:02 node-1 kernel: [    8.319359] systemd-udevd[798]: starting version 204
Sep 20 19:07:02 node-1 kernel: [    8.579135] IPMI System Interface driver.
Sep 20 19:07:02 node-1 kernel: [    8.579239] ipmi_si: probing via ACPI
Sep 20 19:07:02 node-1 kernel: [    8.579257] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 20 19:07:02 node-1 kernel: [    8.579258] ipmi_si: Adding ACPI-specified kcs state machine
Sep 20 19:07:02 node-1 kernel: [    8.579273] ipmi_si: probing via SMBIOS
Sep 20 19:07:02 node-1 kernel: [    8.579274] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 20 19:07:02 node-1 kernel: [    8.579274] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 20 19:07:02 node-1 kernel: [    8.579276] ipmi_si: probing via SPMI
Sep 20 19:07:02 node-1 kernel: [    8.579277] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 20 19:07:02 node-1 kernel: [    8.579277] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 20 19:07:02 node-1 kernel: [    8.579279] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 20 19:07:02 node-1 kernel: [    8.586004] power_meter ACPI000D:00: Found ACPI power meter.
Sep 20 19:07:02 node-1 kernel: [    8.586026] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 20 19:07:02 node-1 kernel: [    8.606861] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 20 19:07:02 node-1 kernel: [    8.606865] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 20 19:07:02 node-1 kernel: [    8.606868] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 20 19:07:02 node-1 kernel: [    8.606870] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 20 19:07:02 node-1 kernel: [    8.606885] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 20 19:07:02 node-1 kernel: [    8.633938] wmi: Mapper loaded
Sep 20 19:07:02 node-1 kernel: [    8.641521] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 20 19:07:02 node-1 kernel: [    8.725729] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 20 19:07:02 node-1 kernel: [    8.725735] ipmi_si 00:09: IPMI kcs interface initialized
Sep 20 19:07:02 node-1 kernel: [    8.726706] systemd-udevd[817]: renamed network interface eth0 to enp6s0
Sep 20 19:07:02 node-1 kernel: [    8.749760] systemd-udevd[826]: renamed network interface eth2 to enp8s0
Sep 20 19:07:02 node-1 kernel: [    8.785713] systemd-udevd[821]: renamed network interface eth1 to enp7s0
Sep 20 19:07:02 node-1 kernel: [    8.805751] systemd-udevd[827]: renamed network interface eth3 to enp9s0
Sep 20 19:07:02 node-1 kernel: [    9.125219] type=1400 audit(1474398394.206:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1075 comm="apparmor_parser"
Sep 20 19:07:02 node-1 kernel: [    9.125425] type=1400 audit(1474398394.206:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1075 comm="apparmor_parser"
Sep 20 19:07:02 node-1 kernel: [    9.125453] type=1400 audit(1474398394.206:4): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1080 comm="apparmor_parser"
Sep 20 19:07:02 node-1 kernel: [    9.125570] type=1400 audit(1474398394.206:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1075 comm="apparmor_parser"
Sep 20 19:07:02 node-1 kernel: [    9.125607] type=1400 audit(1474398394.206:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1080 comm="apparmor_parser"
Sep 20 19:07:02 node-1 kernel: [    9.125726] type=1400 audit(1474398394.206:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1080 comm="apparmor_parser"
Sep 20 19:07:02 node-1 kernel: [    9.153261] type=1400 audit(1474398394.234:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1074 comm="apparmor_parser"
Sep 20 19:07:02 node-1 kernel: [    9.153402] type=1400 audit(1474398394.234:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1074 comm="apparmor_parser"
Sep 20 19:07:02 node-1 kernel: [    9.153525] type=1400 audit(1474398394.234:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1074 comm="apparmor_parser"
Sep 20 19:07:02 node-1 kernel: [    9.154644] type=1400 audit(1474398394.234:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1077 comm="apparmor_parser"
Sep 20 19:07:02 node-1 kernel: [    9.722590] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 20 19:07:02 node-1 kernel: [    9.723387] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 20 19:07:02 node-1 kernel: [    9.937002] enic 0000:06:00.0 enp6s0: Link UP
Sep 20 19:07:02 node-1 kernel: [    9.937428] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 20 19:07:02 node-1 kernel: [    9.937434] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 20 19:07:02 node-1 kernel: [   19.801244] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 20 19:07:03 node-1 failsafe: Failsafe of 120 seconds reached.
Sep 20 19:07:03 node-1 kernel: [   38.552895] init: failsafe main process (8443) killed by TERM signal
Sep 20 19:07:03 node-1 dbus[8472]: [system] AppArmor D-Bus mediation is enabled
Sep 20 19:07:04 node-1 kernel: [   38.811072] audit_printk_skb: 30 callbacks suppressed
Sep 20 19:07:04 node-1 kernel: [   38.811074] type=1400 audit(1474398424.132:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8569 comm="apparmor_parser"
Sep 20 19:07:04 node-1 kernel: [   38.811381] type=1400 audit(1474398424.132:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8568 comm="apparmor_parser"
Sep 20 19:07:04 node-1 kernel: [   38.811387] type=1400 audit(1474398424.132:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8568 comm="apparmor_parser"
Sep 20 19:07:04 node-1 kernel: [   38.811390] type=1400 audit(1474398424.132:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8568 comm="apparmor_parser"
Sep 20 19:07:04 node-1 kernel: [   38.811622] type=1400 audit(1474398424.132:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8568 comm="apparmor_parser"
Sep 20 19:07:04 node-1 kernel: [   38.811624] type=1400 audit(1474398424.132:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8568 comm="apparmor_parser"
Sep 20 19:07:04 node-1 kernel: [   38.811737] type=1400 audit(1474398424.132:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8568 comm="apparmor_parser"
Sep 20 19:07:04 node-1 kernel: [   38.892585] type=1400 audit(1474398424.216:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8571 comm="apparmor_parser"
Sep 20 19:07:04 node-1 cron[8601]: (CRON) INFO (pidfile fd = 3)
Sep 20 19:07:04 node-1 anacron[8636]: Anacron 2.3 started on 2016-09-20
Sep 20 19:07:04 node-1 cron[8639]: (CRON) STARTUP (fork ok)
Sep 20 19:07:04 node-1 cron[8639]: (CRON) INFO (Running @reboot jobs)
Sep 20 19:07:04 node-1 anacron[8636]: Will run job `cron.daily' in 5 min.
Sep 20 19:07:04 node-1 anacron[8636]: Will run job `cron.weekly' in 10 min.
Sep 20 19:07:04 node-1 anacron[8636]: Will run job `cron.monthly' in 15 min.
Sep 20 19:07:04 node-1 anacron[8636]: Jobs will be executed sequentially
Sep 20 19:07:04 node-1 multipathd: path checkers start up
Sep 20 19:07:04 node-1 postfix/master[8780]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 20 19:07:08 node-1 puppet-agent[8964]: Reopening log files
Sep 20 19:07:09 node-1 puppet-agent[8964]: Could not request certificate: Connection refused - connect(2)
Sep 20 19:07:22 node-1 puppet-user[9172]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 20 19:07:22 node-1 puppet-user[9172]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Sep 20 19:07:24 node-1 puppet-user[9172]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 20 19:07:24 node-1 puppet-user[9172]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 20 19:07:24 node-1 puppet-user[9172]: Finished catalog run in 1.06 seconds
Sep 20 19:07:25 node-1 multipathd: uevent trigger error
Sep 20 19:07:25 node-1 puppet-user[9612]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 20 19:07:25 node-1 puppet-user[9612]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Sep 20 19:07:26 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 20 19:07:26 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 20 19:07:26 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 20 19:07:26 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 20 19:07:26 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 20 19:07:26 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 20 19:07:26 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 20 19:07:26 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 20 19:07:26 node-1 puppet-user[9612]: Finished catalog run in 0.06 seconds
Sep 20 19:07:27 node-1 puppet-user[10075]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 20 19:07:27 node-1 puppet-user[10075]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Sep 20 19:07:27 node-1 puppet-user[10075]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 20 19:07:27 node-1 puppet-user[10075]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 20 19:07:27 node-1 puppet-user[10075]: Finished catalog run in 0.03 seconds
Sep 20 19:07:29 node-1 puppet-user[10540]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 20 19:07:29 node-1 puppet-user[10540]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 20 19:07:29 node-1 puppet-user[10540]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 20 19:07:29 node-1 puppet-user[10540]: Finished catalog run in 0.03 seconds
Sep 20 19:07:30 node-1 puppet-user[10994]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 20 19:07:30 node-1 puppet-user[10994]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Sep 20 19:07:30 node-1 puppet-user[10994]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 20 19:07:32 node-1 puppet-user[10994]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Sep 20 19:07:32 node-1 puppet-user[10994]: Finished catalog run in 2.02 seconds
Sep 20 19:07:34 node-1 puppet-user[11530]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 20 19:07:34 node-1 puppet-user[11530]: Compiled catalog for node-1.domain.tld in environment production in 0.22 seconds
Sep 20 19:07:34 node-1 puppet-user[11530]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 20 19:07:34 node-1 puppet-user[11530]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Sep 20 19:07:34 node-1 puppet-user[11530]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 20 19:07:34 node-1 puppet-user[11530]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 20 19:07:34 node-1 puppet-user[11530]: Finished catalog run in 0.26 seconds
Sep 20 19:07:36 node-1 puppet-user[12198]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 20 19:07:36 node-1 puppet-user[12198]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Sep 20 19:07:36 node-1 puppet-user[12198]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 20 19:07:36 node-1 kernel: [   71.127986] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 20 19:07:36 node-1 kernel: [   71.128039] 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 20 19:07:36 node-1 puppet-user[12198]: (/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 20 19:07:36 node-1 puppet-user[12198]: Finished catalog run in 0.06 seconds
Sep 20 19:07:38 node-1 puppet-user[12657]: (Scope(Class[main])) MODULAR: sync_time
Sep 20 19:07:38 node-1 puppet-user[12657]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 20 19:07:38 node-1 ntpdate[13084]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 20 19:07:44 node-1 ntpdate[13084]: adjust time server 10.20.0.2 offset 0.001911 sec
Sep 20 19:07:44 node-1 puppet-user[12657]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 20 19:07:44 node-1 puppet-user[12657]: Finished catalog run in 6.17 seconds
Sep 20 19:07:46 node-1 kernel: [   81.595687] init: plymouth-upstart-bridge main process ended, respawning
Sep 20 19:07:47 node-1 puppet-agent[8964]: Could not run: SIGTERM
Sep 20 19:07:47 node-1 kernel: [   81.910427] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 20 19:07:47 node-1 ec2: 
Sep 20 19:07:47 node-1 ec2: #############################################################
Sep 20 19:07:47 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 20 19:07:47 node-1 ec2: 1024 ad:da:ff:b1:8b:4c:07:83:a1:3e:a7:73:60:93:3e:6e  root@node-1.domain.tld (DSA)
Sep 20 19:07:47 node-1 ec2: 256 e4:5f:a9:e2:34:a4:40:98:8b:a3:62:5e:54:d9:3f:05  root@node-1.domain.tld (ECDSA)
Sep 20 19:07:47 node-1 ec2: 256 6d:38:ee:89:db:91:63:17:ca:a2:2c:15:e0:52:b5:01  root@node-1.domain.tld (ED25519)
Sep 20 19:07:47 node-1 ec2: 2048 b4:e0:81:d0:45:86:00:98:46:61:d7:bf:c8:6b:04:ef  root@node-1.domain.tld (RSA)
Sep 20 19:07:47 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 20 19:07:47 node-1 ec2: #############################################################
Sep 20 19:07:49 node-1 puppet-user[13472]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 20 19:07:49 node-1 puppet-user[13472]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Sep 20 19:07:49 node-1 puppet-user[13472]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 20 19:07:49 node-1 puppet-user[13472]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Sep 20 19:07:49 node-1 puppet-user[13472]: Finished catalog run in 0.08 seconds
Sep 20 19:07:50 node-1 puppet-user[13935]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 20 19:07:51 node-1 puppet-user[13935]: Compiled catalog for node-1.domain.tld in environment production in 0.49 seconds
Sep 20 19:07:51 node-1 puppet-user[13935]: (/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 20 19:07:51 node-1 puppet-user[13935]: (/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 20 19:07:51 node-1 puppet-user[13935]: (/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 20 19:07:51 node-1 puppet-user[13935]: (/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 20 19:07:51 node-1 puppet-user[13935]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 20 19:07:51 node-1 puppet-user[13935]: (/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 20 19:07:51 node-1 puppet-user[13935]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 20 19:07:51 node-1 puppet-user[13935]: (/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 20 19:07:51 node-1 puppet-user[13935]: (/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 20 19:07:51 node-1 puppet-user[13935]: (/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 20 19:07:52 node-1 puppet-user[13935]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 20 19:07:52 node-1 puppet-user[13935]: Finished catalog run in 0.88 seconds
Sep 20 19:07:54 node-1 puppet-user[14457]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 20 19:07:54 node-1 puppet-user[14457]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Sep 20 19:07:57 node-1 puppet-user[14457]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 20 19:08:01 node-1 CRON[15991]: (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 20 19:08:13 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 20 19:08:13 node-1 nailgun-agent: I, [2016-09-20T19:08:13.571064 #15994]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 20 19:08:26 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 20 19:08:26 node-1 nailgun-agent: I, [2016-09-20T19:08:26.664881 #15994]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep 20 19:08:28 node-1 puppet-user[14457]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 20 19:08:28 node-1 puppet-user[14457]: Finished catalog run in 34.22 seconds
Sep 20 19:08:30 node-1 puppet-user[17660]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 20 19:08:30 node-1 puppet-user[17660]: Compiled catalog for node-1.domain.tld in environment production in 0.54 seconds
Sep 20 19:08:30 node-1 puppet-user[17660]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 20 19:08:30 node-1 puppet-user[17660]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 20 19:08:30 node-1 puppet-user[17660]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 20 19:08:30 node-1 puppet-user[17660]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 20 19:08:31 node-1 puppet-user[17660]: Finished catalog run in 0.07 seconds
Sep 20 19:08:32 node-1 puppet-user[18139]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 20 19:08:33 node-1 puppet-user[18139]: Compiled catalog for node-1.domain.tld in environment production in 0.85 seconds
Sep 20 19:08:33 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 20 19:08:34 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 20 19:08:34 node-1 crontab[18572]: (root) LIST (root)
Sep 20 19:08:34 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 20 19:08:34 node-1 crontab[18573]: (root) REPLACE (root)
Sep 20 19:08:35 node-1 puppet-user[18139]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/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 20 19:08:36 node-1 puppet-user[18139]: (/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 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/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 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/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 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/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 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 20 19:08:36 node-1 puppet-user[18139]: (/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 20 19:08:37 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 20 19:08:37 node-1 puppet-user[18139]: (/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 20 19:08:37 node-1 puppet-user[18139]: (/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 20 19:08:37 node-1 puppet-user[18139]: (/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 20 19:08:37 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 20 19:08:37 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 20 19:08:37 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 20 19:08:37 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 20 19:08:37 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 20 19:08:37 node-1 puppet-user[18139]: (/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 20 19:08:37 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 20 19:08:37 node-1 puppet-user[18139]: (/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 20 19:08:37 node-1 puppet-user[18139]: (/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 20 19:08:37 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 20 19:08:37 node-1 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 20 19:08:37 node-1 puppet-user[18139]: (/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 20 19:08:37 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8416" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 20 19:08:37 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 20 19:08:39 node-1 multipathd: uevent trigger error
<27>Sep 20 19:08:39 node-1 multipathd: uevent trigger error
<27>Sep 20 19:08:39 node-1 multipathd: uevent trigger error
<27>Sep 20 19:08:39 node-1 multipathd: uevent trigger error
<27>Sep 20 19:08:39 node-1 multipathd: uevent trigger error
<27>Sep 20 19:08:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:08:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:08:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:08:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:08:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:08:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:09:42 node-1 multipathd: uevent trigger error
<27>Sep 20 19:09:42 node-1 multipathd: uevent trigger error
<27>Sep 20 19:09:42 node-1 multipathd: uevent trigger error
<27>Sep 20 19:09:42 node-1 multipathd: uevent trigger error
<27>Sep 20 19:09:42 node-1 multipathd: uevent trigger error
<27>Sep 20 19:09:42 node-1 multipathd: uevent trigger error
<27>Sep 20 19:10:23 node-1 ntpdate[1764]: no servers can be used, exiting
<27>Sep 20 19:10:23 node-1 ntpdate[2057]: no servers can be used, exiting
<27>Sep 20 19:10:55 node-1 multipathd: uevent trigger error
<27>Sep 20 19:10:55 node-1 multipathd: uevent trigger error
<27>Sep 20 19:10:55 node-1 multipathd: uevent trigger error
<27>Sep 20 19:10:55 node-1 multipathd: uevent trigger error
<27>Sep 20 19:10:55 node-1 multipathd: uevent trigger error
<27>Sep 20 19:10:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:10:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:10:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:10:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:10:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:11:09 node-1 multipathd: uevent trigger error
<27>Sep 20 19:11:09 node-1 multipathd: uevent trigger error
<27>Sep 20 19:11:09 node-1 multipathd: uevent trigger error
<27>Sep 20 19:11:09 node-1 multipathd: uevent trigger error
<27>Sep 20 19:11:09 node-1 multipathd: uevent trigger error
<27>Sep 20 19:11:12 node-1 multipathd: uevent trigger error
<27>Sep 20 19:11:12 node-1 multipathd: uevent trigger error
<27>Sep 20 19:11:12 node-1 multipathd: uevent trigger error
<27>Sep 20 19:11:12 node-1 multipathd: uevent trigger error
<27>Sep 20 19:11:12 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:21 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 20 19:12:21 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 20 19:12:27 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 20 19:12:27 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 20 19:12:33 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 20 19:12:38 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 20 19:12:38 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 20 19:12:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:12:58 node-1 multipathd: uevent trigger error
<129>Sep 20 19:13:00 node-1 haproxy[21978]: 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 20 19:13:01 node-1 haproxy[21984]: Backup Server mysqld/node-3 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 20 19:13:02 node-1 haproxy[21984]: 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 20 19:13:02 node-1 haproxy[21984]: proxy mysqld has no server available!
<27>Sep 20 19:13:04 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:04 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:04 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:04 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:04 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:04 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:07 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:07 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:07 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:07 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:07 node-1 multipathd: uevent trigger error
<129>Sep 20 19:13:10 node-1 haproxy[24636]: 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 20 19:13:10 node-1 haproxy[24636]: Backup Server mysqld/node-3 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 20 19:13:11 node-1 haproxy[24640]: 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 20 19:13:11 node-1 haproxy[24640]: proxy mysqld has no server available!
<129>Sep 20 19:13:11 node-1 haproxy[24640]: 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 20 19:13:11 node-1 haproxy[24640]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:12 node-1 haproxy[24640]: 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 20 19:13:12 node-1 haproxy[24640]: proxy object-storage has no server available!
<27>Sep 20 19:13:13 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:13 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:13 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:13 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:13 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:13 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:13 node-1 multipathd: uevent trigger error
<129>Sep 20 19:13:15 node-1 haproxy[25989]: 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 20 19:13:15 node-1 haproxy[25989]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:16 node-1 haproxy[25993]: 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 20 19:13:16 node-1 haproxy[25993]: proxy neutron has no server available!
<129>Sep 20 19:13:16 node-1 haproxy[25993]: 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 20 19:13:16 node-1 haproxy[25993]: Backup Server mysqld/node-3 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 20 19:13:16 node-1 haproxy[25993]: 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 20 19:13:16 node-1 haproxy[25993]: proxy mysqld has no server available!
<129>Sep 20 19:13:16 node-1 haproxy[25993]: 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 20 19:13:17 node-1 haproxy[25993]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:17 node-1 haproxy[25993]: 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 20 19:13:17 node-1 haproxy[25993]: proxy object-storage has no server available!
<27>Sep 20 19:13:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:18 node-1 multipathd: uevent trigger error
<129>Sep 20 19:13:20 node-1 haproxy[27498]: 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 20 19:13:21 node-1 haproxy[27502]: Server keystone-1/node-3 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 20 19:13:21 node-1 haproxy[27502]: 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 20 19:13:21 node-1 haproxy[27502]: proxy keystone-1 has no server available!
<129>Sep 20 19:13:21 node-1 haproxy[27502]: 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 20 19:13:21 node-1 haproxy[27502]: Server keystone-2/node-3 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 20 19:13:21 node-1 haproxy[27502]: 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 20 19:13:21 node-1 haproxy[27502]: proxy keystone-2 has no server available!
<129>Sep 20 19:13:21 node-1 haproxy[27502]: 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 20 19:13:21 node-1 haproxy[27502]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:22 node-1 haproxy[27502]: 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 20 19:13:22 node-1 haproxy[27502]: proxy neutron has no server available!
<129>Sep 20 19:13:22 node-1 haproxy[27502]: 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 20 19:13:22 node-1 haproxy[27502]: Backup Server mysqld/node-3 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 20 19:13:22 node-1 haproxy[27502]: 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 20 19:13:22 node-1 haproxy[27502]: proxy mysqld has no server available!
<129>Sep 20 19:13:22 node-1 haproxy[27502]: 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 20 19:13:22 node-1 haproxy[27502]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:22 node-1 haproxy[27502]: 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 20 19:13:22 node-1 haproxy[27502]: proxy object-storage has no server available!
<27>Sep 20 19:13:24 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:24 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:24 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:24 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:24 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:24 node-1 multipathd: uevent trigger error
<129>Sep 20 19:13:26 node-1 haproxy[28882]: 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 20 19:13:26 node-1 haproxy[28882]: Server keystone-1/node-3 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 20 19:13:26 node-1 haproxy[28882]: 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 20 19:13:26 node-1 haproxy[28882]: proxy keystone-1 has no server available!
<129>Sep 20 19:13:26 node-1 haproxy[28882]: 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 20 19:13:26 node-1 haproxy[28882]: Server keystone-2/node-3 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 20 19:13:26 node-1 haproxy[28882]: 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 20 19:13:26 node-1 haproxy[28882]: proxy keystone-2 has no server available!
<129>Sep 20 19:13:26 node-1 haproxy[28882]: 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 20 19:13:26 node-1 haproxy[28882]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:27 node-1 haproxy[28886]: 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 20 19:13:27 node-1 haproxy[28886]: proxy neutron has no server available!
<129>Sep 20 19:13:27 node-1 haproxy[28886]: 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 20 19:13:27 node-1 haproxy[28886]: Backup Server mysqld/node-3 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 20 19:13:27 node-1 haproxy[28886]: 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 20 19:13:27 node-1 haproxy[28886]: proxy mysqld has no server available!
<129>Sep 20 19:13:27 node-1 haproxy[28886]: 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 20 19:13:27 node-1 haproxy[28886]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:27 node-1 haproxy[28886]: 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 20 19:13:27 node-1 haproxy[28886]: proxy object-storage has no server available!
<129>Sep 20 19:13:27 node-1 haproxy[28886]: 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 20 19:13:27 node-1 haproxy[28886]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:28 node-1 haproxy[28886]: 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 20 19:13:28 node-1 haproxy[28886]: proxy aodh has no server available!
<27>Sep 20 19:13:29 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:29 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:29 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:29 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:29 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:29 node-1 multipathd: uevent trigger error
<129>Sep 20 19:13:31 node-1 haproxy[30423]: 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 20 19:13:31 node-1 haproxy[30423]: Server keystone-1/node-3 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 20 19:13:31 node-1 haproxy[30423]: 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 20 19:13:31 node-1 haproxy[30423]: proxy keystone-1 has no server available!
<129>Sep 20 19:13:31 node-1 haproxy[30423]: 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 20 19:13:32 node-1 haproxy[30429]: Server keystone-2/node-3 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 20 19:13:32 node-1 haproxy[30429]: 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 20 19:13:32 node-1 haproxy[30429]: proxy keystone-2 has no server available!
<129>Sep 20 19:13:32 node-1 haproxy[30429]: 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 20 19:13:32 node-1 haproxy[30429]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:32 node-1 haproxy[30429]: 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 20 19:13:32 node-1 haproxy[30429]: proxy neutron has no server available!
<129>Sep 20 19:13:32 node-1 haproxy[30429]: 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 20 19:13:32 node-1 haproxy[30429]: Backup Server mysqld/node-3 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 20 19:13:32 node-1 haproxy[30429]: 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 20 19:13:32 node-1 haproxy[30429]: proxy mysqld has no server available!
<129>Sep 20 19:13:32 node-1 haproxy[30429]: 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 20 19:13:32 node-1 haproxy[30429]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:32 node-1 haproxy[30429]: 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 20 19:13:32 node-1 haproxy[30429]: proxy object-storage has no server available!
<129>Sep 20 19:13:33 node-1 haproxy[30429]: 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 20 19:13:33 node-1 haproxy[30429]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:33 node-1 haproxy[30429]: 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 20 19:13:33 node-1 haproxy[30429]: proxy aodh has no server available!
<129>Sep 20 19:13:33 node-1 haproxy[30429]: 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 20 19:13:33 node-1 haproxy[30429]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:33 node-1 haproxy[30429]: 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 20 19:13:33 node-1 haproxy[30429]: proxy ceilometer has no server available!
<27>Sep 20 19:13:34 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:34 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:34 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:34 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:34 node-1 multipathd: uevent trigger error
<129>Sep 20 19:13:37 node-1 haproxy[31776]: 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 20 19:13:37 node-1 haproxy[31776]: Server keystone-1/node-3 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 20 19:13:37 node-1 haproxy[31776]: 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 20 19:13:37 node-1 haproxy[31776]: proxy keystone-1 has no server available!
<129>Sep 20 19:13:37 node-1 haproxy[31776]: 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 20 19:13:37 node-1 haproxy[31776]: Server keystone-2/node-3 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 20 19:13:37 node-1 haproxy[31776]: 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 20 19:13:37 node-1 haproxy[31776]: proxy keystone-2 has no server available!
<129>Sep 20 19:13:37 node-1 haproxy[31776]: 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 20 19:13:37 node-1 haproxy[31776]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:37 node-1 haproxy[31776]: 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 20 19:13:37 node-1 haproxy[31776]: proxy neutron has no server available!
<129>Sep 20 19:13:38 node-1 haproxy[31780]: 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 20 19:13:38 node-1 haproxy[31780]: Backup Server mysqld/node-3 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 20 19:13:38 node-1 haproxy[31780]: 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 20 19:13:38 node-1 haproxy[31780]: proxy mysqld has no server available!
<129>Sep 20 19:13:38 node-1 haproxy[31780]: 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 20 19:13:38 node-1 haproxy[31780]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:38 node-1 haproxy[31780]: 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 20 19:13:38 node-1 haproxy[31780]: proxy object-storage has no server available!
<129>Sep 20 19:13:38 node-1 haproxy[31780]: 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 20 19:13:38 node-1 haproxy[31780]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:38 node-1 haproxy[31780]: 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 20 19:13:38 node-1 haproxy[31780]: proxy aodh has no server available!
<129>Sep 20 19:13:38 node-1 haproxy[31780]: 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 20 19:13:38 node-1 haproxy[31780]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:39 node-1 haproxy[31780]: 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 20 19:13:39 node-1 haproxy[31780]: proxy ceilometer has no server available!
<27>Sep 20 19:13:40 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:40 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:40 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:40 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:40 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:40 node-1 multipathd: uevent trigger error
<129>Sep 20 19:13:42 node-1 haproxy[701]: 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 20 19:13:42 node-1 haproxy[701]: 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 20 19:13:42 node-1 haproxy[701]: Server keystone-1/node-3 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 20 19:13:42 node-1 haproxy[701]: 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 20 19:13:42 node-1 haproxy[701]: proxy keystone-1 has no server available!
<129>Sep 20 19:13:43 node-1 haproxy[716]: 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 20 19:13:43 node-1 haproxy[716]: Server keystone-2/node-3 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 20 19:13:43 node-1 haproxy[716]: 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 20 19:13:43 node-1 haproxy[716]: proxy keystone-2 has no server available!
<129>Sep 20 19:13:43 node-1 haproxy[716]: 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 20 19:13:43 node-1 haproxy[716]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:43 node-1 haproxy[716]: 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 20 19:13:43 node-1 haproxy[716]: proxy neutron has no server available!
<129>Sep 20 19:13:43 node-1 haproxy[716]: 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 20 19:13:43 node-1 haproxy[716]: Backup Server mysqld/node-3 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 20 19:13:43 node-1 haproxy[716]: 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 20 19:13:43 node-1 haproxy[716]: proxy mysqld has no server available!
<129>Sep 20 19:13:43 node-1 haproxy[716]: 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 20 19:13:43 node-1 haproxy[716]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:43 node-1 haproxy[716]: 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 20 19:13:43 node-1 haproxy[716]: proxy object-storage has no server available!
<129>Sep 20 19:13:44 node-1 haproxy[716]: 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 20 19:13:44 node-1 haproxy[716]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:44 node-1 haproxy[716]: 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 20 19:13:44 node-1 haproxy[716]: proxy aodh has no server available!
<129>Sep 20 19:13:44 node-1 haproxy[716]: 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 20 19:13:44 node-1 haproxy[716]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:44 node-1 haproxy[716]: 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 20 19:13:44 node-1 haproxy[716]: proxy ceilometer has no server available!
<27>Sep 20 19:13:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:45 node-1 multipathd: uevent trigger error
<129>Sep 20 19:13:48 node-1 haproxy[2125]: 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 20 19:13:48 node-1 haproxy[2125]: 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 20 19:13:48 node-1 haproxy[2125]: Server keystone-1/node-3 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 20 19:13:48 node-1 haproxy[2125]: 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 20 19:13:48 node-1 haproxy[2125]: proxy keystone-1 has no server available!
<129>Sep 20 19:13:48 node-1 haproxy[2125]: 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 20 19:13:48 node-1 haproxy[2125]: Server keystone-2/node-3 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 20 19:13:48 node-1 haproxy[2125]: 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 20 19:13:48 node-1 haproxy[2125]: proxy keystone-2 has no server available!
<129>Sep 20 19:13:48 node-1 haproxy[2125]: 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 20 19:13:48 node-1 haproxy[2125]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:49 node-1 haproxy[2129]: 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 20 19:13:49 node-1 haproxy[2129]: proxy glance-api has no server available!
<129>Sep 20 19:13:49 node-1 haproxy[2129]: 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 20 19:13:49 node-1 haproxy[2129]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:49 node-1 haproxy[2129]: 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 20 19:13:49 node-1 haproxy[2129]: proxy glance-glare has no server available!
<129>Sep 20 19:13:49 node-1 haproxy[2129]: 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 20 19:13:49 node-1 haproxy[2129]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:49 node-1 haproxy[2129]: 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 20 19:13:49 node-1 haproxy[2129]: proxy neutron has no server available!
<129>Sep 20 19:13:49 node-1 haproxy[2129]: 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 20 19:13:49 node-1 haproxy[2129]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:49 node-1 haproxy[2129]: 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 20 19:13:49 node-1 haproxy[2129]: proxy glance-registry has no server available!
<129>Sep 20 19:13:49 node-1 haproxy[2129]: 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 20 19:13:49 node-1 haproxy[2129]: Backup Server mysqld/node-3 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 20 19:13:49 node-1 haproxy[2129]: 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 20 19:13:49 node-1 haproxy[2129]: proxy mysqld has no server available!
<129>Sep 20 19:13:49 node-1 haproxy[2129]: 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 20 19:13:49 node-1 haproxy[2129]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:49 node-1 haproxy[2129]: 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 20 19:13:49 node-1 haproxy[2129]: proxy object-storage has no server available!
<129>Sep 20 19:13:50 node-1 haproxy[2129]: 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 20 19:13:50 node-1 haproxy[2129]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:50 node-1 haproxy[2129]: 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 20 19:13:50 node-1 haproxy[2129]: proxy aodh has no server available!
<129>Sep 20 19:13:50 node-1 haproxy[2129]: 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 20 19:13:50 node-1 haproxy[2129]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:50 node-1 haproxy[2129]: 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 20 19:13:50 node-1 haproxy[2129]: proxy ceilometer has no server available!
<27>Sep 20 19:13:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:52 node-1 multipathd: uevent trigger error
<129>Sep 20 19:13:55 node-1 haproxy[3538]: 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 20 19:13:55 node-1 haproxy[3538]: 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 20 19:13:55 node-1 haproxy[3538]: Server keystone-1/node-3 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 20 19:13:55 node-1 haproxy[3538]: 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 20 19:13:55 node-1 haproxy[3538]: proxy keystone-1 has no server available!
<129>Sep 20 19:13:55 node-1 haproxy[3538]: 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 20 19:13:55 node-1 haproxy[3538]: Server keystone-2/node-3 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 20 19:13:55 node-1 haproxy[3538]: 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 20 19:13:55 node-1 haproxy[3538]: proxy keystone-2 has no server available!
<129>Sep 20 19:13:55 node-1 haproxy[3538]: 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 20 19:13:55 node-1 haproxy[3538]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:55 node-1 haproxy[3538]: 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 20 19:13:55 node-1 haproxy[3538]: proxy nova-api has no server available!
<129>Sep 20 19:13:55 node-1 haproxy[3538]: 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 20 19:13:55 node-1 haproxy[3538]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:55 node-1 haproxy[3538]: 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 20 19:13:55 node-1 haproxy[3538]: proxy nova-metadata-api has no server available!
<129>Sep 20 19:13:55 node-1 haproxy[3538]: 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 20 19:13:55 node-1 haproxy[3538]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:55 node-1 haproxy[3538]: 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 20 19:13:55 node-1 haproxy[3538]: proxy glance-api has no server available!
<129>Sep 20 19:13:55 node-1 haproxy[3538]: 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 20 19:13:55 node-1 haproxy[3538]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:55 node-1 haproxy[3538]: 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 20 19:13:55 node-1 haproxy[3538]: proxy glance-glare has no server available!
<129>Sep 20 19:13:56 node-1 haproxy[3542]: 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 20 19:13:56 node-1 haproxy[3542]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:56 node-1 haproxy[3542]: 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 20 19:13:56 node-1 haproxy[3542]: proxy neutron has no server available!
<129>Sep 20 19:13:56 node-1 haproxy[3542]: 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 20 19:13:56 node-1 haproxy[3542]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:56 node-1 haproxy[3542]: 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 20 19:13:56 node-1 haproxy[3542]: proxy glance-registry has no server available!
<129>Sep 20 19:13:56 node-1 haproxy[3542]: 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 20 19:13:56 node-1 haproxy[3542]: Backup Server mysqld/node-3 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 20 19:13:56 node-1 haproxy[3542]: 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 20 19:13:56 node-1 haproxy[3542]: proxy mysqld has no server available!
<129>Sep 20 19:13:56 node-1 haproxy[3542]: 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 20 19:13:56 node-1 haproxy[3542]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:56 node-1 haproxy[3542]: 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 20 19:13:56 node-1 haproxy[3542]: proxy object-storage has no server available!
<129>Sep 20 19:13:56 node-1 haproxy[3542]: 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 20 19:13:56 node-1 haproxy[3542]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:56 node-1 haproxy[3542]: 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 20 19:13:56 node-1 haproxy[3542]: proxy aodh has no server available!
<129>Sep 20 19:13:56 node-1 haproxy[3542]: 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 20 19:13:56 node-1 haproxy[3542]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:56 node-1 haproxy[3542]: 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 20 19:13:56 node-1 haproxy[3542]: proxy ceilometer has no server available!
<129>Sep 20 19:13:56 node-1 haproxy[3542]: 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 20 19:13:56 node-1 haproxy[3542]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:13:56 node-1 haproxy[3542]: 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 20 19:13:56 node-1 haproxy[3542]: proxy nova-novncproxy has no server available!
<27>Sep 20 19:13:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:13:58 node-1 multipathd: uevent trigger error
<129>Sep 20 19:14:00 node-1 haproxy[4879]: 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 20 19:14:00 node-1 haproxy[4879]: 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 20 19:14:00 node-1 haproxy[4879]: Server keystone-1/node-3 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 20 19:14:00 node-1 haproxy[4879]: 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 20 19:14:00 node-1 haproxy[4879]: proxy keystone-1 has no server available!
<129>Sep 20 19:14:00 node-1 haproxy[4879]: 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 20 19:14:00 node-1 haproxy[4879]: Server keystone-2/node-3 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 20 19:14:00 node-1 haproxy[4879]: 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 20 19:14:00 node-1 haproxy[4879]: proxy keystone-2 has no server available!
<129>Sep 20 19:14:00 node-1 haproxy[4879]: 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 20 19:14:00 node-1 haproxy[4879]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:01 node-1 haproxy[4883]: 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 20 19:14:01 node-1 haproxy[4883]: proxy nova-api has no server available!
<129>Sep 20 19:14:01 node-1 haproxy[4883]: 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 20 19:14:01 node-1 haproxy[4883]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:01 node-1 haproxy[4883]: 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 20 19:14:01 node-1 haproxy[4883]: proxy nova-metadata-api has no server available!
<129>Sep 20 19:14:01 node-1 haproxy[4883]: 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 20 19:14:01 node-1 haproxy[4883]: Backup Server cinder-api/node-3 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 20 19:14:01 node-1 haproxy[4883]: 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 20 19:14:01 node-1 haproxy[4883]: proxy cinder-api has no server available!
<129>Sep 20 19:14:01 node-1 haproxy[4883]: 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 20 19:14:01 node-1 haproxy[4883]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:01 node-1 haproxy[4883]: 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 20 19:14:01 node-1 haproxy[4883]: proxy glance-api has no server available!
<129>Sep 20 19:14:01 node-1 haproxy[4883]: 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 20 19:14:01 node-1 haproxy[4883]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:01 node-1 haproxy[4883]: 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 20 19:14:01 node-1 haproxy[4883]: proxy glance-glare has no server available!
<129>Sep 20 19:14:01 node-1 haproxy[4883]: 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 20 19:14:01 node-1 haproxy[4883]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:01 node-1 haproxy[4883]: 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 20 19:14:01 node-1 haproxy[4883]: proxy neutron has no server available!
<129>Sep 20 19:14:01 node-1 haproxy[4883]: 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 20 19:14:01 node-1 haproxy[4883]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:01 node-1 haproxy[4883]: 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 20 19:14:01 node-1 haproxy[4883]: proxy glance-registry has no server available!
<129>Sep 20 19:14:01 node-1 haproxy[4883]: 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 20 19:14:01 node-1 haproxy[4883]: Backup Server mysqld/node-3 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 20 19:14:01 node-1 haproxy[4883]: 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 20 19:14:01 node-1 haproxy[4883]: proxy mysqld has no server available!
<129>Sep 20 19:14:02 node-1 haproxy[4883]: 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 20 19:14:02 node-1 haproxy[4883]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:02 node-1 haproxy[4883]: 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 20 19:14:02 node-1 haproxy[4883]: proxy object-storage has no server available!
<129>Sep 20 19:14:02 node-1 haproxy[4883]: 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 20 19:14:02 node-1 haproxy[4883]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:02 node-1 haproxy[4883]: 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 20 19:14:02 node-1 haproxy[4883]: proxy aodh has no server available!
<129>Sep 20 19:14:02 node-1 haproxy[4883]: 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 20 19:14:02 node-1 haproxy[4883]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:02 node-1 haproxy[4883]: 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 20 19:14:02 node-1 haproxy[4883]: proxy ceilometer has no server available!
<129>Sep 20 19:14:02 node-1 haproxy[4883]: 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 20 19:14:02 node-1 haproxy[4883]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:02 node-1 haproxy[4883]: 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 20 19:14:02 node-1 haproxy[4883]: proxy nova-novncproxy has no server available!
<27>Sep 20 19:14:03 node-1 multipathd: uevent trigger error
<27>Sep 20 19:14:03 node-1 multipathd: uevent trigger error
<27>Sep 20 19:14:03 node-1 multipathd: uevent trigger error
<27>Sep 20 19:14:03 node-1 multipathd: uevent trigger error
<27>Sep 20 19:14:03 node-1 multipathd: uevent trigger error
<129>Sep 20 19:14:06 node-1 haproxy[6261]: 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 20 19:14:06 node-1 haproxy[6261]: 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 20 19:14:06 node-1 haproxy[6261]: Server keystone-1/node-3 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 20 19:14:06 node-1 haproxy[6261]: 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 20 19:14:06 node-1 haproxy[6261]: proxy keystone-1 has no server available!
<129>Sep 20 19:14:06 node-1 haproxy[6261]: 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 20 19:14:06 node-1 haproxy[6261]: Server keystone-2/node-3 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 20 19:14:06 node-1 haproxy[6261]: 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 20 19:14:06 node-1 haproxy[6261]: proxy keystone-2 has no server available!
<129>Sep 20 19:14:06 node-1 haproxy[6261]: 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 20 19:14:06 node-1 haproxy[6261]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:06 node-1 haproxy[6261]: 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 20 19:14:06 node-1 haproxy[6261]: proxy nova-api has no server available!
<129>Sep 20 19:14:06 node-1 haproxy[6261]: 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 20 19:14:06 node-1 haproxy[6261]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:06 node-1 haproxy[6261]: 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 20 19:14:06 node-1 haproxy[6261]: proxy nova-metadata-api has no server available!
<129>Sep 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: Backup Server cinder-api/node-3 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 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: proxy cinder-api has no server available!
<129>Sep 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: proxy glance-api has no server available!
<129>Sep 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: proxy glance-glare has no server available!
<129>Sep 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: proxy neutron has no server available!
<129>Sep 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: proxy glance-registry has no server available!
<129>Sep 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: Backup Server mysqld/node-3 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 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: proxy mysqld has no server available!
<129>Sep 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: proxy object-storage has no server available!
<129>Sep 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: proxy aodh has no server available!
<129>Sep 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:07 node-1 haproxy[6265]: 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 20 19:14:07 node-1 haproxy[6265]: proxy ceilometer has no server available!
<129>Sep 20 19:14:08 node-1 haproxy[6265]: 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 20 19:14:08 node-1 haproxy[6265]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:08 node-1 haproxy[6265]: 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 20 19:14:08 node-1 haproxy[6265]: proxy heat-api has no server available!
<129>Sep 20 19:14:08 node-1 haproxy[6265]: 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 20 19:14:08 node-1 haproxy[6265]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:08 node-1 haproxy[6265]: 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 20 19:14:08 node-1 haproxy[6265]: proxy heat-api-cfn has no server available!
<129>Sep 20 19:14:08 node-1 haproxy[6265]: 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 20 19:14:08 node-1 haproxy[6265]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:08 node-1 haproxy[6265]: 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 20 19:14:08 node-1 haproxy[6265]: proxy heat-api-cloudwatch has no server available!
<129>Sep 20 19:14:08 node-1 haproxy[6265]: 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 20 19:14:08 node-1 haproxy[6265]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 20 19:14:08 node-1 haproxy[6265]: 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 20 19:14:08 node-1 haproxy[6265]: proxy nova-novncproxy has no server available!
<27>Sep 20 19:14:09 node-1 multipathd: uevent trigger error
<27>Sep 20 19:14:09 node-1 multipathd: uevent trigger error
<27>Sep 20 19:14:09 node-1 multipathd: uevent trigger error
<27>Sep 20 19:14:09 node-1 multipathd: uevent trigger error
<27>Sep 20 19:14:09 node-1 multipathd: uevent trigger error
<27>Sep 20 19:14:09 node-1 multipathd: uevent trigger error
<27>Sep 20 19:14:13 node-1 multipathd: uevent trigger error
<27>Sep 20 19:14:13 node-1 multipathd: uevent trigger error
<27>Sep 20 19:14:13 node-1 multipathd: uevent trigger error
<27>Sep 20 19:14:13 node-1 multipathd: uevent trigger error
<27>Sep 20 19:14:13 node-1 multipathd: uevent trigger error
<27>Sep 20 19:14:13 node-1 multipathd: uevent trigger error
<27>Sep 20 19:14:20 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 20 19:14:41 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 20 19:14:44 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 20 19:14:46 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 20 19:15:19 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 20 19:15:43 node-1 multipathd: uevent trigger error
<27>Sep 20 19:15:43 node-1 multipathd: uevent trigger error
<27>Sep 20 19:15:43 node-1 multipathd: uevent trigger error
<27>Sep 20 19:15:43 node-1 multipathd: uevent trigger error
<27>Sep 20 19:15:43 node-1 multipathd: uevent trigger error
<27>Sep 20 19:15:43 node-1 multipathd: uevent trigger error
<27>Sep 20 19:17:42 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 20 19:17:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:17:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:17:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:17:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:17:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:17:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:17:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:17:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:17:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:17:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:17:58 node-1 multipathd: uevent trigger error
<43>Sep 20 19:18:18 node-1 apache2_error [Tue Sep 20 19:18:10.228711 2016] [mpm_event:notice] [pid 15106:tid 139726707353472] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 20 19:18:18 node-1 apache2_error [Tue Sep 20 19:18:10.228847 2016] [core:notice] [pid 15106:tid 139726707353472] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 20 19:18:18 node-1 apache2_error [Tue Sep 20 19:18:13.262857 2016] [mpm_event:notice] [pid 15106:tid 139726707353472] AH00491: caught SIGTERM, shutting down
<43>Sep 20 19:18:18 node-1 apache2_error [Tue Sep 20 19:18:14.359454 2016] [mpm_worker:notice] [pid 16586:tid 140030234859392] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 20 19:18:18 node-1 apache2_error [Tue Sep 20 19:18:14.359508 2016] [core:notice] [pid 16586:tid 140030234859392] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 20 19:18:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:18:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:18:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:18:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:18:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:18:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:18:23 node-1 multipathd: uevent trigger error
<27>Sep 20 19:18:23 node-1 multipathd: uevent trigger error
<27>Sep 20 19:18:23 node-1 multipathd: uevent trigger error
<27>Sep 20 19:18:23 node-1 multipathd: uevent trigger error
<27>Sep 20 19:18:23 node-1 multipathd: uevent trigger error
<27>Sep 20 19:18:27 node-1 multipathd: uevent trigger error
<27>Sep 20 19:18:27 node-1 multipathd: uevent trigger error
<27>Sep 20 19:18:27 node-1 multipathd: uevent trigger error
<27>Sep 20 19:18:27 node-1 multipathd: uevent trigger error
<27>Sep 20 19:18:27 node-1 multipathd: uevent trigger error
<43>Sep 20 19:19:38 node-1 apache2_error [Tue Sep 20 19:19:34.551786 2016] [mpm_worker:notice] [pid 16586:tid 140030234859392] AH00295: caught SIGTERM, shutting down
<43>Sep 20 19:19:38 node-1 apache2_error [Tue Sep 20 19:19:35.316728 2016] [mpm_worker:notice] [pid 30810:tid 140348476372864] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 20 19:19:38 node-1 apache2_error [Tue Sep 20 19:19:35.316757 2016] [core:notice] [pid 30810:tid 140348476372864] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 20 19:20:28 node-1 apache2_error [Tue Sep 20 19:20:21.113294 2016] [mpm_worker:notice] [pid 30810:tid 140348476372864] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 20 19:20:28 node-1 apache2_error [Tue Sep 20 19:20:21.306547 2016] [mpm_worker:warn] [pid 30810:tid 140348476372864] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 20 19:20:28 node-1 apache2_error [Tue Sep 20 19:20:21.310255 2016] [mpm_worker:notice] [pid 30810:tid 140348476372864] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 20 19:20:28 node-1 apache2_error [Tue Sep 20 19:20:21.310281 2016] [core:notice] [pid 30810:tid 140348476372864] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 20 19:20:44 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 20 19:21:06 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:06 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:06 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:06 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:06 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:06 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:11 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:11 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:11 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:25 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:25 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:25 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:25 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:25 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:47 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:47 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:47 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:47 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:47 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:21:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:22:37 node-1 multipathd: uevent trigger error
<27>Sep 20 19:22:37 node-1 multipathd: uevent trigger error
<27>Sep 20 19:22:37 node-1 multipathd: uevent trigger error
<27>Sep 20 19:22:37 node-1 multipathd: uevent trigger error
<27>Sep 20 19:22:37 node-1 multipathd: uevent trigger error
<27>Sep 20 19:22:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:22:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:22:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:22:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:22:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:23:42 node-1 multipathd: uevent trigger error
<27>Sep 20 19:23:42 node-1 multipathd: uevent trigger error
<27>Sep 20 19:23:42 node-1 multipathd: uevent trigger error
<27>Sep 20 19:23:42 node-1 multipathd: uevent trigger error
<27>Sep 20 19:23:42 node-1 multipathd: uevent trigger error
<27>Sep 20 19:23:57 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 20 19:24:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:24:53 node-1 multipathd: uevent trigger error
<27>Sep 20 19:24:53 node-1 multipathd: uevent trigger error
<27>Sep 20 19:24:53 node-1 multipathd: uevent trigger error
<27>Sep 20 19:24:53 node-1 multipathd: uevent trigger error
<27>Sep 20 19:24:53 node-1 multipathd: uevent trigger error
<27>Sep 20 19:25:51 node-1 multipathd: uevent trigger error
<27>Sep 20 19:25:51 node-1 multipathd: uevent trigger error
<27>Sep 20 19:25:51 node-1 multipathd: uevent trigger error
<27>Sep 20 19:25:51 node-1 multipathd: uevent trigger error
<27>Sep 20 19:25:51 node-1 multipathd: uevent trigger error
<27>Sep 20 19:25:51 node-1 multipathd: uevent trigger error
<27>Sep 20 19:26:14 node-1 multipathd: uevent trigger error
<27>Sep 20 19:26:14 node-1 multipathd: uevent trigger error
<27>Sep 20 19:26:14 node-1 multipathd: uevent trigger error
<27>Sep 20 19:26:14 node-1 multipathd: uevent trigger error
<27>Sep 20 19:26:14 node-1 multipathd: uevent trigger error
<27>Sep 20 19:26:20 node-1 multipathd: uevent trigger error
<27>Sep 20 19:26:20 node-1 multipathd: uevent trigger error
<27>Sep 20 19:26:20 node-1 multipathd: uevent trigger error
<27>Sep 20 19:26:20 node-1 multipathd: uevent trigger error
<27>Sep 20 19:26:20 node-1 multipathd: uevent trigger error
<27>Sep 20 19:26:20 node-1 multipathd: uevent trigger error
<27>Sep 20 19:26:20 node-1 multipathd: uevent trigger error
<27>Sep 20 19:26:58 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 20 19:28:49 node-1 multipathd: uevent trigger error
<27>Sep 20 19:28:49 node-1 multipathd: uevent trigger error
<27>Sep 20 19:28:49 node-1 multipathd: uevent trigger error
<27>Sep 20 19:28:49 node-1 multipathd: uevent trigger error
<27>Sep 20 19:28:49 node-1 multipathd: uevent trigger error
<27>Sep 20 19:28:49 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:04 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:04 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:04 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:04 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:05 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:29:58 node-1 multipathd: uevent trigger error
<27>Sep 20 19:30:00 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 20 19:30:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:30:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:30:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:30:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:30:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:07 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:07 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:07 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:07 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:07 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:07 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:14 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Sep 20 19:31:14 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Sep 20 19:31:14 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Sep 20 19:31:15 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Sep 20 19:31:15 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Sep 20 19:31:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:29 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:29 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:29 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:29 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:29 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:29 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:44 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:44 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:44 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:44 node-1 multipathd: uevent trigger error
<27>Sep 20 19:31:44 node-1 multipathd: uevent trigger error
<27>Sep 20 19:32:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:32:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:32:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:32:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:32:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:32:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:33:02 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 20 19:34:24 node-1 multipathd: uevent trigger error
<27>Sep 20 19:34:24 node-1 multipathd: uevent trigger error
<27>Sep 20 19:34:24 node-1 multipathd: uevent trigger error
<27>Sep 20 19:34:24 node-1 multipathd: uevent trigger error
<27>Sep 20 19:34:24 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:01 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:01 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:01 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:01 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:01 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:06 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:06 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:06 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:06 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:06 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:06 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:36 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:36 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:36 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:36 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:36 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:36 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:41 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:41 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:41 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:41 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:41 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:57 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:57 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:57 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:57 node-1 multipathd: uevent trigger error
<27>Sep 20 19:35:57 node-1 multipathd: uevent trigger error
<27>Sep 20 19:36:03 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 20 19:36:04 node-1 multipathd: uevent trigger error
<27>Sep 20 19:36:04 node-1 multipathd: uevent trigger error
<27>Sep 20 19:36:04 node-1 multipathd: uevent trigger error
<27>Sep 20 19:36:04 node-1 multipathd: uevent trigger error
<27>Sep 20 19:36:04 node-1 multipathd: uevent trigger error
<27>Sep 20 19:36:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:36:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:36:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:36:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:36:52 node-1 multipathd: uevent trigger error
<27>Sep 20 19:38:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:38:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:38:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:38:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:38:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:38:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:38:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:38:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:38:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:38:18 node-1 multipathd: uevent trigger error
<11>Sep 20 19:38:31 node-1 liberasurecode[28451]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:31 node-1 liberasurecode[28451]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:31 node-1 liberasurecode[28451]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:31 node-1 liberasurecode[28451]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:31 node-1 liberasurecode[28480]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:31 node-1 liberasurecode[28480]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:31 node-1 liberasurecode[28480]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:31 node-1 liberasurecode[28480]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:33 node-1 liberasurecode[28884]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:33 node-1 liberasurecode[28884]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:33 node-1 liberasurecode[28884]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:33 node-1 liberasurecode[28884]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:37 node-1 liberasurecode[29487]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:37 node-1 liberasurecode[29487]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:37 node-1 liberasurecode[29487]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:37 node-1 liberasurecode[29487]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:37 node-1 liberasurecode[29535]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:37 node-1 liberasurecode[29535]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:37 node-1 liberasurecode[29535]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:37 node-1 liberasurecode[29535]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:37 node-1 liberasurecode[29579]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:37 node-1 liberasurecode[29579]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:37 node-1 liberasurecode[29579]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:37 node-1 liberasurecode[29579]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:38 node-1 liberasurecode[29642]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:38 node-1 liberasurecode[29642]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:38 node-1 liberasurecode[29642]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:38 node-1 liberasurecode[29642]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:38 node-1 liberasurecode[29659]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:38 node-1 liberasurecode[29659]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:38 node-1 liberasurecode[29659]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:38 node-1 liberasurecode[29659]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:38 node-1 liberasurecode[29673]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:38 node-1 liberasurecode[29673]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:38 node-1 liberasurecode[29673]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:38 node-1 liberasurecode[29673]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:38 node-1 liberasurecode[29685]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:38 node-1 liberasurecode[29685]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:38 node-1 liberasurecode[29685]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:38 node-1 liberasurecode[29685]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:54 node-1 liberasurecode[32102]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:54 node-1 liberasurecode[32102]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:54 node-1 liberasurecode[32102]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:38:54 node-1 liberasurecode[32102]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 20 19:39:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:39:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:39:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:39:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:39:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:39:02 node-1 multipathd: uevent trigger error
<27>Sep 20 19:39:05 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 20 19:39:50 node-1 apache2_error [Tue Sep 20 19:39:48.459208 2016] [mpm_worker:notice] [pid 30810:tid 140348476372864] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 20 19:39:50 node-1 apache2_error [Tue Sep 20 19:39:48.844895 2016] [mpm_worker:warn] [pid 30810:tid 140348476372864] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 20 19:39:50 node-1 apache2_error [Tue Sep 20 19:39:48.849431 2016] [mpm_worker:notice] [pid 30810:tid 140348476372864] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 20 19:39:50 node-1 apache2_error [Tue Sep 20 19:39:48.849452 2016] [core:notice] [pid 30810:tid 140348476372864] AH00094: Command line: '/usr/sbin/apache2'
<11>Sep 20 19:40:01 node-1 liberasurecode[9926]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:40:01 node-1 liberasurecode[9926]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:40:01 node-1 liberasurecode[9926]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:40:01 node-1 liberasurecode[9926]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Sep 20 19:40:30 node-1 apache2_error [Tue Sep 20 19:40:25.974402 2016] [mpm_worker:notice] [pid 30810:tid 140348476372864] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 20 19:40:30 node-1 apache2_error [Tue Sep 20 19:40:26.167333 2016] [mpm_worker:warn] [pid 30810:tid 140348476372864] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 20 19:40:30 node-1 apache2_error [Tue Sep 20 19:40:26.175849 2016] [mpm_worker:notice] [pid 30810:tid 140348476372864] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 20 19:40:30 node-1 apache2_error [Tue Sep 20 19:40:26.175877 2016] [core:notice] [pid 30810:tid 140348476372864] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 20 19:40:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:40:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:40:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:40:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:40:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:40:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:40:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:40:38 node-1 multipathd: uevent trigger error
<27>Sep 20 19:40:38 node-1 multipathd: uevent trigger error
<27>Sep 20 19:40:38 node-1 multipathd: uevent trigger error
<27>Sep 20 19:40:38 node-1 multipathd: uevent trigger error
<27>Sep 20 19:40:38 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:16 node-1 multipathd: uevent trigger error
<43>Sep 20 19:41:20 node-1 apache2_error [Tue Sep 20 19:41:12.440737 2016] [mpm_worker:notice] [pid 30810:tid 140348476372864] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 20 19:41:20 node-1 apache2_error [Tue Sep 20 19:41:12.639873 2016] [mpm_worker:warn] [pid 30810:tid 140348476372864] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 20 19:41:20 node-1 apache2_error [Tue Sep 20 19:41:12.650589 2016] [mpm_worker:notice] [pid 30810:tid 140348476372864] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 20 19:41:20 node-1 apache2_error [Tue Sep 20 19:41:12.650621 2016] [core:notice] [pid 30810:tid 140348476372864] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 20 19:41:22 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:22 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:22 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:22 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:22 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:28 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:28 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:28 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:28 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:47 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:47 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:47 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:47 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:47 node-1 multipathd: uevent trigger error
<27>Sep 20 19:41:47 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:06 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 20 19:42:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:10 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:16 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:23 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 20 19:42:32 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:32 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:32 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:32 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:32 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:37 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:37 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:37 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:37 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:42 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:42 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:42 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:42 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:42 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:48 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:48 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:48 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:48 node-1 multipathd: uevent trigger error
<27>Sep 20 19:42:48 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:00 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:00 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:00 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:00 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:00 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:05 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:05 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:05 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:05 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:05 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:18 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:19 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 20 19:43:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:35 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:35 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:35 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:35 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:35 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:40 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:40 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:40 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:40 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:40 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:45 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:49 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:50 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:50 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:50 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:50 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:55 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:55 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:55 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:55 node-1 multipathd: uevent trigger error
<27>Sep 20 19:43:55 node-1 multipathd: uevent trigger error
<27>Sep 20 19:44:00 node-1 multipathd: uevent trigger error
<27>Sep 20 19:44:00 node-1 multipathd: uevent trigger error
<27>Sep 20 19:44:00 node-1 multipathd: uevent trigger error
<27>Sep 20 19:44:00 node-1 multipathd: uevent trigger error
<27>Sep 20 19:44:00 node-1 multipathd: uevent trigger error
<11>Sep 20 19:45:02 node-1 liberasurecode[14911]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:45:02 node-1 liberasurecode[14911]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:45:02 node-1 liberasurecode[14911]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 20 19:45:02 node-1 liberasurecode[14911]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 20 19:45:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:45:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:45:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:45:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:45:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:45:30 node-1 multipathd: uevent trigger error
<27>Sep 20 19:45:38 node-1 multipathd: uevent trigger error
<27>Sep 20 19:45:38 node-1 multipathd: uevent trigger error
<27>Sep 20 19:45:38 node-1 multipathd: uevent trigger error
<27>Sep 20 19:45:38 node-1 multipathd: uevent trigger error
<27>Sep 20 19:45:38 node-1 multipathd: uevent trigger error
<27>Sep 20 19:45:50 node-1 multipathd: uevent trigger error
<27>Sep 20 19:45:50 node-1 multipathd: uevent trigger error
<27>Sep 20 19:45:50 node-1 multipathd: uevent trigger error
<27>Sep 20 19:45:50 node-1 multipathd: uevent trigger error
<27>Sep 20 19:45:50 node-1 multipathd: uevent trigger error
<27>Sep 20 19:45:50 node-1 multipathd: uevent trigger error
<129>Sep 20 19:46:00 node-1 haproxy[19171]: Server neutron/node-5 is DOWN, reason: Layer4 connection 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 20 19:46:00 node-1 haproxy[19171]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 20 19:46:38 node-1 multipathd: uevent trigger error
<27>Sep 20 19:46:38 node-1 multipathd: uevent trigger error
<27>Sep 20 19:46:38 node-1 multipathd: uevent trigger error
<27>Sep 20 19:46:38 node-1 multipathd: uevent trigger error
<27>Sep 20 19:46:38 node-1 multipathd: uevent trigger error
<129>Sep 20 19:46:40 node-1 haproxy[19171]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 20 19:46:40 node-1 haproxy[19171]: proxy neutron has no server available!
<27>Sep 20 19:46:44 node-1 multipathd: uevent trigger error
<27>Sep 20 19:46:44 node-1 multipathd: uevent trigger error
<27>Sep 20 19:46:44 node-1 multipathd: uevent trigger error
<27>Sep 20 19:46:44 node-1 multipathd: uevent trigger error
<27>Sep 20 19:46:44 node-1 multipathd: uevent trigger error
<27>Sep 20 19:46:49 node-1 multipathd: uevent trigger error
<27>Sep 20 19:46:49 node-1 multipathd: uevent trigger error
<27>Sep 20 19:46:49 node-1 multipathd: uevent trigger error
<27>Sep 20 19:46:49 node-1 multipathd: uevent trigger error
<27>Sep 20 19:46:49 node-1 multipathd: uevent trigger error
<27>Sep 20 19:47:01 node-1 multipathd: uevent trigger error
<27>Sep 20 19:47:01 node-1 multipathd: uevent trigger error
<27>Sep 20 19:47:01 node-1 multipathd: uevent trigger error
<27>Sep 20 19:47:01 node-1 multipathd: uevent trigger error
<27>Sep 20 19:47:01 node-1 multipathd: uevent trigger error
