Sep 14 16:31:00 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8437" x-info="http://www.rsyslog.com"] start
Sep 14 16:31:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 14 16:31:00 node-1 rsyslogd: rsyslogd's groupid changed to 104
Sep 14 16:31:00 node-1 rsyslogd: rsyslogd's userid changed to 101
Sep 14 16:31:00 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 14 16:31:00 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 14 16:31:00 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 14 16:31:00 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 14 16:31:00 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=57fbb5e6-a74a-4362-8b7b-d3f74438c6c7 nomdmonddf nomdmonisw
Sep 14 16:31:00 node-1 kernel: [    0.000000] KERNEL supported cpus:
Sep 14 16:31:00 node-1 kernel: [    0.000000]   Intel GenuineIntel
Sep 14 16:31:00 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Sep 14 16:31:00 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Sep 14 16:31:00 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 14 16:31:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 14 16:31:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 14 16:31:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 14 16:31:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 14 16:31:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 14 16:31:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 14 16:31:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 14 16:31:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 14 16:31:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 14 16:31:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 14 16:31:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 14 16:31:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 14 16:31:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 14 16:31:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 14 16:31:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 14 16:31:00 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 14 16:31:00 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 14 16:31:00 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 14 16:31:00 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 14 16:31:00 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 14 16:31:00 node-1 kernel: [    0.000000] No AGP bridge found
Sep 14 16:31:00 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 14 16:31:00 node-1 kernel: [    0.000000] MTRR default type: write-back
Sep 14 16:31:00 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 14 16:31:00 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Sep 14 16:31:00 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 14 16:31:00 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 14 16:31:00 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 14 16:31:00 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 14 16:31:00 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 14 16:31:00 node-1 kernel: [    0.000000]   2 disabled
Sep 14 16:31:00 node-1 kernel: [    0.000000]   3 disabled
Sep 14 16:31:00 node-1 kernel: [    0.000000]   4 disabled
Sep 14 16:31:00 node-1 kernel: [    0.000000]   5 disabled
Sep 14 16:31:00 node-1 kernel: [    0.000000]   6 disabled
Sep 14 16:31:00 node-1 kernel: [    0.000000]   7 disabled
Sep 14 16:31:00 node-1 kernel: [    0.000000]   8 disabled
Sep 14 16:31:00 node-1 kernel: [    0.000000]   9 disabled
Sep 14 16:31:00 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 14 16:31:00 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 14 16:31:00 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 14 16:31:00 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 14 16:31:00 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 14 16:31:00 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Sep 14 16:31:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 14 16:31:00 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 14 16:31:00 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 14 16:31:00 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 14 16:31:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 14 16:31:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 14 16:31:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 14 16:31:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 14 16:31:00 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 14 16:31:00 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 14 16:31:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 14 16:31:00 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 14 16:31:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 14 16:31:00 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 14 16:31:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 14 16:31:00 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 14 16:31:00 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 14 16:31:00 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 14 16:31:00 node-1 kernel: [    0.000000] Zone ranges:
Sep 14 16:31:00 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] Movable zone start for each node
Sep 14 16:31:00 node-1 kernel: [    0.000000] Early memory node ranges
Sep 14 16:31:00 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 14 16:31:00 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 14 16:31:00 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 14 16:31:00 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 14 16:31:00 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 14 16:31:00 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 14 16:31:00 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 14 16:31:00 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 14 16:31:00 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 14 16:31:00 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 14 16:31:00 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 14 16:31:00 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 14 16:31:00 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 14 16:31:00 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 14 16:31:00 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 14 16:31:00 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 14 16:31:00 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 14 16:31:00 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 14 16:31:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 14 16:31:00 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 14 16:31:00 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 14 16:31:00 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 14 16:31:00 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 14 16:31:00 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 14 16:31:00 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 14 16:31:00 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 14 16:31:00 node-1 kernel: [    0.000000] Policy zone: Normal
Sep 14 16:31:00 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=57fbb5e6-a74a-4362-8b7b-d3f74438c6c7 nomdmonddf nomdmonisw
Sep 14 16:31:00 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 14 16:31:00 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 14 16:31:00 node-1 kernel: [    0.000000] Checking aperture...
Sep 14 16:31:00 node-1 kernel: [    0.000000] No AGP bridge found
Sep 14 16:31:00 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 14 16:31:00 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 14 16:31:00 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 14 16:31:00 node-1 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Sep 14 16:31:00 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 14 16:31:00 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 14 16:31:00 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 14 16:31:00 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 14 16:31:00 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 14 16:31:00 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 14 16:31:00 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 14 16:31:00 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 14 16:31:00 node-1 kernel: [    0.000000] console [tty0] enabled
Sep 14 16:31:00 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 14 16:31:00 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 14 16:31:00 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 14 16:31:00 node-1 kernel: [    0.000000] hpet clockevent registered
Sep 14 16:31:00 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 14 16:31:00 node-1 kernel: [    0.004000] tsc: Detected 3491.919 MHz processor
Sep 14 16:31:00 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.83 BogoMIPS (lpj=13967676)
Sep 14 16:31:00 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 14 16:31:00 node-1 kernel: [    0.000047] Security Framework initialized
Sep 14 16:31:00 node-1 kernel: [    0.000066] AppArmor: AppArmor initialized
Sep 14 16:31:00 node-1 kernel: [    0.000067] Yama: becoming mindful.
Sep 14 16:31:00 node-1 kernel: [    0.001463] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 14 16:31:00 node-1 kernel: [    0.006368] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 14 16:31:00 node-1 kernel: [    0.008294] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 14 16:31:00 node-1 kernel: [    0.008322] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 14 16:31:00 node-1 kernel: [    0.008610] Initializing cgroup subsys memory
Sep 14 16:31:00 node-1 kernel: [    0.008619] Initializing cgroup subsys devices
Sep 14 16:31:00 node-1 kernel: [    0.008621] Initializing cgroup subsys freezer
Sep 14 16:31:00 node-1 kernel: [    0.008622] Initializing cgroup subsys blkio
Sep 14 16:31:00 node-1 kernel: [    0.008624] Initializing cgroup subsys perf_event
Sep 14 16:31:00 node-1 kernel: [    0.008626] Initializing cgroup subsys hugetlb
Sep 14 16:31:00 node-1 kernel: [    0.008645] CPU: Physical Processor ID: 0
Sep 14 16:31:00 node-1 kernel: [    0.008647] CPU: Processor Core ID: 0
Sep 14 16:31:00 node-1 kernel: [    0.008650] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 14 16:31:00 node-1 kernel: [    0.008650] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 14 16:31:00 node-1 kernel: [    0.009344] mce: CPU supports 22 MCE banks
Sep 14 16:31:00 node-1 kernel: [    0.009371] CPU0: Thermal monitoring enabled (TM1)
Sep 14 16:31:00 node-1 kernel: [    0.009392] process: using mwait in idle threads
Sep 14 16:31:00 node-1 kernel: [    0.009395] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 14 16:31:00 node-1 kernel: [    0.009395] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 14 16:31:00 node-1 kernel: [    0.009395] tlb_flushall_shift: 6
Sep 14 16:31:00 node-1 kernel: [    0.009484] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 14 16:31:00 node-1 kernel: [    0.010210] ACPI: Core revision 20131115
Sep 14 16:31:00 node-1 kernel: [    0.022895] ACPI: All ACPI Tables successfully acquired
Sep 14 16:31:00 node-1 kernel: [    0.023055] ftrace: allocating 28617 entries in 112 pages
Sep 14 16:31:00 node-1 kernel: [    0.032018] dmar: Host address width 46
Sep 14 16:31:00 node-1 kernel: [    0.032020] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 14 16:31:00 node-1 kernel: [    0.032026] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 14 16:31:00 node-1 kernel: [    0.032027] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 14 16:31:00 node-1 kernel: [    0.032031] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 14 16:31:00 node-1 kernel: [    0.032033] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 14 16:31:00 node-1 kernel: [    0.032034] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 14 16:31:00 node-1 kernel: [    0.032035] dmar: ATSR flags: 0x0
Sep 14 16:31:00 node-1 kernel: [    0.032036] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 14 16:31:00 node-1 kernel: [    0.032038] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 14 16:31:00 node-1 kernel: [    0.032153] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 14 16:31:00 node-1 kernel: [    0.032154] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 14 16:31:00 node-1 kernel: [    0.032155] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 14 16:31:00 node-1 kernel: [    0.032157] HPET id 0 under DRHD base 0xc7ffc000
Sep 14 16:31:00 node-1 kernel: [    0.032158] Your BIOS is broken and requested that x2apic be disabled.
Sep 14 16:31:00 node-1 kernel: [    0.032158] This will slightly decrease performance.
Sep 14 16:31:00 node-1 kernel: [    0.032158] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 14 16:31:00 node-1 kernel: [    0.032592] Enabled IRQ remapping in xapic mode
Sep 14 16:31:00 node-1 kernel: [    0.032593] x2apic not enabled, IRQ remapping is in xapic mode
Sep 14 16:31:00 node-1 kernel: [    0.032597] Switched APIC routing to physical flat.
Sep 14 16:31:00 node-1 kernel: [    0.033222] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 14 16:31:00 node-1 kernel: [    0.072872] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 14 16:31:00 node-1 kernel: [    0.072877] TSC deadline timer enabled
Sep 14 16:31:00 node-1 kernel: [    0.072884] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 14 16:31:00 node-1 kernel: [    0.072891] ... version:                3
Sep 14 16:31:00 node-1 kernel: [    0.072892] ... bit width:              48
Sep 14 16:31:00 node-1 kernel: [    0.072893] ... generic registers:      4
Sep 14 16:31:00 node-1 kernel: [    0.072894] ... value mask:             0000ffffffffffff
Sep 14 16:31:00 node-1 kernel: [    0.072895] ... max period:             0000ffffffffffff
Sep 14 16:31:00 node-1 kernel: [    0.072896] ... fixed-purpose events:   3
Sep 14 16:31:00 node-1 kernel: [    0.072897] ... event mask:             000000070000000f
Sep 14 16:31:00 node-1 kernel: [    0.074290] x86: Booting SMP configuration:
Sep 14 16:31:00 node-1 kernel: [    0.088393] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 14 16:31:00 node-1 kernel: [    0.074292] .... node  #0, CPUs:        #1  #2  #3
Sep 14 16:31:00 node-1 kernel: [    0.116305] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 14 16:31:00 node-1 kernel: [    0.270447] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 14 16:31:00 node-1 kernel: [    0.326067] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 14 16:31:00 node-1 kernel: [    0.382522] x86: Booted up 2 nodes, 16 CPUs
Sep 14 16:31:00 node-1 kernel: [    0.382526] smpboot: Total of 16 processors activated (111754.00 BogoMIPS)
Sep 14 16:31:00 node-1 kernel: [    0.405289] devtmpfs: initialized
Sep 14 16:31:00 node-1 kernel: [    0.408363] EVM: security.selinux
Sep 14 16:31:00 node-1 kernel: [    0.408365] EVM: security.SMACK64
Sep 14 16:31:00 node-1 kernel: [    0.408366] EVM: security.ima
Sep 14 16:31:00 node-1 kernel: [    0.408367] EVM: security.capability
Sep 14 16:31:00 node-1 kernel: [    0.408415] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 14 16:31:00 node-1 kernel: [    0.409084] pinctrl core: initialized pinctrl subsystem
Sep 14 16:31:00 node-1 kernel: [    0.409145] regulator-dummy: no parameters
Sep 14 16:31:00 node-1 kernel: [    0.409176] RTC time: 16:30:23, date: 09/14/16
Sep 14 16:31:00 node-1 kernel: [    0.409210] NET: Registered protocol family 16
Sep 14 16:31:00 node-1 kernel: [    0.409292] cpuidle: using governor ladder
Sep 14 16:31:00 node-1 kernel: [    0.409293] cpuidle: using governor menu
Sep 14 16:31:00 node-1 kernel: [    0.409328] ACPI: bus type PCI registered
Sep 14 16:31:00 node-1 kernel: [    0.409330] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 14 16:31:00 node-1 kernel: [    0.409375] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 14 16:31:00 node-1 kernel: [    0.409378] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 14 16:31:00 node-1 kernel: [    0.423104] PCI: Using configuration type 1 for base access
Sep 14 16:31:00 node-1 kernel: [    0.424104] bio: create slab <bio-0> at 0
Sep 14 16:31:00 node-1 kernel: [    0.424375] ACPI: Added _OSI(Module Device)
Sep 14 16:31:00 node-1 kernel: [    0.424377] ACPI: Added _OSI(Processor Device)
Sep 14 16:31:00 node-1 kernel: [    0.424378] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 14 16:31:00 node-1 kernel: [    0.424379] ACPI: Added _OSI(Processor Aggregator Device)
Sep 14 16:31:00 node-1 kernel: [    0.437052] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 14 16:31:00 node-1 kernel: [    0.448627] ACPI: Interpreter enabled
Sep 14 16:31:00 node-1 kernel: [    0.448633] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 14 16:31:00 node-1 kernel: [    0.448637] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 14 16:31:00 node-1 kernel: [    0.448639] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 14 16:31:00 node-1 kernel: [    0.448646] ACPI: (supports S0 S4 S5)
Sep 14 16:31:00 node-1 kernel: [    0.448648] ACPI: Using IOAPIC for interrupt routing
Sep 14 16:31:00 node-1 kernel: [    0.448689] HEST: Table parsing has been initialized.
Sep 14 16:31:00 node-1 kernel: [    0.448692] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 14 16:31:00 node-1 kernel: [    0.449245] ACPI: No dock devices found.
Sep 14 16:31:00 node-1 kernel: [    0.460909] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 14 16:31:00 node-1 kernel: [    0.460914] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 14 16:31:00 node-1 kernel: [    0.460918] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 14 16:31:00 node-1 kernel: [    0.460949] PCI host bridge to bus 0000:ff
Sep 14 16:31:00 node-1 kernel: [    0.460951] pci_bus 0000:ff: root bus resource [bus ff]
Sep 14 16:31:00 node-1 kernel: [    0.460959] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.460997] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 14 16:31:00 node-1 kernel: [    0.461027] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461062] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461091] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 14 16:31:00 node-1 kernel: [    0.461119] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 14 16:31:00 node-1 kernel: [    0.461149] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461177] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461206] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461234] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461260] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461285] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461313] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461338] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461364] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461390] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461418] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461445] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461471] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 14 16:31:00 node-1 kernel: [    0.461499] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461524] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 14 16:31:00 node-1 kernel: [    0.461549] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461575] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461604] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 14 16:31:00 node-1 kernel: [    0.461638] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461669] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461698] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461729] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461759] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461790] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461820] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461849] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461880] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461910] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461941] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.461971] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462004] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462035] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462062] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462094] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462126] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462166] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462201] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462232] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462260] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462290] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462321] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462351] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462383] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462416] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462448] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462477] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462505] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462534] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462563] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462594] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462626] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462683] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 14 16:31:00 node-1 kernel: [    0.462685] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 14 16:31:00 node-1 kernel: [    0.462688] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 14 16:31:00 node-1 kernel: [    0.462706] PCI host bridge to bus 0000:7f
Sep 14 16:31:00 node-1 kernel: [    0.462708] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 14 16:31:00 node-1 kernel: [    0.462713] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462740] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 14 16:31:00 node-1 kernel: [    0.462768] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462797] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462819] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 14 16:31:00 node-1 kernel: [    0.462844] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 14 16:31:00 node-1 kernel: [    0.462873] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462899] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462922] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462947] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462972] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.462996] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463022] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463045] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463071] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463096] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463118] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463141] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463163] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 14 16:31:00 node-1 kernel: [    0.463187] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463209] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 14 16:31:00 node-1 kernel: [    0.463230] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463253] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463279] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 14 16:31:00 node-1 kernel: [    0.463311] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463337] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463364] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463392] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463417] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463445] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463471] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463498] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463523] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463551] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463579] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463606] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463635] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463659] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463684] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463712] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463737] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463764] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463793] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463821] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463846] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463870] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463896] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463922] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463949] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.463976] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.464006] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.464031] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.464054] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.464080] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.464105] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.464134] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.464160] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.465401] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 14 16:31:00 node-1 kernel: [    0.465404] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 14 16:31:00 node-1 kernel: [    0.466529] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 14 16:31:00 node-1 kernel: [    0.467044] PCI host bridge to bus 0000:00
Sep 14 16:31:00 node-1 kernel: [    0.467047] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 14 16:31:00 node-1 kernel: [    0.467049] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 14 16:31:00 node-1 kernel: [    0.467050] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 14 16:31:00 node-1 kernel: [    0.467051] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 14 16:31:00 node-1 kernel: [    0.467053] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 14 16:31:00 node-1 kernel: [    0.467054] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 14 16:31:00 node-1 kernel: [    0.467055] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 14 16:31:00 node-1 kernel: [    0.467061] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 14 16:31:00 node-1 kernel: [    0.467144] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 14 16:31:00 node-1 kernel: [    0.467175] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 14 16:31:00 node-1 kernel: [    0.467220] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 14 16:31:00 node-1 kernel: [    0.467239] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 14 16:31:00 node-1 kernel: [    0.467269] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 14 16:31:00 node-1 kernel: [    0.467309] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 14 16:31:00 node-1 kernel: [    0.467328] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 14 16:31:00 node-1 kernel: [    0.467358] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 14 16:31:00 node-1 kernel: [    0.467398] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 14 16:31:00 node-1 kernel: [    0.467415] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.467486] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.467564] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.467639] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 14 16:31:00 node-1 kernel: [    0.467644] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 14 16:31:00 node-1 kernel: [    0.467729] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 14 16:31:00 node-1 kernel: [    0.467876] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 14 16:31:00 node-1 kernel: [    0.467894] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 14 16:31:00 node-1 kernel: [    0.467972] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 14 16:31:00 node-1 kernel: [    0.468025] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 14 16:31:00 node-1 kernel: [    0.468047] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 14 16:31:00 node-1 kernel: [    0.468103] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 14 16:31:00 node-1 kernel: [    0.468146] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 14 16:31:00 node-1 kernel: [    0.468174] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 14 16:31:00 node-1 kernel: [    0.468230] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 14 16:31:00 node-1 kernel: [    0.468273] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 14 16:31:00 node-1 kernel: [    0.468297] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 14 16:31:00 node-1 kernel: [    0.468314] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 14 16:31:00 node-1 kernel: [    0.468392] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 14 16:31:00 node-1 kernel: [    0.468442] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 14 16:31:00 node-1 kernel: [    0.468468] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 14 16:31:00 node-1 kernel: [    0.468715] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 14 16:31:00 node-1 kernel: [    0.468721] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 14 16:31:00 node-1 kernel: [    0.468727] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 14 16:31:00 node-1 kernel: [    0.468733] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 14 16:31:00 node-1 kernel: [    0.468740] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 14 16:31:00 node-1 kernel: [    0.468771] pci 0000:01:00.0: supports D1 D2
Sep 14 16:31:00 node-1 kernel: [    0.474875] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 14 16:31:00 node-1 kernel: [    0.474881] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 14 16:31:00 node-1 kernel: [    0.474886] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 14 16:31:00 node-1 kernel: [    0.475078] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 14 16:31:00 node-1 kernel: [    0.475112] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 14 16:31:00 node-1 kernel: [    0.482872] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 14 16:31:00 node-1 kernel: [    0.482878] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 14 16:31:00 node-1 kernel: [    0.482882] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 14 16:31:00 node-1 kernel: [    0.482967] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 14 16:31:00 node-1 kernel: [    0.483050] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 14 16:31:00 node-1 kernel: [    0.483129] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 14 16:31:00 node-1 kernel: [    0.483174] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 14 16:31:00 node-1 kernel: [    0.483177] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 14 16:31:00 node-1 kernel: [    0.483179] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 14 16:31:00 node-1 kernel: [    0.483231] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 14 16:31:00 node-1 kernel: [    0.483354] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 14 16:31:00 node-1 kernel: [    0.483426] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 14 16:31:00 node-1 kernel: [    0.483428] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 14 16:31:00 node-1 kernel: [    0.483430] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 14 16:31:00 node-1 kernel: [    0.483480] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 14 16:31:00 node-1 kernel: [    0.483600] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 14 16:31:00 node-1 kernel: [    0.483641] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 14 16:31:00 node-1 kernel: [    0.483761] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 14 16:31:00 node-1 kernel: [    0.483798] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 14 16:31:00 node-1 kernel: [    0.483918] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 14 16:31:00 node-1 kernel: [    0.483955] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 14 16:31:00 node-1 kernel: [    0.484076] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 14 16:31:00 node-1 kernel: [    0.484117] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 14 16:31:00 node-1 kernel: [    0.484120] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 14 16:31:00 node-1 kernel: [    0.484122] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 14 16:31:00 node-1 kernel: [    0.484181] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 14 16:31:00 node-1 kernel: [    0.484244] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 14 16:31:00 node-1 kernel: [    0.484296] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 14 16:31:00 node-1 kernel: [    0.484338] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 14 16:31:00 node-1 kernel: [    0.484445] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 14 16:31:00 node-1 kernel: [    0.484552] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 14 16:31:00 node-1 kernel: [    0.484554] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 14 16:31:00 node-1 kernel: [    0.484556] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 14 16:31:00 node-1 kernel: [    0.484612] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 14 16:31:00 node-1 kernel: [    0.484670] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 14 16:31:00 node-1 kernel: [    0.484718] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 14 16:31:00 node-1 kernel: [    0.484930] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 14 16:31:00 node-1 kernel: [    0.484933] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 14 16:31:00 node-1 kernel: [    0.484996] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 14 16:31:00 node-1 kernel: [    0.485049] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 14 16:31:00 node-1 kernel: [    0.485097] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 14 16:31:00 node-1 kernel: [    0.485308] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 14 16:31:00 node-1 kernel: [    0.485312] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 14 16:31:00 node-1 kernel: [    0.485370] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 14 16:31:00 node-1 kernel: [    0.485463] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 14 16:31:00 node-1 kernel: [    0.485516] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 14 16:31:00 node-1 kernel: [    0.485745] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 14 16:31:00 node-1 kernel: [    0.485749] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 14 16:31:00 node-1 kernel: [    0.485923] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 14 16:31:00 node-1 kernel: [    0.485961] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 14 16:31:00 node-1 kernel: [    0.486035] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 14 16:31:00 node-1 kernel: [    0.486054] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 14 16:31:00 node-1 kernel: [    0.486067] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 14 16:31:00 node-1 kernel: [    0.486080] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 14 16:31:00 node-1 kernel: [    0.486131] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 14 16:31:00 node-1 kernel: [    0.490879] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 14 16:31:00 node-1 kernel: [    0.490888] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 14 16:31:00 node-1 kernel: [    0.490942] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 14 16:31:00 node-1 kernel: [    0.491433] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 14 16:31:00 node-1 kernel: [    0.491435] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 14 16:31:00 node-1 kernel: [    0.491559] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 14 16:31:00 node-1 kernel: [    0.491664] PCI host bridge to bus 0000:80
Sep 14 16:31:00 node-1 kernel: [    0.491666] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 14 16:31:00 node-1 kernel: [    0.491668] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 14 16:31:00 node-1 kernel: [    0.491669] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 14 16:31:00 node-1 kernel: [    0.491677] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.491740] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.491808] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 14 16:31:00 node-1 kernel: [    0.491870] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 14 16:31:00 node-1 kernel: [    0.491875] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 14 16:31:00 node-1 kernel: [    0.491947] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 14 16:31:00 node-1 kernel: [    0.492246] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 14 16:31:00 node-1 kernel: [    0.492277] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 14 16:31:00 node-1 kernel: [    0.492307] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 14 16:31:00 node-1 kernel: [    0.492336] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 14 16:31:00 node-1 kernel: [    0.492365] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 14 16:31:00 node-1 kernel: [    0.492396] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 14 16:31:00 node-1 kernel: [    0.492425] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 14 16:31:00 node-1 kernel: [    0.492455] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 14 16:31:00 node-1 kernel: [    0.492541] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 14 16:31:00 node-1 kernel: [    0.492545] ACPI: \_SB_.UNC1: notify handler is installed
Sep 14 16:31:00 node-1 kernel: [    0.492546] ACPI: \_SB_.UNC0: notify handler is installed
Sep 14 16:31:00 node-1 kernel: [    0.492561] ACPI: \_SB_.PCI0: notify handler is installed
Sep 14 16:31:00 node-1 kernel: [    0.492614] ACPI: \_SB_.PCI1: notify handler is installed
Sep 14 16:31:00 node-1 kernel: [    0.492694] Found 4 acpi root devices
Sep 14 16:31:00 node-1 kernel: [    0.492802] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 14 16:31:00 node-1 kernel: [    0.492804] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 14 16:31:00 node-1 kernel: [    0.492806] vgaarb: loaded
Sep 14 16:31:00 node-1 kernel: [    0.492807] vgaarb: bridge control possible 0000:0c:00.0
Sep 14 16:31:00 node-1 kernel: [    0.492930] SCSI subsystem initialized
Sep 14 16:31:00 node-1 kernel: [    0.492998] libata version 3.00 loaded.
Sep 14 16:31:00 node-1 kernel: [    0.493013] ACPI: bus type USB registered
Sep 14 16:31:00 node-1 kernel: [    0.493024] usbcore: registered new interface driver usbfs
Sep 14 16:31:00 node-1 kernel: [    0.493029] usbcore: registered new interface driver hub
Sep 14 16:31:00 node-1 kernel: [    0.493050] usbcore: registered new device driver usb
Sep 14 16:31:00 node-1 kernel: [    0.493207] PCI: Using ACPI for IRQ routing
Sep 14 16:31:00 node-1 kernel: [    0.496818] PCI: pci_cache_line_size set to 64 bytes
Sep 14 16:31:00 node-1 kernel: [    0.497024] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 14 16:31:00 node-1 kernel: [    0.497026] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 14 16:31:00 node-1 kernel: [    0.497026] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 14 16:31:00 node-1 kernel: [    0.497091] NetLabel: Initializing
Sep 14 16:31:00 node-1 kernel: [    0.497093] NetLabel:  domain hash size = 128
Sep 14 16:31:00 node-1 kernel: [    0.497093] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 14 16:31:00 node-1 kernel: [    0.497103] NetLabel:  unlabeled traffic allowed by default
Sep 14 16:31:00 node-1 kernel: [    0.497158] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 14 16:31:00 node-1 kernel: [    0.497163] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 14 16:31:00 node-1 kernel: [    0.499233] Switched to clocksource hpet
Sep 14 16:31:00 node-1 kernel: [    0.503757] AppArmor: AppArmor Filesystem Enabled
Sep 14 16:31:00 node-1 kernel: [    0.503795] pnp: PnP ACPI init
Sep 14 16:31:00 node-1 kernel: [    0.503807] ACPI: bus type PNP registered
Sep 14 16:31:00 node-1 kernel: [    0.503987] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 14 16:31:00 node-1 kernel: [    0.503998] pnp 00:01: [dma 4]
Sep 14 16:31:00 node-1 kernel: [    0.504017] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 14 16:31:00 node-1 kernel: [    0.504051] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 14 16:31:00 node-1 kernel: [    0.504076] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 14 16:31:00 node-1 kernel: [    0.504097] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 14 16:31:00 node-1 kernel: [    0.504144] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 14 16:31:00 node-1 kernel: [    0.504256] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 14 16:31:00 node-1 kernel: [    0.504258] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 14 16:31:00 node-1 kernel: [    0.504260] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 14 16:31:00 node-1 kernel: [    0.504261] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 14 16:31:00 node-1 kernel: [    0.504263] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 14 16:31:00 node-1 kernel: [    0.504264] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 14 16:31:00 node-1 kernel: [    0.504268] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 14 16:31:00 node-1 kernel: [    0.504269] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 14 16:31:00 node-1 kernel: [    0.504271] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 14 16:31:00 node-1 kernel: [    0.504272] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 14 16:31:00 node-1 kernel: [    0.504274] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 14 16:31:00 node-1 kernel: [    0.504275] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 14 16:31:00 node-1 kernel: [    0.504277] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 14 16:31:00 node-1 kernel: [    0.504279] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 14 16:31:00 node-1 kernel: [    0.504381] pnp 00:07: [dma 0 disabled]
Sep 14 16:31:00 node-1 kernel: [    0.504414] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 14 16:31:00 node-1 kernel: [    0.504495] pnp 00:08: [dma 0 disabled]
Sep 14 16:31:00 node-1 kernel: [    0.504531] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 14 16:31:00 node-1 kernel: [    0.504589] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 14 16:31:00 node-1 kernel: [    0.505036] pnp: PnP ACPI: found 10 devices
Sep 14 16:31:00 node-1 kernel: [    0.505038] ACPI: bus type PNP unregistered
Sep 14 16:31:00 node-1 kernel: [    0.511067] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 14 16:31:00 node-1 kernel: [    0.511071] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 14 16:31:00 node-1 kernel: [    0.511073] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 14 16:31:00 node-1 kernel: [    0.511079] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 14 16:31:00 node-1 kernel: [    0.511081] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 14 16:31:00 node-1 kernel: [    0.511095] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 14 16:31:00 node-1 kernel: [    0.511125] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 14 16:31:00 node-1 kernel: [    0.511139] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 14 16:31:00 node-1 kernel: [    0.511169] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 14 16:31:00 node-1 kernel: [    0.511183] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 14 16:31:00 node-1 kernel: [    0.511216] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 14 16:31:00 node-1 kernel: [    0.511231] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 14 16:31:00 node-1 kernel: [    0.511260] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 14 16:31:00 node-1 kernel: [    0.511262] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 14 16:31:00 node-1 kernel: [    0.511277] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 14 16:31:00 node-1 kernel: [    0.511306] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 14 16:31:00 node-1 kernel: [    0.511308] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 14 16:31:00 node-1 kernel: [    0.511323] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 14 16:31:00 node-1 kernel: [    0.511355] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 14 16:31:00 node-1 kernel: [    0.511356] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 14 16:31:00 node-1 kernel: [    0.511359] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 14 16:31:00 node-1 kernel: [    0.511364] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 14 16:31:00 node-1 kernel: [    0.511366] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 14 16:31:00 node-1 kernel: [    0.511369] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 14 16:31:00 node-1 kernel: [    0.511373] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 14 16:31:00 node-1 kernel: [    0.511379] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 14 16:31:00 node-1 kernel: [    0.511388] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 14 16:31:00 node-1 kernel: [    0.511391] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 14 16:31:00 node-1 kernel: [    0.511399] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 14 16:31:00 node-1 kernel: [    0.511400] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 14 16:31:00 node-1 kernel: [    0.511401] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 14 16:31:00 node-1 kernel: [    0.511402] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 14 16:31:00 node-1 kernel: [    0.511403] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 14 16:31:00 node-1 kernel: [    0.511404] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 14 16:31:00 node-1 kernel: [    0.511405] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 14 16:31:00 node-1 kernel: [    0.511405] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 14 16:31:00 node-1 kernel: [    0.511407] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 14 16:31:00 node-1 kernel: [    0.511407] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 14 16:31:00 node-1 kernel: [    0.511409] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 14 16:31:00 node-1 kernel: [    0.511409] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 14 16:31:00 node-1 kernel: [    0.511410] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 14 16:31:00 node-1 kernel: [    0.511411] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 14 16:31:00 node-1 kernel: [    0.511412] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 14 16:31:00 node-1 kernel: [    0.511413] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 14 16:31:00 node-1 kernel: [    0.511414] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 14 16:31:00 node-1 kernel: [    0.511415] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 14 16:31:00 node-1 kernel: [    0.511416] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 14 16:31:00 node-1 kernel: [    0.511417] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 14 16:31:00 node-1 kernel: [    0.511419] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 14 16:31:00 node-1 kernel: [    0.511420] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 14 16:31:00 node-1 kernel: [    0.511422] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 14 16:31:00 node-1 kernel: [    0.511423] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 14 16:31:00 node-1 kernel: [    0.511463] NET: Registered protocol family 2
Sep 14 16:31:00 node-1 kernel: [    0.511761] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 14 16:31:00 node-1 kernel: [    0.512127] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 14 16:31:00 node-1 kernel: [    0.512301] TCP: Hash tables configured (established 262144 bind 65536)
Sep 14 16:31:00 node-1 kernel: [    0.512343] TCP: reno registered
Sep 14 16:31:00 node-1 kernel: [    0.512373] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 14 16:31:00 node-1 kernel: [    0.512481] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 14 16:31:00 node-1 kernel: [    0.512643] NET: Registered protocol family 1
Sep 14 16:31:00 node-1 kernel: [    0.551325] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 14 16:31:00 node-1 kernel: [    0.551341] PCI: CLS 64 bytes, default 64
Sep 14 16:31:00 node-1 kernel: [    0.551427] Trying to unpack rootfs image as initramfs...
Sep 14 16:31:00 node-1 kernel: [    0.774090] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Sep 14 16:31:00 node-1 kernel: [    0.774139] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 14 16:31:00 node-1 kernel: [    0.774142] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 14 16:31:00 node-1 kernel: [    0.774558] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 16:31:00 node-1 kernel: [    0.774567] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 16:31:00 node-1 kernel: [    0.774576] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 16:31:00 node-1 kernel: [    0.774583] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 16:31:00 node-1 kernel: [    0.774592] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 16:31:00 node-1 kernel: [    0.774599] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 16:31:00 node-1 kernel: [    0.774606] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 16:31:00 node-1 kernel: [    0.774613] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 16:31:00 node-1 kernel: [    0.774621] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 16:31:00 node-1 kernel: [    0.774628] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 16:31:00 node-1 kernel: [    0.774639] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 16:31:00 node-1 kernel: [    0.774646] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 16:31:00 node-1 kernel: [    0.774671] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 16:31:00 node-1 kernel: [    0.774677] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 16:31:00 node-1 kernel: [    0.774683] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 16:31:00 node-1 kernel: [    0.774687] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 16:31:00 node-1 kernel: [    0.774732] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 14 16:31:00 node-1 kernel: [    0.774734] Scanning for low memory corruption every 60 seconds
Sep 14 16:31:00 node-1 kernel: [    0.775055] Initialise system trusted keyring
Sep 14 16:31:00 node-1 kernel: [    0.775105] audit: initializing netlink socket (disabled)
Sep 14 16:31:00 node-1 kernel: [    0.775116] type=2000 audit(1473870623.732:1): initialized
Sep 14 16:31:00 node-1 kernel: [    0.792973] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 14 16:31:00 node-1 kernel: [    0.794760] zbud: loaded
Sep 14 16:31:00 node-1 kernel: [    0.794886] VFS: Disk quotas dquot_6.5.2
Sep 14 16:31:00 node-1 kernel: [    0.794924] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 14 16:31:00 node-1 kernel: [    0.795295] fuse init (API version 7.22)
Sep 14 16:31:00 node-1 kernel: [    0.795347] msgmni has been set to 32768
Sep 14 16:31:00 node-1 kernel: [    0.795392] Key type big_key registered
Sep 14 16:31:00 node-1 kernel: [    0.795960] Key type asymmetric registered
Sep 14 16:31:00 node-1 kernel: [    0.795964] Asymmetric key parser 'x509' registered
Sep 14 16:31:00 node-1 kernel: [    0.796013] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 14 16:31:00 node-1 kernel: [    0.796099] io scheduler noop registered
Sep 14 16:31:00 node-1 kernel: [    0.796103] io scheduler deadline registered (default)
Sep 14 16:31:00 node-1 kernel: [    0.796144] io scheduler cfq registered
Sep 14 16:31:00 node-1 kernel: [    0.796765] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    0.796893] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    0.797021] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    0.797132] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    0.797246] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    0.797335] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    0.797774] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 14 16:31:00 node-1 kernel: [    0.797803] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 14 16:31:00 node-1 kernel: [    0.797819] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 14 16:31:00 node-1 kernel: [    0.797831] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797834] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797836] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 14 16:31:00 node-1 kernel: [    0.797842] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797843] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797844] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797846] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797848] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797849] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797851] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797852] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797853] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797855] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797857] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797858] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797860] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 14 16:31:00 node-1 kernel: [    0.797871] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797874] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 14 16:31:00 node-1 kernel: [    0.797885] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797888] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 14 16:31:00 node-1 kernel: [    0.797899] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797900] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 14 16:31:00 node-1 kernel: [    0.797903] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 14 16:31:00 node-1 kernel: [    0.797932] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 14 16:31:00 node-1 kernel: [    0.797937] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 14 16:31:00 node-1 kernel: [    0.797941] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 14 16:31:00 node-1 kernel: [    0.797950] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 14 16:31:00 node-1 kernel: [    0.797986] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 14 16:31:00 node-1 kernel: [    0.797987] vesafb: scrolling: redraw
Sep 14 16:31:00 node-1 kernel: [    0.797989] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 14 16:31:00 node-1 kernel: [    0.818620] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 14 16:31:00 node-1 kernel: [    0.827113] Console: switching to colour frame buffer device 80x30
Sep 14 16:31:00 node-1 kernel: [    0.835793] fb0: VESA VGA frame buffer device
Sep 14 16:31:00 node-1 kernel: [    0.835987] intel_idle: MWAIT substates: 0x2120
Sep 14 16:31:00 node-1 kernel: [    0.835988] intel_idle: v0.4 model 0x3F
Sep 14 16:31:00 node-1 kernel: [    0.835989] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 14 16:31:00 node-1 kernel: [    0.836228] ipmi message handler version 39.2
Sep 14 16:31:00 node-1 kernel: [    0.836492] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 14 16:31:00 node-1 kernel: [    0.836924] ACPI: AC Adapter [P111] (on-line)
Sep 14 16:31:00 node-1 kernel: [    0.842174] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 14 16:31:00 node-1 kernel: [    0.853187] ACPI: Power Button [PWRB]
Sep 14 16:31:00 node-1 kernel: [    0.858947] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 14 16:31:00 node-1 kernel: [    0.870555] ACPI: Power Button [PWRF]
Sep 14 16:31:00 node-1 kernel: [    0.896776] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 14 16:31:00 node-1 kernel: [    0.908425] pstore: Registered erst as persistent store backend
Sep 14 16:31:00 node-1 kernel: [    0.914591] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 14 16:31:00 node-1 kernel: [    0.926597] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 14 16:31:00 node-1 kernel: [    0.953447] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 14 16:31:00 node-1 kernel: [    0.986729] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 14 16:31:00 node-1 kernel: [    1.000854] Linux agpgart interface v0.103
Sep 14 16:31:00 node-1 kernel: [    1.008521] brd: module loaded
Sep 14 16:31:00 node-1 kernel: [    1.015530] loop: module loaded
Sep 14 16:31:00 node-1 kernel: [    1.022224] libphy: Fixed MDIO Bus: probed
Sep 14 16:31:00 node-1 kernel: [    1.028664] tun: Universal TUN/TAP device driver, 1.6
Sep 14 16:31:00 node-1 kernel: [    1.035110] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 14 16:31:00 node-1 kernel: [    1.041615] PPP generic driver version 2.4.2
Sep 14 16:31:00 node-1 kernel: [    1.047987] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 14 16:31:00 node-1 kernel: [    1.054429] ehci-pci: EHCI PCI platform driver
Sep 14 16:31:00 node-1 kernel: [    1.060932] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 14 16:31:00 node-1 kernel: [    1.067315] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 14 16:31:00 node-1 kernel: [    1.079792] ehci-pci 0000:00:1a.0: debug port 2
Sep 14 16:31:00 node-1 kernel: [    1.089960] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 14 16:31:00 node-1 kernel: [    1.089978] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 14 16:31:00 node-1 kernel: [    1.106709] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 14 16:31:00 node-1 kernel: [    1.112766] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 14 16:31:00 node-1 kernel: [    1.118927] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 14 16:31:00 node-1 kernel: [    1.130798] usb usb1: Product: EHCI Host Controller
Sep 14 16:31:00 node-1 kernel: [    1.136810] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 14 16:31:00 node-1 kernel: [    1.142837] usb usb1: SerialNumber: 0000:00:1a.0
Sep 14 16:31:00 node-1 kernel: [    1.148803] hub 1-0:1.0: USB hub found
Sep 14 16:31:00 node-1 kernel: [    1.154566] hub 1-0:1.0: 2 ports detected
Sep 14 16:31:00 node-1 kernel: [    1.160334] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 14 16:31:00 node-1 kernel: [    1.165891] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 14 16:31:00 node-1 kernel: [    1.176754] ehci-pci 0000:00:1d.0: debug port 2
Sep 14 16:31:00 node-1 kernel: [    1.186034] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 14 16:31:00 node-1 kernel: [    1.186037] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 14 16:31:00 node-1 kernel: [    1.202627] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 14 16:31:00 node-1 kernel: [    1.207819] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 14 16:31:00 node-1 kernel: [    1.213104] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 14 16:31:00 node-1 kernel: [    1.223667] usb usb2: Product: EHCI Host Controller
Sep 14 16:31:00 node-1 kernel: [    1.229127] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 14 16:31:00 node-1 kernel: [    1.234675] usb usb2: SerialNumber: 0000:00:1d.0
Sep 14 16:31:00 node-1 kernel: [    1.240210] hub 2-0:1.0: USB hub found
Sep 14 16:31:00 node-1 kernel: [    1.245568] hub 2-0:1.0: 2 ports detected
Sep 14 16:31:00 node-1 kernel: [    1.250871] ehci-platform: EHCI generic platform driver
Sep 14 16:31:00 node-1 kernel: [    1.256110] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 14 16:31:00 node-1 kernel: [    1.261417] ohci-pci: OHCI PCI platform driver
Sep 14 16:31:00 node-1 kernel: [    1.266721] ohci-platform: OHCI generic platform driver
Sep 14 16:31:00 node-1 kernel: [    1.271917] uhci_hcd: USB Universal Host Controller Interface driver
Sep 14 16:31:00 node-1 kernel: [    1.277252] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 14 16:31:00 node-1 kernel: [    1.470408] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 14 16:31:00 node-1 kernel: [    1.630618] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 14 16:31:00 node-1 kernel: [    1.636127] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 14 16:31:00 node-1 kernel: [    1.641885] hub 1-1:1.0: USB hub found
Sep 14 16:31:00 node-1 kernel: [    1.647354] hub 1-1:1.0: 6 ports detected
Sep 14 16:31:00 node-1 kernel: [    1.762151] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 14 16:31:00 node-1 kernel: [    2.030278] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 14 16:31:00 node-1 kernel: [    2.035698] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 14 16:31:00 node-1 kernel: [    2.041292] hub 2-1:1.0: USB hub found
Sep 14 16:31:00 node-1 kernel: [    2.046889] hub 2-1:1.0: 8 ports detected
Sep 14 16:31:00 node-1 kernel: [    2.317900] i8042: No controller found
Sep 14 16:31:00 node-1 kernel: [    2.321742] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 14 16:31:00 node-1 kernel: [    2.328653] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 14 16:31:00 node-1 kernel: [    2.330254] mousedev: PS/2 mouse device common for all mice
Sep 14 16:31:00 node-1 kernel: [    2.331987] rtc_cmos 00:02: RTC can wake from S4
Sep 14 16:31:00 node-1 kernel: [    2.333401] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 14 16:31:00 node-1 kernel: [    2.334204] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 14 16:31:00 node-1 kernel: [    2.335206] device-mapper: uevent: version 1.0.3
Sep 14 16:31:00 node-1 kernel: [    2.336374] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 14 16:31:00 node-1 kernel: [    2.336541] ledtrig-cpu: registered to indicate activity on CPUs
Sep 14 16:31:00 node-1 kernel: [    2.338577] TCP: cubic registered
Sep 14 16:31:00 node-1 kernel: [    2.339644] NET: Registered protocol family 10
Sep 14 16:31:00 node-1 kernel: [    2.342486] NET: Registered protocol family 17
Sep 14 16:31:00 node-1 kernel: [    2.342622] Key type dns_resolver registered
Sep 14 16:31:00 node-1 kernel: [    2.349156] Loading compiled-in X.509 certificates
Sep 14 16:31:00 node-1 kernel: [    2.351079] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 14 16:31:00 node-1 kernel: [    2.351385] registered taskstats version 1
Sep 14 16:31:00 node-1 kernel: [    2.391124] Key type trusted registered
Sep 14 16:31:00 node-1 kernel: [    2.415022] Key type encrypted registered
Sep 14 16:31:00 node-1 kernel: [    2.415024] AppArmor: AppArmor sha1 policy hashing enabled
Sep 14 16:31:00 node-1 kernel: [    2.415056] IMA: No TPM chip found, activating TPM-bypass!
Sep 14 16:31:00 node-1 kernel: [    2.423926] regulator-dummy: disabling
Sep 14 16:31:00 node-1 kernel: [    2.424676]   Magic number: 0:246:540
Sep 14 16:31:00 node-1 kernel: [    2.427533]  node: hash matches
Sep 14 16:31:00 node-1 kernel: [    2.466903] rtc_cmos 00:02: setting system clock to 2016-09-14 16:30:25 UTC (1473870625)
Sep 14 16:31:00 node-1 kernel: [    2.467252] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 14 16:31:00 node-1 kernel: [    2.467253] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 14 16:31:00 node-1 kernel: [    2.467254] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 14 16:31:00 node-1 kernel: [    2.467254] usb 2-1.4: Manufacturer: Avocent
Sep 14 16:31:00 node-1 kernel: [    2.467255] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 14 16:31:00 node-1 kernel: [    2.512737] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 14 16:31:00 node-1 kernel: [    2.518320] EDD information not available.
Sep 14 16:31:00 node-1 kernel: [    2.523788] PM: Hibernation image not present or could not be loaded.
Sep 14 16:31:00 node-1 kernel: [    2.524651] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 14 16:31:00 node-1 kernel: [    2.535731] Write protecting the kernel read-only data: 12288k
Sep 14 16:31:00 node-1 kernel: [    2.541806] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 14 16:31:00 node-1 kernel: [    2.554026] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 14 16:31:00 node-1 kernel: [    2.586267] device-mapper: multipath: version 1.6.0 loaded
Sep 14 16:31:00 node-1 kernel: [    2.594254] systemd-udevd[213]: starting version 204
Sep 14 16:31:00 node-1 kernel: [    2.617772] md: linear personality registered for level -1
Sep 14 16:31:00 node-1 kernel: [    2.632362] md: multipath personality registered for level -4
Sep 14 16:31:00 node-1 kernel: [    2.640399] md: raid0 personality registered for level 0
Sep 14 16:31:00 node-1 kernel: [    2.648968] md: raid1 personality registered for level 1
Sep 14 16:31:00 node-1 kernel: [    2.657982] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 14 16:31:00 node-1 kernel: [    2.664276] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 14 16:31:00 node-1 kernel: [    2.664646] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 14 16:31:00 node-1 kernel: [    2.676957] megasas: FW now in Ready state
Sep 14 16:31:00 node-1 kernel: [    2.677101] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Sep 14 16:31:00 node-1 kernel: [    2.677117] 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 14 16:31:00 node-1 kernel: [    2.677118] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 14 16:31:00 node-1 kernel: [    2.678190] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.678358] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.678437] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.678568] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.678903] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.696726] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Sep 14 16:31:00 node-1 kernel: [    2.696744] enic 0000:07: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 14 16:31:00 node-1 kernel: [    2.696790] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 14 16:31:00 node-1 kernel: [    2.698976] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.699146] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.699272] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.699413] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.699794] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.715961] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Sep 14 16:31:00 node-1 kernel: [    2.715962] 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 14 16:31:00 node-1 kernel: [    2.715987] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 14 16:31:00 node-1 kernel: [    2.716278] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.716358] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.716510] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.716600] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.717003] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.721375] raid6: sse2x1   10961 MB/s
Sep 14 16:31:00 node-1 kernel: [    2.734079] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Sep 14 16:31:00 node-1 kernel: [    2.734088] 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 14 16:31:00 node-1 kernel: [    2.734092] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 14 16:31:00 node-1 kernel: [    2.734473] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.734709] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.734812] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.734867] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.735165] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.789316] raid6: sse2x2   13902 MB/s
Sep 14 16:31:00 node-1 kernel: [    2.857257] raid6: sse2x4   16832 MB/s
Sep 14 16:31:00 node-1 kernel: [    2.888257] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.888264] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.888269] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.888276] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.888281] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.888286] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.888291] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.888296] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.888302] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.888307] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.888312] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.888317] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.888322] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.888327] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.888332] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.888337] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Sep 14 16:31:00 node-1 kernel: [    2.888384] hidraw: raw HID events driver (C) Jiri Kosina
Sep 14 16:31:00 node-1 kernel: [    2.888540] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 14 16:31:00 node-1 kernel: [    2.910574] usbcore: registered new interface driver usbhid
Sep 14 16:31:00 node-1 kernel: [    2.917210] usbhid: USB HID core driver
Sep 14 16:31:00 node-1 kernel: [    2.925168] raid6: avx2x1   22520 MB/s
Sep 14 16:31:00 node-1 kernel: [    2.935718] 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 14 16:31:00 node-1 kernel: [    2.948601] 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 14 16:31:00 node-1 kernel: [    2.961568] 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 14 16:31:00 node-1 kernel: [    2.975017] 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 14 16:31:00 node-1 kernel: [    2.988709] 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 14 16:31:00 node-1 kernel: [    2.997183] raid6: avx2x2    3246 MB/s
Sep 14 16:31:00 node-1 kernel: [    3.009022] 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 14 16:31:00 node-1 kernel: [    3.065040] raid6: avx2x4   21286 MB/s
Sep 14 16:31:00 node-1 kernel: [    3.072021] raid6: using algorithm avx2x1 (22520 MB/s)
Sep 14 16:31:00 node-1 kernel: [    3.078937] raid6: using avx2x2 recovery algorithm
Sep 14 16:31:00 node-1 kernel: [    3.086606] xor: automatically using best checksumming function:
Sep 14 16:31:00 node-1 kernel: [    3.132985]    avx       : 35670.000 MB/sec
Sep 14 16:31:00 node-1 kernel: [    3.140415] async_tx: api initialized (async)
Sep 14 16:31:00 node-1 kernel: [    3.151099] md: raid6 personality registered for level 6
Sep 14 16:31:00 node-1 kernel: [    3.157759] md: raid5 personality registered for level 5
Sep 14 16:31:00 node-1 kernel: [    3.164188] md: raid4 personality registered for level 4
Sep 14 16:31:00 node-1 kernel: [    3.173756] md: raid10 personality registered for level 10
Sep 14 16:31:00 node-1 kernel: [    3.227190] multipathd (353): /proc/353/oom_adj is deprecated, please use /proc/353/oom_score_adj instead.
Sep 14 16:31:00 node-1 kernel: [    3.229505] megasas:IOC Init cmd success
Sep 14 16:31:00 node-1 kernel: [    3.276929] megasas: INIT adapter done
Sep 14 16:31:00 node-1 kernel: [    3.352847] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 14 16:31:00 node-1 kernel: [    3.359153] scsi0 : LSI SAS based MegaRAID driver
Sep 14 16:31:00 node-1 kernel: [    3.366594] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 14 16:31:00 node-1 kernel: [    3.385018] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 14 16:31:00 node-1 kernel: [    3.398896] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 14 16:31:00 node-1 kernel: [    3.404790] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 14 16:31:00 node-1 kernel: [    3.416534] sd 0:2:0:0: [sda] Write Protect is off
Sep 14 16:31:00 node-1 kernel: [    3.422325] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 14 16:31:00 node-1 kernel: [    3.422349] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 14 16:31:00 node-1 kernel: [    3.463165]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Sep 14 16:31:00 node-1 kernel: [    3.469128] Switched to clocksource tsc
Sep 14 16:31:00 node-1 kernel: [    3.470183] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 14 16:31:00 node-1 kernel: [    3.608058] random: lvm urandom read with 27 bits of entropy available
Sep 14 16:31:00 node-1 kernel: [    3.725329] bio: create slab <bio-1> at 1
Sep 14 16:31:00 node-1 kernel: [    4.617352] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Sep 14 16:31:00 node-1 kernel: [    5.337062] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Sep 14 16:31:00 node-1 kernel: [    5.364587] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 14 16:31:00 node-1 kernel: [    5.377243] random: nonblocking pool is initialized
Sep 14 16:31:00 node-1 kernel: [    5.464769] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 14 16:31:00 node-1 kernel: [    5.494756] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 14 16:31:00 node-1 kernel: [    5.606246] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 14 16:31:00 node-1 kernel: [    5.823491] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 14 16:31:00 node-1 kernel: [    5.865847] XFS (dm-1): Mounting Filesystem
Sep 14 16:31:00 node-1 kernel: [    6.164495] XFS (dm-1): Ending clean mount
Sep 14 16:31:00 node-1 kernel: [    6.217006] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 14 16:31:00 node-1 kernel: [    6.253174] XFS (dm-2): Mounting Filesystem
Sep 14 16:31:00 node-1 kernel: [    6.321448] XFS (dm-2): Ending clean mount
Sep 14 16:31:00 node-1 kernel: [    6.435869] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Sep 14 16:31:00 node-1 kernel: [    8.099036] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 14 16:31:00 node-1 kernel: [    8.126744] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 14 16:31:00 node-1 kernel: [    8.254323] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 14 16:31:00 node-1 kernel: [    8.254334] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 14 16:31:00 node-1 kernel: [    8.254342] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 14 16:31:00 node-1 kernel: [    8.254350] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 14 16:31:00 node-1 kernel: [    8.290204] systemd-udevd[804]: starting version 204
Sep 14 16:31:00 node-1 kernel: [    8.506345] power_meter ACPI000D:00: Found ACPI power meter.
Sep 14 16:31:00 node-1 kernel: [    8.506358] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 14 16:31:00 node-1 kernel: [    8.513412] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 14 16:31:00 node-1 kernel: [    8.513417] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 14 16:31:00 node-1 kernel: [    8.513420] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 14 16:31:00 node-1 kernel: [    8.513421] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 14 16:31:00 node-1 kernel: [    8.513436] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 14 16:31:00 node-1 kernel: [    8.517212] wmi: Mapper loaded
Sep 14 16:31:00 node-1 kernel: [    8.523115] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 14 16:31:00 node-1 kernel: [    8.556474] IPMI System Interface driver.
Sep 14 16:31:00 node-1 kernel: [    8.556526] ipmi_si: probing via ACPI
Sep 14 16:31:00 node-1 kernel: [    8.556539] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 14 16:31:00 node-1 kernel: [    8.556541] ipmi_si: Adding ACPI-specified kcs state machine
Sep 14 16:31:00 node-1 kernel: [    8.556559] ipmi_si: probing via SMBIOS
Sep 14 16:31:00 node-1 kernel: [    8.556561] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 14 16:31:00 node-1 kernel: [    8.556561] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 14 16:31:00 node-1 kernel: [    8.556563] ipmi_si: probing via SPMI
Sep 14 16:31:00 node-1 kernel: [    8.556564] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 14 16:31:00 node-1 kernel: [    8.556565] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 14 16:31:00 node-1 kernel: [    8.556567] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 14 16:31:00 node-1 kernel: [    8.616822] systemd-udevd[828]: renamed network interface eth0 to enp6s0
Sep 14 16:31:00 node-1 kernel: [    8.648694] systemd-udevd[822]: renamed network interface eth1 to enp7s0
Sep 14 16:31:00 node-1 kernel: [    8.697416] systemd-udevd[825]: renamed network interface eth2 to enp8s0
Sep 14 16:31:00 node-1 kernel: [    8.728692] systemd-udevd[833]: renamed network interface eth3 to enp9s0
Sep 14 16:31:00 node-1 kernel: [    8.772279] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 14 16:31:00 node-1 kernel: [    8.772285] ipmi_si 00:09: IPMI kcs interface initialized
Sep 14 16:31:00 node-1 kernel: [    9.001675] type=1400 audit(1473870632.077:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1070 comm="apparmor_parser"
Sep 14 16:31:00 node-1 kernel: [    9.001822] type=1400 audit(1473870632.077:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1070 comm="apparmor_parser"
Sep 14 16:31:00 node-1 kernel: [    9.001949] type=1400 audit(1473870632.077:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1070 comm="apparmor_parser"
Sep 14 16:31:00 node-1 kernel: [    9.005554] type=1400 audit(1473870632.081:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1079 comm="apparmor_parser"
Sep 14 16:31:00 node-1 kernel: [    9.005693] type=1400 audit(1473870632.081:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1079 comm="apparmor_parser"
Sep 14 16:31:00 node-1 kernel: [    9.005812] type=1400 audit(1473870632.081:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1079 comm="apparmor_parser"
Sep 14 16:31:00 node-1 kernel: [    9.018507] type=1400 audit(1473870632.093:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1114 comm="apparmor_parser"
Sep 14 16:31:00 node-1 kernel: [    9.018642] type=1400 audit(1473870632.093:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1114 comm="apparmor_parser"
Sep 14 16:31:00 node-1 kernel: [    9.018756] type=1400 audit(1473870632.093:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1114 comm="apparmor_parser"
Sep 14 16:31:00 node-1 kernel: [    9.019599] type=1400 audit(1473870632.093:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1069 comm="apparmor_parser"
Sep 14 16:31:00 node-1 kernel: [    9.565740] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 14 16:31:00 node-1 kernel: [    9.574562] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 14 16:31:00 node-1 kernel: [    9.764067] enic 0000:06:00.0 enp6s0: Link UP
Sep 14 16:31:00 node-1 kernel: [    9.765189] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 14 16:31:00 node-1 kernel: [    9.765195] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 14 16:31:00 node-1 kernel: [   19.503358] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 14 16:31:02 node-1 failsafe: Failsafe of 120 seconds reached.
Sep 14 16:31:02 node-1 kernel: [   38.357888] init: failsafe main process (8464) killed by TERM signal
Sep 14 16:31:02 node-1 dbus[8493]: [system] AppArmor D-Bus mediation is enabled
Sep 14 16:31:02 node-1 kernel: [   38.642177] audit_printk_skb: 30 callbacks suppressed
Sep 14 16:31:02 node-1 kernel: [   38.642178] type=1400 audit(1473870662.352:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8589 comm="apparmor_parser"
Sep 14 16:31:02 node-1 kernel: [   38.642182] type=1400 audit(1473870662.352:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8589 comm="apparmor_parser"
Sep 14 16:31:02 node-1 kernel: [   38.642185] type=1400 audit(1473870662.352:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8589 comm="apparmor_parser"
Sep 14 16:31:02 node-1 kernel: [   38.642408] type=1400 audit(1473870662.352:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8589 comm="apparmor_parser"
Sep 14 16:31:02 node-1 kernel: [   38.642410] type=1400 audit(1473870662.352:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8589 comm="apparmor_parser"
Sep 14 16:31:02 node-1 kernel: [   38.642522] type=1400 audit(1473870662.352:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8589 comm="apparmor_parser"
Sep 14 16:31:02 node-1 kernel: [   38.659811] type=1400 audit(1473870662.368:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8590 comm="apparmor_parser"
Sep 14 16:31:02 node-1 kernel: [   38.747953] type=1400 audit(1473870662.456:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8592 comm="apparmor_parser"
Sep 14 16:31:02 node-1 anacron[8646]: Anacron 2.3 started on 2016-09-14
Sep 14 16:31:02 node-1 cron[8623]: (CRON) INFO (pidfile fd = 3)
Sep 14 16:31:02 node-1 cron[8673]: (CRON) STARTUP (fork ok)
Sep 14 16:31:02 node-1 multipathd: path checkers start up
Sep 14 16:31:02 node-1 anacron[8646]: Will run job `cron.daily' in 5 min.
Sep 14 16:31:02 node-1 anacron[8646]: Will run job `cron.weekly' in 10 min.
Sep 14 16:31:02 node-1 anacron[8646]: Will run job `cron.monthly' in 15 min.
Sep 14 16:31:02 node-1 anacron[8646]: Jobs will be executed sequentially
Sep 14 16:31:02 node-1 cron[8673]: (CRON) INFO (Running @reboot jobs)
Sep 14 16:31:03 node-1 postfix/master[8802]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 14 16:31:06 node-1 puppet-agent[8987]: Reopening log files
Sep 14 16:31:07 node-1 puppet-agent[8987]: Could not request certificate: Connection refused - connect(2)
Sep 14 16:31:20 node-1 puppet-user[9066]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 14 16:31:20 node-1 puppet-user[9066]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 14 16:31:21 node-1 puppet-user[9066]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 14 16:31:21 node-1 puppet-user[9066]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 14 16:31:21 node-1 puppet-user[9066]: Finished catalog run in 0.92 seconds
Sep 14 16:31:23 node-1 multipathd: uevent trigger error
Sep 14 16:31:23 node-1 puppet-user[9501]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 14 16:31:23 node-1 puppet-user[9501]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Sep 14 16:31:23 node-1 puppet-user[9501]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 14 16:31:23 node-1 puppet-user[9501]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 14 16:31:23 node-1 puppet-user[9501]: (/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 14 16:31:23 node-1 puppet-user[9501]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 14 16:31:23 node-1 puppet-user[9501]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 14 16:31:23 node-1 puppet-user[9501]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 14 16:31:23 node-1 puppet-user[9501]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 14 16:31:23 node-1 puppet-user[9501]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 14 16:31:23 node-1 puppet-user[9501]: Finished catalog run in 0.07 seconds
Sep 14 16:31:24 node-1 puppet-user[10088]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 14 16:31:24 node-1 puppet-user[10088]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Sep 14 16:31:25 node-1 puppet-user[10088]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 14 16:31:25 node-1 puppet-user[10088]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 14 16:31:25 node-1 puppet-user[10088]: Finished catalog run in 0.06 seconds
Sep 14 16:31:26 node-1 puppet-user[10557]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 14 16:31:26 node-1 puppet-user[10557]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 14 16:31:26 node-1 puppet-user[10557]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 14 16:31:26 node-1 puppet-user[10557]: Finished catalog run in 0.04 seconds
Sep 14 16:31:28 node-1 puppet-user[11011]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 14 16:31:28 node-1 puppet-user[11011]: Compiled catalog for node-1.domain.tld in environment production in 0.21 seconds
Sep 14 16:31:28 node-1 puppet-user[11011]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 14 16:31:30 node-1 puppet-user[11011]: (/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 14 16:31:30 node-1 puppet-user[11011]: Finished catalog run in 1.95 seconds
Sep 14 16:31:31 node-1 puppet-user[11547]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 14 16:31:31 node-1 puppet-user[11547]: Compiled catalog for node-1.domain.tld in environment production in 0.21 seconds
Sep 14 16:31:32 node-1 puppet-user[11547]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 14 16:31:32 node-1 puppet-user[11547]: (/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 14 16:31:32 node-1 puppet-user[11547]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 14 16:31:32 node-1 puppet-user[11547]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 14 16:31:32 node-1 puppet-user[11547]: Finished catalog run in 0.29 seconds
Sep 14 16:31:33 node-1 puppet-user[12028]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 14 16:31:33 node-1 puppet-user[12028]: Compiled catalog for node-1.domain.tld in environment production in 0.16 seconds
Sep 14 16:31:34 node-1 puppet-user[12028]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 14 16:31:34 node-1 kernel: [   70.297697] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 14 16:31:34 node-1 kernel: [   70.297748] 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 14 16:31:34 node-1 puppet-user[12028]: (/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 14 16:31:34 node-1 puppet-user[12028]: Finished catalog run in 0.06 seconds
Sep 14 16:31:35 node-1 puppet-user[12497]: (Scope(Class[main])) MODULAR: sync_time
Sep 14 16:31:35 node-1 puppet-user[12497]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Sep 14 16:31:36 node-1 ntpdate[13087]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 14 16:31:42 node-1 ntpdate[13087]: adjust time server 10.20.0.2 offset -0.300722 sec
Sep 14 16:31:42 node-1 puppet-user[12497]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 14 16:31:42 node-1 puppet-user[12497]: Finished catalog run in 6.17 seconds
Sep 14 16:31:46 node-1 puppet-user[13274]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 14 16:31:46 node-1 puppet-user[13274]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Sep 14 16:31:46 node-1 puppet-user[13274]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 14 16:31:46 node-1 puppet-user[13274]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Sep 14 16:31:46 node-1 puppet-user[13274]: Finished catalog run in 0.07 seconds
Sep 14 16:31:47 node-1 kernel: [   83.791300] init: plymouth-upstart-bridge main process ended, respawning
Sep 14 16:31:47 node-1 puppet-agent[8987]: Could not run: SIGTERM
Sep 14 16:31:47 node-1 kernel: [   84.046374] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 14 16:31:47 node-1 ec2: 
Sep 14 16:31:47 node-1 ec2: #############################################################
Sep 14 16:31:47 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 14 16:31:47 node-1 ec2: 1024 4a:ba:85:50:0e:9e:47:4a:65:a7:db:a1:3e:c3:7b:b5  root@node-1.domain.tld (DSA)
Sep 14 16:31:47 node-1 ec2: 256 da:d8:a4:8e:a7:93:ae:e9:3f:21:3b:95:4c:52:63:06  root@node-1.domain.tld (ECDSA)
Sep 14 16:31:47 node-1 ec2: 256 3b:24:10:68:57:f3:bc:c9:e9:47:fa:aa:ab:e4:71:c2  root@node-1.domain.tld (ED25519)
Sep 14 16:31:47 node-1 ec2: 2048 1a:9c:26:09:77:75:6a:b0:af:b7:b9:4e:ed:92:8e:3b  root@node-1.domain.tld (RSA)
Sep 14 16:31:47 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 14 16:31:47 node-1 ec2: #############################################################
Sep 14 16:31:48 node-1 puppet-user[13729]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 14 16:31:50 node-1 puppet-user[13729]: Compiled catalog for node-1.domain.tld in environment production in 2.15 seconds
Sep 14 16:31:50 node-1 puppet-user[13729]: (/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 14 16:31:50 node-1 puppet-user[13729]: (/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 14 16:31:50 node-1 puppet-user[13729]: (/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 14 16:31:50 node-1 puppet-user[13729]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Sep 14 16:31:50 node-1 puppet-user[13729]: (/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 14 16:31:50 node-1 puppet-user[13729]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Sep 14 16:31:50 node-1 puppet-user[13729]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 14 16:31:50 node-1 puppet-user[13729]: (/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 14 16:31:50 node-1 puppet-user[13729]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 14 16:31:50 node-1 puppet-user[13729]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Sep 14 16:31:50 node-1 puppet-user[13729]: (/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 14 16:31:50 node-1 puppet-user[13729]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Sep 14 16:31:50 node-1 puppet-user[13729]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Sep 14 16:31:50 node-1 puppet-user[13729]: (/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 14 16:31:51 node-1 puppet-user[13729]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Sep 14 16:31:51 node-1 puppet-user[13729]: (/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 14 16:31:59 node-1 puppet-user[13729]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Sep 14 16:31:59 node-1 puppet-user[13729]: Finished catalog run in 9.51 seconds
Sep 14 16:32:01 node-1 puppet-user[14751]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 14 16:32:01 node-1 puppet-user[14751]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Sep 14 16:32:01 node-1 CRON[15186]: (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 14 16:32:06 node-1 puppet-user[14751]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 14 16:32:23 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 14 16:32:23 node-1 nailgun-agent: I, [2016-09-14T16:32:23.887582 #15189]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 14 16:32:36 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 14 16:32:37 node-1 nailgun-agent: I, [2016-09-14T16:32:37.051873 #15189]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep 14 16:32:39 node-1 puppet-user[14751]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 14 16:32:39 node-1 puppet-user[14751]: Finished catalog run in 37.51 seconds
Sep 14 16:32:41 node-1 puppet-user[17596]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 14 16:32:41 node-1 puppet-user[17596]: Compiled catalog for node-1.domain.tld in environment production in 0.59 seconds
Sep 14 16:32:41 node-1 puppet-user[17596]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 14 16:32:42 node-1 puppet-user[17596]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 14 16:32:42 node-1 puppet-user[17596]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 14 16:32:42 node-1 puppet-user[17596]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 14 16:32:42 node-1 puppet-user[17596]: Finished catalog run in 0.10 seconds
Sep 14 16:32:43 node-1 puppet-user[18065]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 14 16:32:44 node-1 puppet-user[18065]: Compiled catalog for node-1.domain.tld in environment production in 0.90 seconds
Sep 14 16:32:45 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 14 16:32:45 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 14 16:32:45 node-1 crontab[18508]: (root) LIST (root)
Sep 14 16:32:45 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 14 16:32:45 node-1 crontab[18509]: (root) REPLACE (root)
Sep 14 16:32:47 node-1 puppet-user[18065]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/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 14 16:32:49 node-1 puppet-user[18065]: (/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 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/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 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/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 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/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 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/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 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/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 14 16:32:49 node-1 puppet-user[18065]: (/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 14 16:32:49 node-1 puppet-user[18065]: (/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 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 14 16:32:49 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 14 16:32:50 node-1 puppet-user[18065]: (/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 14 16:32:50 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 14 16:32:50 node-1 puppet-user[18065]: (/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 14 16:32:50 node-1 puppet-user[18065]: (/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 14 16:32:50 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 14 16:32:50 node-1 puppet-user[18065]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 14 16:32:50 node-1 puppet-user[18065]: (/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 14 16:32:50 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8437" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 16:32:50 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 14 16:32:52 node-1 multipathd: uevent trigger error
<27>Sep 14 16:32:52 node-1 multipathd: uevent trigger error
<27>Sep 14 16:32:52 node-1 multipathd: uevent trigger error
<27>Sep 14 16:32:52 node-1 multipathd: uevent trigger error
<27>Sep 14 16:32:52 node-1 multipathd: uevent trigger error
<27>Sep 14 16:33:11 node-1 multipathd: uevent trigger error
<27>Sep 14 16:33:11 node-1 multipathd: uevent trigger error
<27>Sep 14 16:33:11 node-1 multipathd: uevent trigger error
<27>Sep 14 16:33:11 node-1 multipathd: uevent trigger error
<27>Sep 14 16:33:11 node-1 multipathd: uevent trigger error
<27>Sep 14 16:33:12 node-1 multipathd: uevent trigger error
<27>Sep 14 16:34:07 node-1 multipathd: uevent trigger error
<27>Sep 14 16:34:07 node-1 multipathd: uevent trigger error
<27>Sep 14 16:34:07 node-1 multipathd: uevent trigger error
<27>Sep 14 16:34:07 node-1 multipathd: uevent trigger error
<27>Sep 14 16:34:07 node-1 multipathd: uevent trigger error
<27>Sep 14 16:34:49 node-1 ntpdate[2176]: no servers can be used, exiting
<27>Sep 14 16:35:21 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:21 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:21 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:21 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:21 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:24 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:24 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:24 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:24 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:24 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:24 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:37 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:37 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:37 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:37 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:37 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:40 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:40 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:40 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:40 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:40 node-1 multipathd: uevent trigger error
<27>Sep 14 16:35:40 node-1 multipathd: uevent trigger error
<27>Sep 14 16:36:43 node-1 multipathd: uevent trigger error
<27>Sep 14 16:36:43 node-1 multipathd: uevent trigger error
<27>Sep 14 16:36:43 node-1 multipathd: uevent trigger error
<27>Sep 14 16:36:43 node-1 multipathd: uevent trigger error
<27>Sep 14 16:36:43 node-1 multipathd: uevent trigger error
<27>Sep 14 16:36:51 node-1 multipathd: uevent trigger error
<27>Sep 14 16:36:51 node-1 multipathd: uevent trigger error
<27>Sep 14 16:36:51 node-1 multipathd: uevent trigger error
<27>Sep 14 16:36:51 node-1 multipathd: uevent trigger error
<27>Sep 14 16:36:51 node-1 multipathd: uevent trigger error
<27>Sep 14 16:36:54 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 14 16:36:54 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 14 16:37:00 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 14 16:37:00 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 14 16:37:05 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 14 16:37:11 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 14 16:37:11 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 14 16:37:18 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:18 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:18 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:18 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:18 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:18 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:31 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:31 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:31 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:31 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:31 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:31 node-1 multipathd: uevent trigger error
<129>Sep 14 16:37:33 node-1 haproxy[22572]: 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 14 16:37:34 node-1 haproxy[22576]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:37:34 node-1 haproxy[22576]: 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 14 16:37:34 node-1 haproxy[22576]: proxy mysqld has no server available!
<27>Sep 14 16:37:36 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:36 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:36 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:36 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:36 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:36 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:40 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:40 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:40 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:40 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:40 node-1 multipathd: uevent trigger error
<129>Sep 14 16:37:42 node-1 haproxy[25151]: 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 14 16:37:43 node-1 haproxy[25155]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:37:43 node-1 haproxy[25155]: 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 14 16:37:43 node-1 haproxy[25155]: proxy mysqld has no server available!
<129>Sep 14 16:37:43 node-1 haproxy[25155]: 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 14 16:37:44 node-1 haproxy[25155]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:37:44 node-1 haproxy[25155]: 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 14 16:37:44 node-1 haproxy[25155]: proxy object-storage has no server available!
<27>Sep 14 16:37:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:45 node-1 multipathd: uevent trigger error
<129>Sep 14 16:37:48 node-1 haproxy[26492]: 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 14 16:37:48 node-1 haproxy[26492]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:37:48 node-1 haproxy[26492]: 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 14 16:37:48 node-1 haproxy[26492]: proxy neutron has no server available!
<129>Sep 14 16:37:48 node-1 haproxy[26492]: 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 14 16:37:49 node-1 haproxy[26496]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:37:49 node-1 haproxy[26496]: 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 14 16:37:49 node-1 haproxy[26496]: proxy mysqld has no server available!
<129>Sep 14 16:37:49 node-1 haproxy[26496]: 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 14 16:37:49 node-1 haproxy[26496]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:37:50 node-1 haproxy[26496]: 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 14 16:37:50 node-1 haproxy[26496]: proxy object-storage has no server available!
<27>Sep 14 16:37:51 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:51 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:51 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:51 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:51 node-1 multipathd: uevent trigger error
<129>Sep 14 16:37:53 node-1 haproxy[27894]: 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 14 16:37:54 node-1 haproxy[27898]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:37:54 node-1 haproxy[27898]: 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 14 16:37:54 node-1 haproxy[27898]: proxy keystone-1 has no server available!
<129>Sep 14 16:37:54 node-1 haproxy[27898]: 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 14 16:37:54 node-1 haproxy[27898]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:37:54 node-1 haproxy[27898]: 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 14 16:37:54 node-1 haproxy[27898]: proxy keystone-2 has no server available!
<129>Sep 14 16:37:54 node-1 haproxy[27898]: 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 14 16:37:54 node-1 haproxy[27898]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:37:54 node-1 haproxy[27898]: 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 14 16:37:54 node-1 haproxy[27898]: proxy neutron has no server available!
<129>Sep 14 16:37:55 node-1 haproxy[27898]: 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 14 16:37:55 node-1 haproxy[27898]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:37:55 node-1 haproxy[27898]: 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 14 16:37:55 node-1 haproxy[27898]: proxy mysqld has no server available!
<129>Sep 14 16:37:55 node-1 haproxy[27898]: 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 14 16:37:55 node-1 haproxy[27898]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:37:55 node-1 haproxy[27898]: 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 14 16:37:55 node-1 haproxy[27898]: proxy object-storage has no server available!
<27>Sep 14 16:37:57 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:57 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:57 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:57 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:57 node-1 multipathd: uevent trigger error
<27>Sep 14 16:37:57 node-1 multipathd: uevent trigger error
<129>Sep 14 16:37:59 node-1 haproxy[29299]: 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 14 16:37:59 node-1 haproxy[29299]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:37:59 node-1 haproxy[29299]: 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 14 16:37:59 node-1 haproxy[29299]: proxy keystone-1 has no server available!
<129>Sep 14 16:37:59 node-1 haproxy[29299]: 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 14 16:37:59 node-1 haproxy[29299]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:37:59 node-1 haproxy[29299]: 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 14 16:37:59 node-1 haproxy[29299]: proxy keystone-2 has no server available!
<129>Sep 14 16:37:59 node-1 haproxy[29299]: 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 14 16:38:00 node-1 haproxy[29305]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:00 node-1 haproxy[29305]: 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 14 16:38:00 node-1 haproxy[29305]: proxy neutron has no server available!
<129>Sep 14 16:38:00 node-1 haproxy[29305]: 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 14 16:38:00 node-1 haproxy[29305]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:00 node-1 haproxy[29305]: 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 14 16:38:00 node-1 haproxy[29305]: proxy mysqld has no server available!
<129>Sep 14 16:38:00 node-1 haproxy[29305]: 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 14 16:38:00 node-1 haproxy[29305]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:00 node-1 haproxy[29305]: 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 14 16:38:00 node-1 haproxy[29305]: proxy object-storage has no server available!
<129>Sep 14 16:38:00 node-1 haproxy[29305]: 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 14 16:38:01 node-1 haproxy[29305]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:01 node-1 haproxy[29305]: 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 14 16:38:01 node-1 haproxy[29305]: proxy aodh has no server available!
<27>Sep 14 16:38:02 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:02 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:02 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:02 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:02 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:02 node-1 multipathd: uevent trigger error
<129>Sep 14 16:38:04 node-1 haproxy[30642]: 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 14 16:38:04 node-1 haproxy[30642]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:05 node-1 haproxy[30646]: 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 14 16:38:05 node-1 haproxy[30646]: proxy keystone-1 has no server available!
<129>Sep 14 16:38:05 node-1 haproxy[30646]: 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 14 16:38:05 node-1 haproxy[30646]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:05 node-1 haproxy[30646]: 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 14 16:38:05 node-1 haproxy[30646]: proxy keystone-2 has no server available!
<129>Sep 14 16:38:05 node-1 haproxy[30646]: 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 14 16:38:05 node-1 haproxy[30646]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:05 node-1 haproxy[30646]: 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 14 16:38:05 node-1 haproxy[30646]: proxy neutron has no server available!
<129>Sep 14 16:38:05 node-1 haproxy[30646]: 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 14 16:38:05 node-1 haproxy[30646]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:05 node-1 haproxy[30646]: 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 14 16:38:05 node-1 haproxy[30646]: proxy mysqld has no server available!
<129>Sep 14 16:38:06 node-1 haproxy[30646]: 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 14 16:38:06 node-1 haproxy[30646]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:06 node-1 haproxy[30646]: 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 14 16:38:06 node-1 haproxy[30646]: proxy object-storage has no server available!
<129>Sep 14 16:38:06 node-1 haproxy[30646]: 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 14 16:38:06 node-1 haproxy[30646]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:06 node-1 haproxy[30646]: 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 14 16:38:06 node-1 haproxy[30646]: proxy aodh has no server available!
<129>Sep 14 16:38:06 node-1 haproxy[30646]: 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 14 16:38:06 node-1 haproxy[30646]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:06 node-1 haproxy[30646]: 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 14 16:38:06 node-1 haproxy[30646]: proxy ceilometer has no server available!
<27>Sep 14 16:38:08 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:08 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:08 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:08 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:08 node-1 multipathd: uevent trigger error
<129>Sep 14 16:38:10 node-1 haproxy[32000]: 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 14 16:38:10 node-1 haproxy[32000]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:10 node-1 haproxy[32000]: 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 14 16:38:10 node-1 haproxy[32000]: proxy keystone-1 has no server available!
<129>Sep 14 16:38:10 node-1 haproxy[32000]: 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 14 16:38:10 node-1 haproxy[32000]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:11 node-1 haproxy[32017]: 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 14 16:38:11 node-1 haproxy[32017]: proxy keystone-2 has no server available!
<129>Sep 14 16:38:11 node-1 haproxy[32017]: 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 14 16:38:11 node-1 haproxy[32017]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:11 node-1 haproxy[32017]: 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 14 16:38:11 node-1 haproxy[32017]: proxy neutron has no server available!
<129>Sep 14 16:38:11 node-1 haproxy[32017]: 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 14 16:38:11 node-1 haproxy[32017]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:11 node-1 haproxy[32017]: 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 14 16:38:11 node-1 haproxy[32017]: proxy mysqld has no server available!
<129>Sep 14 16:38:11 node-1 haproxy[32017]: 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 14 16:38:11 node-1 haproxy[32017]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:11 node-1 haproxy[32017]: 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 14 16:38:11 node-1 haproxy[32017]: proxy object-storage has no server available!
<129>Sep 14 16:38:11 node-1 haproxy[32017]: 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 14 16:38:12 node-1 haproxy[32017]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:12 node-1 haproxy[32017]: 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 14 16:38:12 node-1 haproxy[32017]: proxy aodh has no server available!
<129>Sep 14 16:38:12 node-1 haproxy[32017]: 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 14 16:38:12 node-1 haproxy[32017]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:12 node-1 haproxy[32017]: 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 14 16:38:12 node-1 haproxy[32017]: proxy ceilometer has no server available!
<27>Sep 14 16:38:13 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:13 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:13 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:13 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:13 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:13 node-1 multipathd: uevent trigger error
<129>Sep 14 16:38:15 node-1 haproxy[941]: 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 14 16:38:16 node-1 haproxy[950]: 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 14 16:38:16 node-1 haproxy[950]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:16 node-1 haproxy[950]: 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 14 16:38:16 node-1 haproxy[950]: proxy keystone-1 has no server available!
<129>Sep 14 16:38:16 node-1 haproxy[950]: 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 14 16:38:16 node-1 haproxy[950]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:16 node-1 haproxy[950]: 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 14 16:38:16 node-1 haproxy[950]: proxy keystone-2 has no server available!
<129>Sep 14 16:38:16 node-1 haproxy[950]: 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 14 16:38:16 node-1 haproxy[950]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:16 node-1 haproxy[950]: 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 14 16:38:16 node-1 haproxy[950]: proxy neutron has no server available!
<129>Sep 14 16:38:16 node-1 haproxy[950]: 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 14 16:38:16 node-1 haproxy[950]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:17 node-1 haproxy[950]: 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 14 16:38:17 node-1 haproxy[950]: proxy mysqld has no server available!
<129>Sep 14 16:38:17 node-1 haproxy[950]: 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 14 16:38:17 node-1 haproxy[950]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:17 node-1 haproxy[950]: 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 14 16:38:17 node-1 haproxy[950]: proxy object-storage has no server available!
<129>Sep 14 16:38:17 node-1 haproxy[950]: 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 14 16:38:17 node-1 haproxy[950]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:17 node-1 haproxy[950]: 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 14 16:38:17 node-1 haproxy[950]: proxy aodh has no server available!
<129>Sep 14 16:38:17 node-1 haproxy[950]: 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 14 16:38:17 node-1 haproxy[950]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:17 node-1 haproxy[950]: 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 14 16:38:17 node-1 haproxy[950]: proxy ceilometer has no server available!
<27>Sep 14 16:38:18 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:18 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:19 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:19 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:19 node-1 multipathd: uevent trigger error
<129>Sep 14 16:38:21 node-1 haproxy[2451]: 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 14 16:38:21 node-1 haproxy[2451]: 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 14 16:38:21 node-1 haproxy[2451]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:21 node-1 haproxy[2451]: 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 14 16:38:21 node-1 haproxy[2451]: proxy keystone-1 has no server available!
<129>Sep 14 16:38:21 node-1 haproxy[2451]: 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 14 16:38:22 node-1 haproxy[2455]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:22 node-1 haproxy[2455]: 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 14 16:38:22 node-1 haproxy[2455]: proxy keystone-2 has no server available!
<129>Sep 14 16:38:22 node-1 haproxy[2455]: 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 14 16:38:22 node-1 haproxy[2455]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:22 node-1 haproxy[2455]: 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 14 16:38:22 node-1 haproxy[2455]: proxy glance-api has no server available!
<129>Sep 14 16:38:22 node-1 haproxy[2455]: 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 14 16:38:22 node-1 haproxy[2455]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:22 node-1 haproxy[2455]: 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 14 16:38:22 node-1 haproxy[2455]: proxy glance-glare has no server available!
<129>Sep 14 16:38:22 node-1 haproxy[2455]: 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 14 16:38:22 node-1 haproxy[2455]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:22 node-1 haproxy[2455]: 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 14 16:38:22 node-1 haproxy[2455]: proxy neutron has no server available!
<129>Sep 14 16:38:22 node-1 haproxy[2455]: 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 14 16:38:22 node-1 haproxy[2455]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:22 node-1 haproxy[2455]: 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 14 16:38:22 node-1 haproxy[2455]: proxy glance-registry has no server available!
<129>Sep 14 16:38:22 node-1 haproxy[2455]: 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 14 16:38:22 node-1 haproxy[2455]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:23 node-1 haproxy[2455]: 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 14 16:38:23 node-1 haproxy[2455]: proxy mysqld has no server available!
<129>Sep 14 16:38:23 node-1 haproxy[2455]: 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 14 16:38:23 node-1 haproxy[2455]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:23 node-1 haproxy[2455]: 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 14 16:38:23 node-1 haproxy[2455]: proxy object-storage has no server available!
<129>Sep 14 16:38:23 node-1 haproxy[2455]: 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 14 16:38:23 node-1 haproxy[2455]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:23 node-1 haproxy[2455]: 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 14 16:38:23 node-1 haproxy[2455]: proxy aodh has no server available!
<129>Sep 14 16:38:23 node-1 haproxy[2455]: 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 14 16:38:23 node-1 haproxy[2455]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:23 node-1 haproxy[2455]: 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 14 16:38:23 node-1 haproxy[2455]: proxy ceilometer has no server available!
<27>Sep 14 16:38:24 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:24 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:24 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:24 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:24 node-1 multipathd: uevent trigger error
<129>Sep 14 16:38:27 node-1 haproxy[3855]: 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 14 16:38:27 node-1 haproxy[3855]: 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 14 16:38:27 node-1 haproxy[3855]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:27 node-1 haproxy[3855]: 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 14 16:38:27 node-1 haproxy[3855]: proxy keystone-1 has no server available!
<129>Sep 14 16:38:27 node-1 haproxy[3855]: 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 14 16:38:27 node-1 haproxy[3855]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:27 node-1 haproxy[3855]: 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 14 16:38:27 node-1 haproxy[3855]: proxy keystone-2 has no server available!
<129>Sep 14 16:38:27 node-1 haproxy[3855]: 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 14 16:38:27 node-1 haproxy[3855]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:27 node-1 haproxy[3855]: 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 14 16:38:27 node-1 haproxy[3855]: proxy nova-api has no server available!
<129>Sep 14 16:38:27 node-1 haproxy[3855]: 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 14 16:38:27 node-1 haproxy[3855]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:28 node-1 haproxy[3860]: 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 14 16:38:28 node-1 haproxy[3860]: proxy nova-metadata-api has no server available!
<129>Sep 14 16:38:28 node-1 haproxy[3860]: 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 14 16:38:28 node-1 haproxy[3860]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:28 node-1 haproxy[3860]: 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 14 16:38:28 node-1 haproxy[3860]: proxy glance-api has no server available!
<129>Sep 14 16:38:28 node-1 haproxy[3860]: 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 14 16:38:28 node-1 haproxy[3860]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:28 node-1 haproxy[3860]: 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 14 16:38:28 node-1 haproxy[3860]: proxy glance-glare has no server available!
<129>Sep 14 16:38:28 node-1 haproxy[3860]: 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 14 16:38:28 node-1 haproxy[3860]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:28 node-1 haproxy[3860]: 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 14 16:38:28 node-1 haproxy[3860]: proxy neutron has no server available!
<129>Sep 14 16:38:28 node-1 haproxy[3860]: 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 14 16:38:28 node-1 haproxy[3860]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:28 node-1 haproxy[3860]: 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 14 16:38:28 node-1 haproxy[3860]: proxy glance-registry has no server available!
<129>Sep 14 16:38:28 node-1 haproxy[3860]: 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 14 16:38:28 node-1 haproxy[3860]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:28 node-1 haproxy[3860]: 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 14 16:38:28 node-1 haproxy[3860]: proxy mysqld has no server available!
<129>Sep 14 16:38:28 node-1 haproxy[3860]: 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 14 16:38:28 node-1 haproxy[3860]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:28 node-1 haproxy[3860]: 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 14 16:38:28 node-1 haproxy[3860]: proxy object-storage has no server available!
<129>Sep 14 16:38:28 node-1 haproxy[3860]: 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 14 16:38:28 node-1 haproxy[3860]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:29 node-1 haproxy[3860]: 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 14 16:38:29 node-1 haproxy[3860]: proxy aodh has no server available!
<129>Sep 14 16:38:29 node-1 haproxy[3860]: 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 14 16:38:29 node-1 haproxy[3860]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:29 node-1 haproxy[3860]: 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 14 16:38:29 node-1 haproxy[3860]: proxy ceilometer has no server available!
<129>Sep 14 16:38:29 node-1 haproxy[3860]: 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 14 16:38:29 node-1 haproxy[3860]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:29 node-1 haproxy[3860]: 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 14 16:38:29 node-1 haproxy[3860]: proxy nova-novncproxy has no server available!
<27>Sep 14 16:38:30 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:30 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:30 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:30 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:30 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:30 node-1 multipathd: uevent trigger error
<129>Sep 14 16:38:33 node-1 haproxy[5377]: 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 14 16:38:33 node-1 haproxy[5377]: 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 14 16:38:33 node-1 haproxy[5377]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:33 node-1 haproxy[5377]: 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 14 16:38:33 node-1 haproxy[5377]: proxy keystone-1 has no server available!
<129>Sep 14 16:38:33 node-1 haproxy[5377]: 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 14 16:38:33 node-1 haproxy[5377]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:33 node-1 haproxy[5377]: 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 14 16:38:33 node-1 haproxy[5377]: proxy keystone-2 has no server available!
<129>Sep 14 16:38:33 node-1 haproxy[5377]: 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 14 16:38:33 node-1 haproxy[5377]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:33 node-1 haproxy[5377]: 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 14 16:38:33 node-1 haproxy[5377]: proxy nova-api has no server available!
<129>Sep 14 16:38:33 node-1 haproxy[5377]: 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 14 16:38:33 node-1 haproxy[5377]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:33 node-1 haproxy[5377]: 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 14 16:38:33 node-1 haproxy[5377]: proxy nova-metadata-api has no server available!
<129>Sep 14 16:38:33 node-1 haproxy[5377]: 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 14 16:38:33 node-1 haproxy[5377]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:33 node-1 haproxy[5377]: 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 14 16:38:33 node-1 haproxy[5377]: proxy cinder-api has no server available!
<129>Sep 14 16:38:33 node-1 haproxy[5377]: 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 14 16:38:33 node-1 haproxy[5377]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:33 node-1 haproxy[5377]: 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 14 16:38:33 node-1 haproxy[5377]: proxy glance-api has no server available!
<129>Sep 14 16:38:33 node-1 haproxy[5377]: 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 14 16:38:34 node-1 haproxy[5381]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:34 node-1 haproxy[5381]: 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 14 16:38:34 node-1 haproxy[5381]: proxy glance-glare has no server available!
<129>Sep 14 16:38:34 node-1 haproxy[5381]: 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 14 16:38:34 node-1 haproxy[5381]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:34 node-1 haproxy[5381]: 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 14 16:38:34 node-1 haproxy[5381]: proxy neutron has no server available!
<129>Sep 14 16:38:34 node-1 haproxy[5381]: 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 14 16:38:34 node-1 haproxy[5381]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:34 node-1 haproxy[5381]: 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 14 16:38:34 node-1 haproxy[5381]: proxy glance-registry has no server available!
<129>Sep 14 16:38:34 node-1 haproxy[5381]: 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 14 16:38:34 node-1 haproxy[5381]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:34 node-1 haproxy[5381]: 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 14 16:38:34 node-1 haproxy[5381]: proxy mysqld has no server available!
<129>Sep 14 16:38:34 node-1 haproxy[5381]: 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 14 16:38:34 node-1 haproxy[5381]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:34 node-1 haproxy[5381]: 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 14 16:38:34 node-1 haproxy[5381]: proxy object-storage has no server available!
<129>Sep 14 16:38:34 node-1 haproxy[5381]: 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 14 16:38:34 node-1 haproxy[5381]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:34 node-1 haproxy[5381]: 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 14 16:38:34 node-1 haproxy[5381]: proxy aodh has no server available!
<129>Sep 14 16:38:34 node-1 haproxy[5381]: 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 14 16:38:34 node-1 haproxy[5381]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:34 node-1 haproxy[5381]: 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 14 16:38:34 node-1 haproxy[5381]: proxy ceilometer has no server available!
<129>Sep 14 16:38:34 node-1 haproxy[5381]: 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 14 16:38:34 node-1 haproxy[5381]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:35 node-1 haproxy[5381]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 14 16:38:35 node-1 haproxy[5381]: proxy nova-novncproxy has no server available!
<27>Sep 14 16:38:36 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:36 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:36 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:36 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:36 node-1 multipathd: uevent trigger error
<129>Sep 14 16:38:39 node-1 haproxy[6776]: 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 14 16:38:39 node-1 haproxy[6776]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:39 node-1 haproxy[6776]: 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 14 16:38:39 node-1 haproxy[6776]: proxy keystone-1 has no server available!
<129>Sep 14 16:38:39 node-1 haproxy[6776]: 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 14 16:38:39 node-1 haproxy[6776]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:39 node-1 haproxy[6776]: 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 14 16:38:39 node-1 haproxy[6776]: proxy keystone-2 has no server available!
<129>Sep 14 16:38:39 node-1 haproxy[6776]: 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 14 16:38:39 node-1 haproxy[6776]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:39 node-1 haproxy[6776]: 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 14 16:38:39 node-1 haproxy[6776]: proxy nova-api has no server available!
<129>Sep 14 16:38:39 node-1 haproxy[6776]: 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 14 16:38:39 node-1 haproxy[6776]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:39 node-1 haproxy[6776]: 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 14 16:38:39 node-1 haproxy[6776]: proxy nova-metadata-api has no server available!
<129>Sep 14 16:38:39 node-1 haproxy[6776]: 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 14 16:38:39 node-1 haproxy[6776]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:39 node-1 haproxy[6776]: 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 14 16:38:39 node-1 haproxy[6776]: proxy cinder-api has no server available!
<129>Sep 14 16:38:39 node-1 haproxy[6776]: 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 14 16:38:39 node-1 haproxy[6776]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:39 node-1 haproxy[6776]: 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 14 16:38:39 node-1 haproxy[6776]: proxy glance-api has no server available!
<129>Sep 14 16:38:39 node-1 haproxy[6776]: 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 14 16:38:39 node-1 haproxy[6776]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:39 node-1 haproxy[6776]: 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 14 16:38:39 node-1 haproxy[6776]: proxy glance-glare has no server available!
<129>Sep 14 16:38:39 node-1 haproxy[6776]: 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 14 16:38:40 node-1 haproxy[6780]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: proxy neutron has no server available!
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: proxy glance-registry has no server available!
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: proxy mysqld has no server available!
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: proxy object-storage has no server available!
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: proxy aodh has no server available!
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: proxy ceilometer has no server available!
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: proxy heat-api has no server available!
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: proxy heat-api-cfn has no server available!
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:40 node-1 haproxy[6780]: proxy heat-api-cloudwatch has no server available!
<129>Sep 14 16:38:40 node-1 haproxy[6780]: 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 14 16:38:41 node-1 haproxy[6780]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 16:38:41 node-1 haproxy[6780]: 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 14 16:38:41 node-1 haproxy[6780]: proxy nova-novncproxy has no server available!
<27>Sep 14 16:38:42 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:42 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:42 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:42 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:42 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:38:55 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 14 16:39:21 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 14 16:39:23 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 14 16:39:53 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 14 16:39:56 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 14 16:40:21 node-1 multipathd: uevent trigger error
<27>Sep 14 16:40:21 node-1 multipathd: uevent trigger error
<27>Sep 14 16:40:21 node-1 multipathd: uevent trigger error
<27>Sep 14 16:40:21 node-1 multipathd: uevent trigger error
<27>Sep 14 16:40:21 node-1 multipathd: uevent trigger error
<27>Sep 14 16:42:39 node-1 multipathd: uevent trigger error
<27>Sep 14 16:42:39 node-1 multipathd: uevent trigger error
<27>Sep 14 16:42:39 node-1 multipathd: uevent trigger error
<27>Sep 14 16:42:39 node-1 multipathd: uevent trigger error
<27>Sep 14 16:42:39 node-1 multipathd: uevent trigger error
<27>Sep 14 16:42:39 node-1 multipathd: uevent trigger error
<27>Sep 14 16:42:46 node-1 multipathd: uevent trigger error
<27>Sep 14 16:42:46 node-1 multipathd: uevent trigger error
<27>Sep 14 16:42:46 node-1 multipathd: uevent trigger error
<27>Sep 14 16:42:46 node-1 multipathd: uevent trigger error
<27>Sep 14 16:43:00 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 14 16:43:00 node-1 apache2_error [Wed Sep 14 16:43:00.222038 2016] [mpm_event:notice] [pid 16699:tid 139642662438784] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 14 16:43:00 node-1 apache2_error [Wed Sep 14 16:43:00.222200 2016] [core:notice] [pid 16699:tid 139642662438784] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 14 16:43:08 node-1 multipathd: uevent trigger error
<27>Sep 14 16:43:08 node-1 multipathd: uevent trigger error
<27>Sep 14 16:43:08 node-1 multipathd: uevent trigger error
<27>Sep 14 16:43:08 node-1 multipathd: uevent trigger error
<27>Sep 14 16:43:08 node-1 multipathd: uevent trigger error
<43>Sep 14 16:43:10 node-1 apache2_error [Wed Sep 14 16:43:03.523904 2016] [mpm_event:notice] [pid 16699:tid 139642662438784] AH00491: caught SIGTERM, shutting down
<43>Sep 14 16:43:10 node-1 apache2_error [Wed Sep 14 16:43:04.614261 2016] [mpm_worker:notice] [pid 17094:tid 140429651830656] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 14 16:43:10 node-1 apache2_error [Wed Sep 14 16:43:04.614395 2016] [core:notice] [pid 17094:tid 140429651830656] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 14 16:43:13 node-1 multipathd: uevent trigger error
<27>Sep 14 16:43:13 node-1 multipathd: uevent trigger error
<27>Sep 14 16:43:13 node-1 multipathd: uevent trigger error
<27>Sep 14 16:43:13 node-1 multipathd: uevent trigger error
<27>Sep 14 16:43:13 node-1 multipathd: uevent trigger error
<27>Sep 14 16:43:16 node-1 multipathd: uevent trigger error
<27>Sep 14 16:43:16 node-1 multipathd: uevent trigger error
<27>Sep 14 16:43:16 node-1 multipathd: uevent trigger error
<27>Sep 14 16:43:16 node-1 multipathd: uevent trigger error
<27>Sep 14 16:43:16 node-1 multipathd: uevent trigger error
<27>Sep 14 16:43:17 node-1 multipathd: uevent trigger error
<43>Sep 14 16:44:41 node-1 apache2_error [Wed Sep 14 16:44:32.328632 2016] [mpm_worker:notice] [pid 17094:tid 140429651830656] AH00295: caught SIGTERM, shutting down
<43>Sep 14 16:44:41 node-1 apache2_error [Wed Sep 14 16:44:33.076795 2016] [mpm_worker:notice] [pid 923:tid 140236098316160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 14 16:44:41 node-1 apache2_error [Wed Sep 14 16:44:33.076830 2016] [core:notice] [pid 923:tid 140236098316160] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 14 16:45:21 node-1 apache2_error [Wed Sep 14 16:45:18.699859 2016] [mpm_worker:notice] [pid 923:tid 140236098316160] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 14 16:45:21 node-1 apache2_error [Wed Sep 14 16:45:18.895674 2016] [mpm_worker:warn] [pid 923:tid 140236098316160] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 14 16:45:21 node-1 apache2_error [Wed Sep 14 16:45:18.900141 2016] [mpm_worker:notice] [pid 923:tid 140236098316160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 14 16:45:21 node-1 apache2_error [Wed Sep 14 16:45:18.900169 2016] [core:notice] [pid 923:tid 140236098316160] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 14 16:46:01 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 14 16:46:03 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:03 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:03 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:03 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:03 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:03 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:07 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:07 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:07 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:07 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:07 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:07 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:23 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:23 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:23 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:23 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:23 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:44 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:44 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:44 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:44 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:44 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:44 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:49 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:49 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:49 node-1 multipathd: uevent trigger error
<27>Sep 14 16:46:49 node-1 multipathd: uevent trigger error
<27>Sep 14 16:47:37 node-1 multipathd: uevent trigger error
<27>Sep 14 16:47:37 node-1 multipathd: uevent trigger error
<27>Sep 14 16:47:37 node-1 multipathd: uevent trigger error
<27>Sep 14 16:47:37 node-1 multipathd: uevent trigger error
<27>Sep 14 16:47:37 node-1 multipathd: uevent trigger error
<27>Sep 14 16:47:51 node-1 multipathd: uevent trigger error
<27>Sep 14 16:47:51 node-1 multipathd: uevent trigger error
<27>Sep 14 16:47:51 node-1 multipathd: uevent trigger error
<27>Sep 14 16:47:51 node-1 multipathd: uevent trigger error
<27>Sep 14 16:48:46 node-1 multipathd: uevent trigger error
<27>Sep 14 16:48:46 node-1 multipathd: uevent trigger error
<27>Sep 14 16:48:46 node-1 multipathd: uevent trigger error
<27>Sep 14 16:48:46 node-1 multipathd: uevent trigger error
<27>Sep 14 16:48:46 node-1 multipathd: uevent trigger error
<27>Sep 14 16:49:05 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 14 16:50:00 node-1 multipathd: uevent trigger error
<27>Sep 14 16:50:00 node-1 multipathd: uevent trigger error
<27>Sep 14 16:50:00 node-1 multipathd: uevent trigger error
<27>Sep 14 16:50:00 node-1 multipathd: uevent trigger error
<27>Sep 14 16:50:00 node-1 multipathd: uevent trigger error
<27>Sep 14 16:50:00 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:03 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:03 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:03 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:03 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:03 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:03 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:09 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:09 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:09 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:09 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:09 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:09 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:09 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:09 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:09 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:34 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:34 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:34 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:34 node-1 multipathd: uevent trigger error
<27>Sep 14 16:51:34 node-1 multipathd: uevent trigger error
<27>Sep 14 16:52:07 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 14 16:54:10 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:10 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:10 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:10 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:10 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:26 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:26 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:26 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:26 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:26 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:26 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:31 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:31 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:31 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:31 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:31 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:31 node-1 multipathd: uevent trigger error
<27>Sep 14 16:54:31 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:09 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 14 16:55:15 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:15 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:15 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:15 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:15 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:15 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:15 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:20 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:20 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:20 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:20 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:20 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:55:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:35 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:35 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:36 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:36 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:36 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:36 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:43 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Sep 14 16:56:43 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Sep 14 16:56:43 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Sep 14 16:56:44 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Sep 14 16:56:44 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Sep 14 16:56:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:45 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:58 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:58 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:58 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:58 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:58 node-1 multipathd: uevent trigger error
<27>Sep 14 16:56:58 node-1 multipathd: uevent trigger error
<27>Sep 14 16:57:13 node-1 multipathd: uevent trigger error
<27>Sep 14 16:57:13 node-1 multipathd: uevent trigger error
<27>Sep 14 16:57:13 node-1 multipathd: uevent trigger error
<27>Sep 14 16:57:13 node-1 multipathd: uevent trigger error
<27>Sep 14 16:57:13 node-1 multipathd: uevent trigger error
<27>Sep 14 16:57:33 node-1 multipathd: uevent trigger error
<27>Sep 14 16:57:33 node-1 multipathd: uevent trigger error
<27>Sep 14 16:57:33 node-1 multipathd: uevent trigger error
<27>Sep 14 16:57:33 node-1 multipathd: uevent trigger error
<27>Sep 14 16:57:33 node-1 multipathd: uevent trigger error
<27>Sep 14 16:57:33 node-1 multipathd: uevent trigger error
<27>Sep 14 16:58:10 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 14 17:00:00 node-1 multipathd: uevent trigger error
<27>Sep 14 17:00:00 node-1 multipathd: uevent trigger error
<27>Sep 14 17:00:00 node-1 multipathd: uevent trigger error
<27>Sep 14 17:00:00 node-1 multipathd: uevent trigger error
<27>Sep 14 17:00:00 node-1 multipathd: uevent trigger error
<27>Sep 14 17:00:52 node-1 multipathd: uevent trigger error
<27>Sep 14 17:00:52 node-1 multipathd: uevent trigger error
<27>Sep 14 17:00:52 node-1 multipathd: uevent trigger error
<27>Sep 14 17:00:52 node-1 multipathd: uevent trigger error
<27>Sep 14 17:00:52 node-1 multipathd: uevent trigger error
<27>Sep 14 17:00:57 node-1 multipathd: uevent trigger error
<27>Sep 14 17:00:57 node-1 multipathd: uevent trigger error
<27>Sep 14 17:00:57 node-1 multipathd: uevent trigger error
<27>Sep 14 17:00:57 node-1 multipathd: uevent trigger error
<27>Sep 14 17:00:57 node-1 multipathd: uevent trigger error
<27>Sep 14 17:01:12 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 14 17:01:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:01:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:01:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:01:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:01:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:01:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:01:45 node-1 multipathd: uevent trigger error
<27>Sep 14 17:01:45 node-1 multipathd: uevent trigger error
<27>Sep 14 17:01:45 node-1 multipathd: uevent trigger error
<27>Sep 14 17:01:45 node-1 multipathd: uevent trigger error
<27>Sep 14 17:01:50 node-1 multipathd: uevent trigger error
<27>Sep 14 17:01:50 node-1 multipathd: uevent trigger error
<27>Sep 14 17:01:50 node-1 multipathd: uevent trigger error
<27>Sep 14 17:01:50 node-1 multipathd: uevent trigger error
<27>Sep 14 17:01:50 node-1 multipathd: uevent trigger error
<27>Sep 14 17:02:02 node-1 multipathd: uevent trigger error
<27>Sep 14 17:02:02 node-1 multipathd: uevent trigger error
<27>Sep 14 17:02:02 node-1 multipathd: uevent trigger error
<27>Sep 14 17:02:02 node-1 multipathd: uevent trigger error
<27>Sep 14 17:02:02 node-1 multipathd: uevent trigger error
<27>Sep 14 17:02:09 node-1 multipathd: uevent trigger error
<27>Sep 14 17:02:09 node-1 multipathd: uevent trigger error
<27>Sep 14 17:02:09 node-1 multipathd: uevent trigger error
<27>Sep 14 17:02:09 node-1 multipathd: uevent trigger error
<27>Sep 14 17:02:09 node-1 multipathd: uevent trigger error
<27>Sep 14 17:02:09 node-1 multipathd: uevent trigger error
<27>Sep 14 17:02:43 node-1 multipathd: uevent trigger error
<27>Sep 14 17:02:43 node-1 multipathd: uevent trigger error
<27>Sep 14 17:02:43 node-1 multipathd: uevent trigger error
<27>Sep 14 17:02:43 node-1 multipathd: uevent trigger error
<27>Sep 14 17:02:43 node-1 multipathd: uevent trigger error
<27>Sep 14 17:03:50 node-1 multipathd: uevent trigger error
<27>Sep 14 17:03:50 node-1 multipathd: uevent trigger error
<27>Sep 14 17:03:50 node-1 multipathd: uevent trigger error
<27>Sep 14 17:03:50 node-1 multipathd: uevent trigger error
<27>Sep 14 17:03:50 node-1 multipathd: uevent trigger error
<27>Sep 14 17:04:09 node-1 multipathd: uevent trigger error
<27>Sep 14 17:04:09 node-1 multipathd: uevent trigger error
<27>Sep 14 17:04:09 node-1 multipathd: uevent trigger error
<27>Sep 14 17:04:09 node-1 multipathd: uevent trigger error
<27>Sep 14 17:04:13 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<11>Sep 14 17:04:23 node-1 liberasurecode[5335]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:23 node-1 liberasurecode[5335]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:23 node-1 liberasurecode[5335]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:23 node-1 liberasurecode[5335]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:23 node-1 liberasurecode[5362]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:23 node-1 liberasurecode[5362]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:23 node-1 liberasurecode[5362]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:23 node-1 liberasurecode[5362]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:25 node-1 liberasurecode[6643]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:25 node-1 liberasurecode[6643]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:25 node-1 liberasurecode[6643]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:25 node-1 liberasurecode[6643]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8698]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8698]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8698]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8698]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8745]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8745]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8745]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8745]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8797]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8797]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8797]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8797]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8860]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8860]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8860]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8860]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8873]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8873]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8873]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8873]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8885]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8885]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8885]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8885]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8906]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8906]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8906]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:31 node-1 liberasurecode[8906]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:48 node-1 liberasurecode[9854]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:48 node-1 liberasurecode[9854]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:48 node-1 liberasurecode[9854]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:04:48 node-1 liberasurecode[9854]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 14 17:04:56 node-1 multipathd: uevent trigger error
<27>Sep 14 17:04:56 node-1 multipathd: uevent trigger error
<27>Sep 14 17:04:56 node-1 multipathd: uevent trigger error
<27>Sep 14 17:04:56 node-1 multipathd: uevent trigger error
<27>Sep 14 17:04:56 node-1 multipathd: uevent trigger error
<11>Sep 14 17:05:01 node-1 liberasurecode[13334]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:05:01 node-1 liberasurecode[13334]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:05:01 node-1 liberasurecode[13334]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:05:01 node-1 liberasurecode[13334]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Sep 14 17:05:52 node-1 apache2_error [Wed Sep 14 17:05:43.622282 2016] [mpm_worker:notice] [pid 923:tid 140236098316160] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 14 17:05:52 node-1 apache2_error [Wed Sep 14 17:05:44.006811 2016] [mpm_worker:warn] [pid 923:tid 140236098316160] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 14 17:05:52 node-1 apache2_error [Wed Sep 14 17:05:44.012564 2016] [mpm_worker:notice] [pid 923:tid 140236098316160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 14 17:05:52 node-1 apache2_error [Wed Sep 14 17:05:44.012608 2016] [core:notice] [pid 923:tid 140236098316160] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 14 17:06:22 node-1 apache2_error [Wed Sep 14 17:06:20.958708 2016] [mpm_worker:notice] [pid 923:tid 140236098316160] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 14 17:06:22 node-1 apache2_error [Wed Sep 14 17:06:21.155184 2016] [mpm_worker:warn] [pid 923:tid 140236098316160] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 14 17:06:22 node-1 apache2_error [Wed Sep 14 17:06:21.163148 2016] [mpm_worker:notice] [pid 923:tid 140236098316160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 14 17:06:22 node-1 apache2_error [Wed Sep 14 17:06:21.163186 2016] [core:notice] [pid 923:tid 140236098316160] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 14 17:06:25 node-1 multipathd: uevent trigger error
<27>Sep 14 17:06:25 node-1 multipathd: uevent trigger error
<27>Sep 14 17:06:25 node-1 multipathd: uevent trigger error
<27>Sep 14 17:06:25 node-1 multipathd: uevent trigger error
<27>Sep 14 17:06:25 node-1 multipathd: uevent trigger error
<27>Sep 14 17:06:32 node-1 multipathd: uevent trigger error
<27>Sep 14 17:06:32 node-1 multipathd: uevent trigger error
<27>Sep 14 17:06:32 node-1 multipathd: uevent trigger error
<27>Sep 14 17:06:32 node-1 multipathd: uevent trigger error
<27>Sep 14 17:06:33 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:11 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:11 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:11 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:11 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:11 node-1 multipathd: uevent trigger error
<43>Sep 14 17:07:13 node-1 apache2_error [Wed Sep 14 17:07:07.369471 2016] [mpm_worker:notice] [pid 923:tid 140236098316160] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 14 17:07:13 node-1 apache2_error [Wed Sep 14 17:07:07.567696 2016] [mpm_worker:warn] [pid 923:tid 140236098316160] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 14 17:07:13 node-1 apache2_error [Wed Sep 14 17:07:07.580070 2016] [mpm_worker:notice] [pid 923:tid 140236098316160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 14 17:07:13 node-1 apache2_error [Wed Sep 14 17:07:07.580111 2016] [core:notice] [pid 923:tid 140236098316160] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 14 17:07:15 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 14 17:07:18 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:18 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:18 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:18 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:18 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:24 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:24 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:24 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:24 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:24 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:35 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:35 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:35 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:35 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:35 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:48 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:48 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:48 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:48 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:48 node-1 multipathd: uevent trigger error
<27>Sep 14 17:07:48 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:12 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:20 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 14 17:08:29 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:29 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:29 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:29 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:29 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:33 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:33 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:33 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:33 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:33 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:33 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:38 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:38 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:38 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:38 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:38 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:44 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:44 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:44 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:44 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:44 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:56 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:56 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:56 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:56 node-1 multipathd: uevent trigger error
<27>Sep 14 17:08:56 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:11 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:11 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:11 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:11 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:11 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:16 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 14 17:09:24 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:24 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:24 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:24 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:24 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:31 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:31 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:31 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:31 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:31 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:36 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:36 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:36 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:36 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:36 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:46 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:46 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:46 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:46 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:46 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:51 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:51 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:51 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:51 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:51 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:56 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:56 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:56 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:56 node-1 multipathd: uevent trigger error
<27>Sep 14 17:09:56 node-1 multipathd: uevent trigger error
<27>Sep 14 17:10:01 node-1 multipathd: uevent trigger error
<27>Sep 14 17:10:01 node-1 multipathd: uevent trigger error
<27>Sep 14 17:10:01 node-1 multipathd: uevent trigger error
<27>Sep 14 17:10:01 node-1 multipathd: uevent trigger error
<27>Sep 14 17:10:01 node-1 multipathd: uevent trigger error
<11>Sep 14 17:10:02 node-1 liberasurecode[22096]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:10:02 node-1 liberasurecode[22096]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:10:02 node-1 liberasurecode[22096]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:10:02 node-1 liberasurecode[22096]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 14 17:11:21 node-1 multipathd: uevent trigger error
<27>Sep 14 17:11:21 node-1 multipathd: uevent trigger error
<27>Sep 14 17:11:21 node-1 multipathd: uevent trigger error
<27>Sep 14 17:11:21 node-1 multipathd: uevent trigger error
<27>Sep 14 17:11:21 node-1 multipathd: uevent trigger error
<27>Sep 14 17:11:29 node-1 multipathd: uevent trigger error
<27>Sep 14 17:11:29 node-1 multipathd: uevent trigger error
<27>Sep 14 17:11:29 node-1 multipathd: uevent trigger error
<27>Sep 14 17:11:29 node-1 multipathd: uevent trigger error
<27>Sep 14 17:11:29 node-1 multipathd: uevent trigger error
<27>Sep 14 17:11:40 node-1 multipathd: uevent trigger error
<27>Sep 14 17:11:40 node-1 multipathd: uevent trigger error
<27>Sep 14 17:11:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:11:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:11:41 node-1 multipathd: uevent trigger error
<129>Sep 14 17:11:50 node-1 haproxy[31590]: 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 14 17:11:51 node-1 haproxy[31590]: 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.
<129>Sep 14 17:12:30 node-1 haproxy[31590]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 14 17:12:35 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:35 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:35 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:35 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:35 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:41 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:46 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:46 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:46 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:46 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:46 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:46 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:58 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:58 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:58 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:58 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:58 node-1 multipathd: uevent trigger error
<27>Sep 14 17:12:58 node-1 multipathd: uevent trigger error
<11>Sep 14 17:15:01 node-1 liberasurecode[647]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:15:01 node-1 liberasurecode[647]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:15:01 node-1 liberasurecode[647]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 17:15:01 node-1 liberasurecode[647]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
