Sep  3 15:48:01 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8426" x-info="http://www.rsyslog.com"] start
Sep  3 15:48:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep  3 15:48:01 node-1 rsyslogd: rsyslogd's groupid changed to 104
Sep  3 15:48:01 node-1 rsyslogd: rsyslogd's userid changed to 101
Sep  3 15:48:01 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep  3 15:48:01 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep  3 15:48:01 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep  3 15:48:01 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  3 15:48:01 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=4bfc0f3d-95a2-4559-99bc-e107e1f668b9 nomdmonddf nomdmonisw
Sep  3 15:48:01 node-1 kernel: [    0.000000] KERNEL supported cpus:
Sep  3 15:48:01 node-1 kernel: [    0.000000]   Intel GenuineIntel
Sep  3 15:48:01 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Sep  3 15:48:01 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Sep  3 15:48:01 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep  3 15:48:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep  3 15:48:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep  3 15:48:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep  3 15:48:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep  3 15:48:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep  3 15:48:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep  3 15:48:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep  3 15:48:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep  3 15:48:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep  3 15:48:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep  3 15:48:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep  3 15:48:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep  3 15:48:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep  3 15:48:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep  3 15:48:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep  3 15:48:01 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep  3 15:48:01 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Sep  3 15:48:01 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  3 15:48:01 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep  3 15:48:01 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep  3 15:48:01 node-1 kernel: [    0.000000] No AGP bridge found
Sep  3 15:48:01 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep  3 15:48:01 node-1 kernel: [    0.000000] MTRR default type: write-back
Sep  3 15:48:01 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep  3 15:48:01 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Sep  3 15:48:01 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep  3 15:48:01 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep  3 15:48:01 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Sep  3 15:48:01 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep  3 15:48:01 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep  3 15:48:01 node-1 kernel: [    0.000000]   2 disabled
Sep  3 15:48:01 node-1 kernel: [    0.000000]   3 disabled
Sep  3 15:48:01 node-1 kernel: [    0.000000]   4 disabled
Sep  3 15:48:01 node-1 kernel: [    0.000000]   5 disabled
Sep  3 15:48:01 node-1 kernel: [    0.000000]   6 disabled
Sep  3 15:48:01 node-1 kernel: [    0.000000]   7 disabled
Sep  3 15:48:01 node-1 kernel: [    0.000000]   8 disabled
Sep  3 15:48:01 node-1 kernel: [    0.000000]   9 disabled
Sep  3 15:48:01 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep  3 15:48:01 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep  3 15:48:01 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep  3 15:48:01 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep  3 15:48:01 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep  3 15:48:01 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Sep  3 15:48:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep  3 15:48:01 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep  3 15:48:01 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep  3 15:48:01 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep  3 15:48:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep  3 15:48:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep  3 15:48:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep  3 15:48:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep  3 15:48:01 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep  3 15:48:01 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep  3 15:48:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep  3 15:48:01 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep  3 15:48:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep  3 15:48:01 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep  3 15:48:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep  3 15:48:01 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35826000-0x36c0afff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep  3 15:48:01 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep  3 15:48:01 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep  3 15:48:01 node-1 kernel: [    0.000000] Zone ranges:
Sep  3 15:48:01 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] Movable zone start for each node
Sep  3 15:48:01 node-1 kernel: [    0.000000] Early memory node ranges
Sep  3 15:48:01 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep  3 15:48:01 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep  3 15:48:01 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep  3 15:48:01 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep  3 15:48:01 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep  3 15:48:01 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep  3 15:48:01 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep  3 15:48:01 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep  3 15:48:01 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep  3 15:48:01 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep  3 15:48:01 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep  3 15:48:01 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep  3 15:48:01 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep  3 15:48:01 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep  3 15:48:01 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep  3 15:48:01 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep  3 15:48:01 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep  3 15:48:01 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Sep  3 15:48:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep  3 15:48:01 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep  3 15:48:01 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep  3 15:48:01 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep  3 15:48:01 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep  3 15:48:01 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep  3 15:48:01 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  3 15:48:01 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep  3 15:48:01 node-1 kernel: [    0.000000] Policy zone: Normal
Sep  3 15:48:01 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=4bfc0f3d-95a2-4559-99bc-e107e1f668b9 nomdmonddf nomdmonisw
Sep  3 15:48:01 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep  3 15:48:01 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep  3 15:48:01 node-1 kernel: [    0.000000] Checking aperture...
Sep  3 15:48:01 node-1 kernel: [    0.000000] No AGP bridge found
Sep  3 15:48:01 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep  3 15:48:01 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep  3 15:48:01 node-1 kernel: [    0.000000] Memory: 32653324K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627172K reserved)
Sep  3 15:48:01 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep  3 15:48:01 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Sep  3 15:48:01 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep  3 15:48:01 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep  3 15:48:01 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep  3 15:48:01 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep  3 15:48:01 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep  3 15:48:01 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Sep  3 15:48:01 node-1 kernel: [    0.000000] console [tty0] enabled
Sep  3 15:48:01 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep  3 15:48:01 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep  3 15:48:01 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep  3 15:48:01 node-1 kernel: [    0.000000] hpet clockevent registered
Sep  3 15:48:01 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep  3 15:48:01 node-1 kernel: [    0.004000] tsc: Detected 3492.036 MHz processor
Sep  3 15:48:01 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.07 BogoMIPS (lpj=13968144)
Sep  3 15:48:01 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep  3 15:48:01 node-1 kernel: [    0.000049] Security Framework initialized
Sep  3 15:48:01 node-1 kernel: [    0.000069] AppArmor: AppArmor initialized
Sep  3 15:48:01 node-1 kernel: [    0.000070] Yama: becoming mindful.
Sep  3 15:48:01 node-1 kernel: [    0.001464] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep  3 15:48:01 node-1 kernel: [    0.006383] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep  3 15:48:01 node-1 kernel: [    0.008313] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep  3 15:48:01 node-1 kernel: [    0.008341] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep  3 15:48:01 node-1 kernel: [    0.008631] Initializing cgroup subsys memory
Sep  3 15:48:01 node-1 kernel: [    0.008640] Initializing cgroup subsys devices
Sep  3 15:48:01 node-1 kernel: [    0.008642] Initializing cgroup subsys freezer
Sep  3 15:48:01 node-1 kernel: [    0.008644] Initializing cgroup subsys blkio
Sep  3 15:48:01 node-1 kernel: [    0.008646] Initializing cgroup subsys perf_event
Sep  3 15:48:01 node-1 kernel: [    0.008648] Initializing cgroup subsys hugetlb
Sep  3 15:48:01 node-1 kernel: [    0.008668] CPU: Physical Processor ID: 0
Sep  3 15:48:01 node-1 kernel: [    0.008669] CPU: Processor Core ID: 0
Sep  3 15:48:01 node-1 kernel: [    0.008673] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep  3 15:48:01 node-1 kernel: [    0.008673] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep  3 15:48:01 node-1 kernel: [    0.009366] mce: CPU supports 22 MCE banks
Sep  3 15:48:01 node-1 kernel: [    0.009393] CPU0: Thermal monitoring enabled (TM1)
Sep  3 15:48:01 node-1 kernel: [    0.009414] process: using mwait in idle threads
Sep  3 15:48:01 node-1 kernel: [    0.009417] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep  3 15:48:01 node-1 kernel: [    0.009417] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep  3 15:48:01 node-1 kernel: [    0.009417] tlb_flushall_shift: 6
Sep  3 15:48:01 node-1 kernel: [    0.009506] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep  3 15:48:01 node-1 kernel: [    0.010226] ACPI: Core revision 20131115
Sep  3 15:48:01 node-1 kernel: [    0.022898] ACPI: All ACPI Tables successfully acquired
Sep  3 15:48:01 node-1 kernel: [    0.023060] ftrace: allocating 28617 entries in 112 pages
Sep  3 15:48:01 node-1 kernel: [    0.032028] dmar: Host address width 46
Sep  3 15:48:01 node-1 kernel: [    0.032030] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep  3 15:48:01 node-1 kernel: [    0.032036] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep  3 15:48:01 node-1 kernel: [    0.032038] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep  3 15:48:01 node-1 kernel: [    0.032042] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep  3 15:48:01 node-1 kernel: [    0.032043] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep  3 15:48:01 node-1 kernel: [    0.032044] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep  3 15:48:01 node-1 kernel: [    0.032045] dmar: ATSR flags: 0x0
Sep  3 15:48:01 node-1 kernel: [    0.032047] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep  3 15:48:01 node-1 kernel: [    0.032048] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep  3 15:48:01 node-1 kernel: [    0.032164] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep  3 15:48:01 node-1 kernel: [    0.032165] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep  3 15:48:01 node-1 kernel: [    0.032166] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep  3 15:48:01 node-1 kernel: [    0.032167] HPET id 0 under DRHD base 0xc7ffc000
Sep  3 15:48:01 node-1 kernel: [    0.032168] Your BIOS is broken and requested that x2apic be disabled.
Sep  3 15:48:01 node-1 kernel: [    0.032168] This will slightly decrease performance.
Sep  3 15:48:01 node-1 kernel: [    0.032168] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep  3 15:48:01 node-1 kernel: [    0.032599] Enabled IRQ remapping in xapic mode
Sep  3 15:48:01 node-1 kernel: [    0.032600] x2apic not enabled, IRQ remapping is in xapic mode
Sep  3 15:48:01 node-1 kernel: [    0.032604] Switched APIC routing to physical flat.
Sep  3 15:48:01 node-1 kernel: [    0.033233] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep  3 15:48:01 node-1 kernel: [    0.072885] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep  3 15:48:01 node-1 kernel: [    0.072890] TSC deadline timer enabled
Sep  3 15:48:01 node-1 kernel: [    0.072898] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep  3 15:48:01 node-1 kernel: [    0.072904] ... version:                3
Sep  3 15:48:01 node-1 kernel: [    0.072905] ... bit width:              48
Sep  3 15:48:01 node-1 kernel: [    0.072906] ... generic registers:      4
Sep  3 15:48:01 node-1 kernel: [    0.072907] ... value mask:             0000ffffffffffff
Sep  3 15:48:01 node-1 kernel: [    0.072908] ... max period:             0000ffffffffffff
Sep  3 15:48:01 node-1 kernel: [    0.072909] ... fixed-purpose events:   3
Sep  3 15:48:01 node-1 kernel: [    0.072909] ... event mask:             000000070000000f
Sep  3 15:48:01 node-1 kernel: [    0.074311] x86: Booting SMP configuration:
Sep  3 15:48:01 node-1 kernel: [    0.088520] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep  3 15:48:01 node-1 kernel: [    0.074313] .... node  #0, CPUs:        #1  #2  #3
Sep  3 15:48:01 node-1 kernel: [    0.116446] .... node  #1, CPUs:    #4  #5  #6  #7
Sep  3 15:48:01 node-1 kernel: [    0.270596] .... node  #0, CPUs:    #8  #9 #10 #11
Sep  3 15:48:01 node-1 kernel: [    0.326210] .... node  #1, CPUs:   #12 #13 #14 #15
Sep  3 15:48:01 node-1 kernel: [    0.382868] x86: Booted up 2 nodes, 16 CPUs
Sep  3 15:48:01 node-1 kernel: [    0.382871] smpboot: Total of 16 processors activated (111757.42 BogoMIPS)
Sep  3 15:48:01 node-1 kernel: [    0.406147] devtmpfs: initialized
Sep  3 15:48:01 node-1 kernel: [    0.409289] EVM: security.selinux
Sep  3 15:48:01 node-1 kernel: [    0.409291] EVM: security.SMACK64
Sep  3 15:48:01 node-1 kernel: [    0.409292] EVM: security.ima
Sep  3 15:48:01 node-1 kernel: [    0.409292] EVM: security.capability
Sep  3 15:48:01 node-1 kernel: [    0.409342] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep  3 15:48:01 node-1 kernel: [    0.410016] pinctrl core: initialized pinctrl subsystem
Sep  3 15:48:01 node-1 kernel: [    0.410077] regulator-dummy: no parameters
Sep  3 15:48:01 node-1 kernel: [    0.410109] RTC time: 15:47:24, date: 09/03/16
Sep  3 15:48:01 node-1 kernel: [    0.410142] NET: Registered protocol family 16
Sep  3 15:48:01 node-1 kernel: [    0.410225] cpuidle: using governor ladder
Sep  3 15:48:01 node-1 kernel: [    0.410226] cpuidle: using governor menu
Sep  3 15:48:01 node-1 kernel: [    0.410261] ACPI: bus type PCI registered
Sep  3 15:48:01 node-1 kernel: [    0.410263] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep  3 15:48:01 node-1 kernel: [    0.410306] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep  3 15:48:01 node-1 kernel: [    0.410309] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep  3 15:48:01 node-1 kernel: [    0.424036] PCI: Using configuration type 1 for base access
Sep  3 15:48:01 node-1 kernel: [    0.425019] bio: create slab <bio-0> at 0
Sep  3 15:48:01 node-1 kernel: [    0.425295] ACPI: Added _OSI(Module Device)
Sep  3 15:48:01 node-1 kernel: [    0.425297] ACPI: Added _OSI(Processor Device)
Sep  3 15:48:01 node-1 kernel: [    0.425298] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep  3 15:48:01 node-1 kernel: [    0.425299] ACPI: Added _OSI(Processor Aggregator Device)
Sep  3 15:48:01 node-1 kernel: [    0.437955] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep  3 15:48:01 node-1 kernel: [    0.448444] ACPI: Interpreter enabled
Sep  3 15:48:01 node-1 kernel: [    0.448449] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep  3 15:48:01 node-1 kernel: [    0.448453] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep  3 15:48:01 node-1 kernel: [    0.448456] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep  3 15:48:01 node-1 kernel: [    0.448463] ACPI: (supports S0 S4 S5)
Sep  3 15:48:01 node-1 kernel: [    0.448464] ACPI: Using IOAPIC for interrupt routing
Sep  3 15:48:01 node-1 kernel: [    0.448509] HEST: Table parsing has been initialized.
Sep  3 15:48:01 node-1 kernel: [    0.448512] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep  3 15:48:01 node-1 kernel: [    0.449067] ACPI: No dock devices found.
Sep  3 15:48:01 node-1 kernel: [    0.460749] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep  3 15:48:01 node-1 kernel: [    0.460754] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep  3 15:48:01 node-1 kernel: [    0.460757] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep  3 15:48:01 node-1 kernel: [    0.460784] PCI host bridge to bus 0000:ff
Sep  3 15:48:01 node-1 kernel: [    0.460786] pci_bus 0000:ff: root bus resource [bus ff]
Sep  3 15:48:01 node-1 kernel: [    0.460794] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep  3 15:48:01 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep  3 15:48:01 node-1 kernel: [    0.460834] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep  3 15:48:01 node-1 kernel: [    0.460864] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.460899] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.460928] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep  3 15:48:01 node-1 kernel: [    0.460956] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep  3 15:48:01 node-1 kernel: [    0.460987] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461016] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461046] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461074] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461100] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461127] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461155] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461180] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461207] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461233] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461262] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461289] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461315] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep  3 15:48:01 node-1 kernel: [    0.461343] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461369] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep  3 15:48:01 node-1 kernel: [    0.461395] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461421] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461450] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep  3 15:48:01 node-1 kernel: [    0.461488] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461521] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461550] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461583] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461616] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461649] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461682] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461712] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461742] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461773] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461804] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461837] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461870] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461901] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461929] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461961] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.461993] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462032] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462067] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462101] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462132] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462161] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462193] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462224] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462255] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462286] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462318] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462348] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462378] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462408] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462438] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462470] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462502] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462560] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep  3 15:48:01 node-1 kernel: [    0.462563] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep  3 15:48:01 node-1 kernel: [    0.462566] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep  3 15:48:01 node-1 kernel: [    0.462587] PCI host bridge to bus 0000:7f
Sep  3 15:48:01 node-1 kernel: [    0.462588] pci_bus 0000:7f: root bus resource [bus 7f]
Sep  3 15:48:01 node-1 kernel: [    0.462593] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462621] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep  3 15:48:01 node-1 kernel: [    0.462651] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462680] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462702] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep  3 15:48:01 node-1 kernel: [    0.462726] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep  3 15:48:01 node-1 kernel: [    0.462756] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462782] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462807] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462833] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462858] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462883] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462908] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462930] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462954] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.462980] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463002] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463025] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463048] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep  3 15:48:01 node-1 kernel: [    0.463072] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463094] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep  3 15:48:01 node-1 kernel: [    0.463116] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463139] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463165] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep  3 15:48:01 node-1 kernel: [    0.463199] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463225] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463252] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463279] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463304] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463332] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463360] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463390] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463415] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463442] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463468] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463496] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463525] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463553] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463578] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463607] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463633] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463661] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463691] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463720] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463746] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463771] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463797] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463825] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463852] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463879] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463908] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463934] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463957] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.463982] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.464008] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.464036] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.464062] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.465316] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep  3 15:48:01 node-1 kernel: [    0.465319] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep  3 15:48:01 node-1 kernel: [    0.466437] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep  3 15:48:01 node-1 kernel: [    0.466948] PCI host bridge to bus 0000:00
Sep  3 15:48:01 node-1 kernel: [    0.466950] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep  3 15:48:01 node-1 kernel: [    0.466952] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep  3 15:48:01 node-1 kernel: [    0.466953] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep  3 15:48:01 node-1 kernel: [    0.466954] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep  3 15:48:01 node-1 kernel: [    0.466956] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep  3 15:48:01 node-1 kernel: [    0.466957] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep  3 15:48:01 node-1 kernel: [    0.466959] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep  3 15:48:01 node-1 kernel: [    0.466964] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep  3 15:48:01 node-1 kernel: [    0.467047] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep  3 15:48:01 node-1 kernel: [    0.467078] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep  3 15:48:01 node-1 kernel: [    0.467119] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep  3 15:48:01 node-1 kernel: [    0.467139] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep  3 15:48:01 node-1 kernel: [    0.467169] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep  3 15:48:01 node-1 kernel: [    0.467209] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep  3 15:48:01 node-1 kernel: [    0.467228] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep  3 15:48:01 node-1 kernel: [    0.467258] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep  3 15:48:01 node-1 kernel: [    0.467301] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep  3 15:48:01 node-1 kernel: [    0.467318] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.467390] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.467468] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.467545] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep  3 15:48:01 node-1 kernel: [    0.467551] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep  3 15:48:01 node-1 kernel: [    0.467636] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep  3 15:48:01 node-1 kernel: [    0.467784] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep  3 15:48:01 node-1 kernel: [    0.467801] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep  3 15:48:01 node-1 kernel: [    0.467879] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep  3 15:48:01 node-1 kernel: [    0.467932] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep  3 15:48:01 node-1 kernel: [    0.467954] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep  3 15:48:01 node-1 kernel: [    0.468010] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep  3 15:48:01 node-1 kernel: [    0.468054] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep  3 15:48:01 node-1 kernel: [    0.468082] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep  3 15:48:01 node-1 kernel: [    0.468138] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep  3 15:48:01 node-1 kernel: [    0.468181] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep  3 15:48:01 node-1 kernel: [    0.468206] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep  3 15:48:01 node-1 kernel: [    0.468223] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep  3 15:48:01 node-1 kernel: [    0.468301] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep  3 15:48:01 node-1 kernel: [    0.468351] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep  3 15:48:01 node-1 kernel: [    0.468378] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep  3 15:48:01 node-1 kernel: [    0.468627] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep  3 15:48:01 node-1 kernel: [    0.468633] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep  3 15:48:01 node-1 kernel: [    0.468639] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep  3 15:48:01 node-1 kernel: [    0.468645] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep  3 15:48:01 node-1 kernel: [    0.468652] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep  3 15:48:01 node-1 kernel: [    0.468683] pci 0000:01:00.0: supports D1 D2
Sep  3 15:48:01 node-1 kernel: [    0.474753] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep  3 15:48:01 node-1 kernel: [    0.474759] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep  3 15:48:01 node-1 kernel: [    0.474763] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep  3 15:48:01 node-1 kernel: [    0.474992] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep  3 15:48:01 node-1 kernel: [    0.475025] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep  3 15:48:01 node-1 kernel: [    0.482750] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep  3 15:48:01 node-1 kernel: [    0.482756] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep  3 15:48:01 node-1 kernel: [    0.482760] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep  3 15:48:01 node-1 kernel: [    0.482845] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep  3 15:48:01 node-1 kernel: [    0.482918] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep  3 15:48:01 node-1 kernel: [    0.483013] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep  3 15:48:01 node-1 kernel: [    0.483071] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep  3 15:48:01 node-1 kernel: [    0.483075] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep  3 15:48:01 node-1 kernel: [    0.483076] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep  3 15:48:01 node-1 kernel: [    0.483129] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep  3 15:48:01 node-1 kernel: [    0.483252] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep  3 15:48:01 node-1 kernel: [    0.483306] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep  3 15:48:01 node-1 kernel: [    0.483308] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep  3 15:48:01 node-1 kernel: [    0.483310] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep  3 15:48:01 node-1 kernel: [    0.483360] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep  3 15:48:01 node-1 kernel: [    0.483483] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep  3 15:48:01 node-1 kernel: [    0.483521] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep  3 15:48:01 node-1 kernel: [    0.483640] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep  3 15:48:01 node-1 kernel: [    0.483676] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep  3 15:48:01 node-1 kernel: [    0.483816] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep  3 15:48:01 node-1 kernel: [    0.483854] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep  3 15:48:01 node-1 kernel: [    0.483972] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep  3 15:48:01 node-1 kernel: [    0.484016] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep  3 15:48:01 node-1 kernel: [    0.484019] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep  3 15:48:01 node-1 kernel: [    0.484021] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep  3 15:48:01 node-1 kernel: [    0.484081] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep  3 15:48:01 node-1 kernel: [    0.484144] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep  3 15:48:01 node-1 kernel: [    0.484196] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep  3 15:48:01 node-1 kernel: [    0.484237] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep  3 15:48:01 node-1 kernel: [    0.484319] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep  3 15:48:01 node-1 kernel: [    0.484428] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep  3 15:48:01 node-1 kernel: [    0.484430] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep  3 15:48:01 node-1 kernel: [    0.484432] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep  3 15:48:01 node-1 kernel: [    0.484488] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep  3 15:48:01 node-1 kernel: [    0.484542] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep  3 15:48:01 node-1 kernel: [    0.484590] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep  3 15:48:01 node-1 kernel: [    0.484829] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep  3 15:48:01 node-1 kernel: [    0.484833] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep  3 15:48:01 node-1 kernel: [    0.484896] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep  3 15:48:01 node-1 kernel: [    0.484950] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep  3 15:48:01 node-1 kernel: [    0.484998] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep  3 15:48:01 node-1 kernel: [    0.485206] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep  3 15:48:01 node-1 kernel: [    0.485210] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep  3 15:48:01 node-1 kernel: [    0.485269] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep  3 15:48:01 node-1 kernel: [    0.485329] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep  3 15:48:01 node-1 kernel: [    0.485381] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep  3 15:48:01 node-1 kernel: [    0.485606] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep  3 15:48:01 node-1 kernel: [    0.485610] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep  3 15:48:01 node-1 kernel: [    0.485785] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep  3 15:48:01 node-1 kernel: [    0.485824] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep  3 15:48:01 node-1 kernel: [    0.485899] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep  3 15:48:01 node-1 kernel: [    0.485918] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep  3 15:48:01 node-1 kernel: [    0.485931] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep  3 15:48:01 node-1 kernel: [    0.485944] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep  3 15:48:01 node-1 kernel: [    0.485995] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep  3 15:48:01 node-1 kernel: [    0.490756] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep  3 15:48:01 node-1 kernel: [    0.490765] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep  3 15:48:01 node-1 kernel: [    0.490817] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep  3 15:48:01 node-1 kernel: [    0.491544] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep  3 15:48:01 node-1 kernel: [    0.491547] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep  3 15:48:01 node-1 kernel: [    0.491672] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep  3 15:48:01 node-1 kernel: [    0.491781] PCI host bridge to bus 0000:80
Sep  3 15:48:01 node-1 kernel: [    0.491783] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep  3 15:48:01 node-1 kernel: [    0.491784] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep  3 15:48:01 node-1 kernel: [    0.491785] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep  3 15:48:01 node-1 kernel: [    0.491793] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.491857] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.491925] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep  3 15:48:01 node-1 kernel: [    0.491987] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep  3 15:48:01 node-1 kernel: [    0.491993] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep  3 15:48:01 node-1 kernel: [    0.492066] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep  3 15:48:01 node-1 kernel: [    0.492367] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep  3 15:48:01 node-1 kernel: [    0.492399] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep  3 15:48:01 node-1 kernel: [    0.492429] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep  3 15:48:01 node-1 kernel: [    0.492458] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep  3 15:48:01 node-1 kernel: [    0.492488] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep  3 15:48:01 node-1 kernel: [    0.492518] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep  3 15:48:01 node-1 kernel: [    0.492548] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep  3 15:48:01 node-1 kernel: [    0.492578] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep  3 15:48:01 node-1 kernel: [    0.492664] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep  3 15:48:01 node-1 kernel: [    0.492668] ACPI: \_SB_.UNC1: notify handler is installed
Sep  3 15:48:01 node-1 kernel: [    0.492669] ACPI: \_SB_.UNC0: notify handler is installed
Sep  3 15:48:01 node-1 kernel: [    0.492685] ACPI: \_SB_.PCI0: notify handler is installed
Sep  3 15:48:01 node-1 kernel: [    0.492738] ACPI: \_SB_.PCI1: notify handler is installed
Sep  3 15:48:01 node-1 kernel: [    0.492817] Found 4 acpi root devices
Sep  3 15:48:01 node-1 kernel: [    0.492938] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep  3 15:48:01 node-1 kernel: [    0.492940] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep  3 15:48:01 node-1 kernel: [    0.492942] vgaarb: loaded
Sep  3 15:48:01 node-1 kernel: [    0.492943] vgaarb: bridge control possible 0000:0c:00.0
Sep  3 15:48:01 node-1 kernel: [    0.493067] SCSI subsystem initialized
Sep  3 15:48:01 node-1 kernel: [    0.493132] libata version 3.00 loaded.
Sep  3 15:48:01 node-1 kernel: [    0.493148] ACPI: bus type USB registered
Sep  3 15:48:01 node-1 kernel: [    0.493158] usbcore: registered new interface driver usbfs
Sep  3 15:48:01 node-1 kernel: [    0.493163] usbcore: registered new interface driver hub
Sep  3 15:48:01 node-1 kernel: [    0.493184] usbcore: registered new device driver usb
Sep  3 15:48:01 node-1 kernel: [    0.493365] PCI: Using ACPI for IRQ routing
Sep  3 15:48:01 node-1 kernel: [    0.496981] PCI: pci_cache_line_size set to 64 bytes
Sep  3 15:48:01 node-1 kernel: [    0.497190] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep  3 15:48:01 node-1 kernel: [    0.497192] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep  3 15:48:01 node-1 kernel: [    0.497192] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep  3 15:48:01 node-1 kernel: [    0.497257] NetLabel: Initializing
Sep  3 15:48:01 node-1 kernel: [    0.497258] NetLabel:  domain hash size = 128
Sep  3 15:48:01 node-1 kernel: [    0.497259] NetLabel:  protocols = UNLABELED CIPSOv4
Sep  3 15:48:01 node-1 kernel: [    0.497269] NetLabel:  unlabeled traffic allowed by default
Sep  3 15:48:01 node-1 kernel: [    0.497325] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep  3 15:48:01 node-1 kernel: [    0.497329] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep  3 15:48:01 node-1 kernel: [    0.499395] Switched to clocksource hpet
Sep  3 15:48:01 node-1 kernel: [    0.503354] AppArmor: AppArmor Filesystem Enabled
Sep  3 15:48:01 node-1 kernel: [    0.503367] pnp: PnP ACPI init
Sep  3 15:48:01 node-1 kernel: [    0.503373] ACPI: bus type PNP registered
Sep  3 15:48:01 node-1 kernel: [    0.503490] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep  3 15:48:01 node-1 kernel: [    0.503498] pnp 00:01: [dma 4]
Sep  3 15:48:01 node-1 kernel: [    0.503510] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep  3 15:48:01 node-1 kernel: [    0.503537] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep  3 15:48:01 node-1 kernel: [    0.503556] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep  3 15:48:01 node-1 kernel: [    0.503575] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep  3 15:48:01 node-1 kernel: [    0.503608] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep  3 15:48:01 node-1 kernel: [    0.503661] system 00:06: [io  0x0500-0x057f] has been reserved
Sep  3 15:48:01 node-1 kernel: [    0.503663] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep  3 15:48:01 node-1 kernel: [    0.503664] system 00:06: [io  0x0580-0x059f] has been reserved
Sep  3 15:48:01 node-1 kernel: [    0.503666] system 00:06: [io  0x0600-0x061f] has been reserved
Sep  3 15:48:01 node-1 kernel: [    0.503667] system 00:06: [io  0x0880-0x0883] has been reserved
Sep  3 15:48:01 node-1 kernel: [    0.503672] system 00:06: [io  0x0800-0x081f] has been reserved
Sep  3 15:48:01 node-1 kernel: [    0.503674] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep  3 15:48:01 node-1 kernel: [    0.503676] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep  3 15:48:01 node-1 kernel: [    0.503677] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep  3 15:48:01 node-1 kernel: [    0.503679] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep  3 15:48:01 node-1 kernel: [    0.503680] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep  3 15:48:01 node-1 kernel: [    0.503682] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep  3 15:48:01 node-1 kernel: [    0.503683] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep  3 15:48:01 node-1 kernel: [    0.503686] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep  3 15:48:01 node-1 kernel: [    0.503769] pnp 00:07: [dma 0 disabled]
Sep  3 15:48:01 node-1 kernel: [    0.503797] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep  3 15:48:01 node-1 kernel: [    0.503871] pnp 00:08: [dma 0 disabled]
Sep  3 15:48:01 node-1 kernel: [    0.503904] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep  3 15:48:01 node-1 kernel: [    0.503955] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep  3 15:48:01 node-1 kernel: [    0.504306] pnp: PnP ACPI: found 10 devices
Sep  3 15:48:01 node-1 kernel: [    0.504308] ACPI: bus type PNP unregistered
Sep  3 15:48:01 node-1 kernel: [    0.510621] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep  3 15:48:01 node-1 kernel: [    0.510624] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep  3 15:48:01 node-1 kernel: [    0.510627] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep  3 15:48:01 node-1 kernel: [    0.510631] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep  3 15:48:01 node-1 kernel: [    0.510633] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep  3 15:48:01 node-1 kernel: [    0.510648] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep  3 15:48:01 node-1 kernel: [    0.510677] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep  3 15:48:01 node-1 kernel: [    0.510713] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep  3 15:48:01 node-1 kernel: [    0.510742] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep  3 15:48:01 node-1 kernel: [    0.510757] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep  3 15:48:01 node-1 kernel: [    0.510786] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep  3 15:48:01 node-1 kernel: [    0.510800] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep  3 15:48:01 node-1 kernel: [    0.510833] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep  3 15:48:01 node-1 kernel: [    0.510834] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep  3 15:48:01 node-1 kernel: [    0.510849] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep  3 15:48:01 node-1 kernel: [    0.510878] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep  3 15:48:01 node-1 kernel: [    0.510880] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep  3 15:48:01 node-1 kernel: [    0.510894] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep  3 15:48:01 node-1 kernel: [    0.510923] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep  3 15:48:01 node-1 kernel: [    0.510925] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep  3 15:48:01 node-1 kernel: [    0.510928] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep  3 15:48:01 node-1 kernel: [    0.510932] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep  3 15:48:01 node-1 kernel: [    0.510933] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep  3 15:48:01 node-1 kernel: [    0.510936] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep  3 15:48:01 node-1 kernel: [    0.510939] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep  3 15:48:01 node-1 kernel: [    0.510944] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep  3 15:48:01 node-1 kernel: [    0.510952] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep  3 15:48:01 node-1 kernel: [    0.510956] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep  3 15:48:01 node-1 kernel: [    0.510962] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep  3 15:48:01 node-1 kernel: [    0.510963] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep  3 15:48:01 node-1 kernel: [    0.510964] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep  3 15:48:01 node-1 kernel: [    0.510965] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep  3 15:48:01 node-1 kernel: [    0.510965] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep  3 15:48:01 node-1 kernel: [    0.510966] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep  3 15:48:01 node-1 kernel: [    0.510967] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep  3 15:48:01 node-1 kernel: [    0.510968] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep  3 15:48:01 node-1 kernel: [    0.510969] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep  3 15:48:01 node-1 kernel: [    0.510970] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep  3 15:48:01 node-1 kernel: [    0.510971] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep  3 15:48:01 node-1 kernel: [    0.510972] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep  3 15:48:01 node-1 kernel: [    0.510973] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep  3 15:48:01 node-1 kernel: [    0.510974] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep  3 15:48:01 node-1 kernel: [    0.510974] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep  3 15:48:01 node-1 kernel: [    0.510975] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep  3 15:48:01 node-1 kernel: [    0.510976] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep  3 15:48:01 node-1 kernel: [    0.510977] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep  3 15:48:01 node-1 kernel: [    0.510978] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep  3 15:48:01 node-1 kernel: [    0.510979] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep  3 15:48:01 node-1 kernel: [    0.510980] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep  3 15:48:01 node-1 kernel: [    0.510981] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep  3 15:48:01 node-1 kernel: [    0.510983] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep  3 15:48:01 node-1 kernel: [    0.510984] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep  3 15:48:01 node-1 kernel: [    0.511022] NET: Registered protocol family 2
Sep  3 15:48:01 node-1 kernel: [    0.511281] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep  3 15:48:01 node-1 kernel: [    0.511617] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep  3 15:48:01 node-1 kernel: [    0.511763] TCP: Hash tables configured (established 262144 bind 65536)
Sep  3 15:48:01 node-1 kernel: [    0.511799] TCP: reno registered
Sep  3 15:48:01 node-1 kernel: [    0.511829] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep  3 15:48:01 node-1 kernel: [    0.511921] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep  3 15:48:01 node-1 kernel: [    0.512067] NET: Registered protocol family 1
Sep  3 15:48:01 node-1 kernel: [    0.551427] pci 0000:0c:00.0: Video device with shadowed ROM
Sep  3 15:48:01 node-1 kernel: [    0.551434] PCI: CLS 64 bytes, default 64
Sep  3 15:48:01 node-1 kernel: [    0.551476] Trying to unpack rootfs image as initramfs...
Sep  3 15:48:01 node-1 kernel: [    0.771402] Freeing initrd memory: 20372K (ffff880035826000 - ffff880036c0b000)
Sep  3 15:48:01 node-1 kernel: [    0.771437] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep  3 15:48:01 node-1 kernel: [    0.771439] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep  3 15:48:01 node-1 kernel: [    0.771858] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep  3 15:48:01 node-1 kernel: [    0.771865] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep  3 15:48:01 node-1 kernel: [    0.771869] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep  3 15:48:01 node-1 kernel: [    0.771875] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep  3 15:48:01 node-1 kernel: [    0.771887] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep  3 15:48:01 node-1 kernel: [    0.771903] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep  3 15:48:01 node-1 kernel: [    0.771919] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep  3 15:48:01 node-1 kernel: [    0.771933] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep  3 15:48:01 node-1 kernel: [    0.771945] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep  3 15:48:01 node-1 kernel: [    0.771955] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep  3 15:48:01 node-1 kernel: [    0.771961] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep  3 15:48:01 node-1 kernel: [    0.771968] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep  3 15:48:01 node-1 kernel: [    0.771976] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep  3 15:48:01 node-1 kernel: [    0.771989] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep  3 15:48:01 node-1 kernel: [    0.772002] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep  3 15:48:01 node-1 kernel: [    0.772015] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep  3 15:48:01 node-1 kernel: [    0.772068] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep  3 15:48:01 node-1 kernel: [    0.772072] Scanning for low memory corruption every 60 seconds
Sep  3 15:48:01 node-1 kernel: [    0.772394] Initialise system trusted keyring
Sep  3 15:48:01 node-1 kernel: [    0.772441] audit: initializing netlink socket (disabled)
Sep  3 15:48:01 node-1 kernel: [    0.772454] type=2000 audit(1472917643.728:1): initialized
Sep  3 15:48:01 node-1 kernel: [    0.790264] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep  3 15:48:01 node-1 kernel: [    0.791723] zbud: loaded
Sep  3 15:48:01 node-1 kernel: [    0.791836] VFS: Disk quotas dquot_6.5.2
Sep  3 15:48:01 node-1 kernel: [    0.791877] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep  3 15:48:01 node-1 kernel: [    0.792244] fuse init (API version 7.22)
Sep  3 15:48:01 node-1 kernel: [    0.792304] msgmni has been set to 32768
Sep  3 15:48:01 node-1 kernel: [    0.792347] Key type big_key registered
Sep  3 15:48:01 node-1 kernel: [    0.792851] Key type asymmetric registered
Sep  3 15:48:01 node-1 kernel: [    0.792853] Asymmetric key parser 'x509' registered
Sep  3 15:48:01 node-1 kernel: [    0.792874] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep  3 15:48:01 node-1 kernel: [    0.792927] io scheduler noop registered
Sep  3 15:48:01 node-1 kernel: [    0.792928] io scheduler deadline registered (default)
Sep  3 15:48:01 node-1 kernel: [    0.792944] io scheduler cfq registered
Sep  3 15:48:01 node-1 kernel: [    0.793262] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    0.793353] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    0.793440] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    0.793527] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    0.793622] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    0.793689] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    0.793953] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep  3 15:48:01 node-1 kernel: [    0.793971] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep  3 15:48:01 node-1 kernel: [    0.793984] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep  3 15:48:01 node-1 kernel: [    0.793993] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.793995] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.793998] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep  3 15:48:01 node-1 kernel: [    0.794001] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.794003] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.794004] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.794005] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.794007] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.794008] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.794010] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.794011] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.794013] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.794014] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.794015] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.794017] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.794019] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep  3 15:48:01 node-1 kernel: [    0.794023] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.794025] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep  3 15:48:01 node-1 kernel: [    0.794033] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.794036] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep  3 15:48:01 node-1 kernel: [    0.794046] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.794047] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep  3 15:48:01 node-1 kernel: [    0.794050] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep  3 15:48:01 node-1 kernel: [    0.794063] ioapic: probe of 0000:00:05.4 failed with error -22
Sep  3 15:48:01 node-1 kernel: [    0.794148] ioapic: probe of 0000:80:05.4 failed with error -22
Sep  3 15:48:01 node-1 kernel: [    0.794152] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  3 15:48:01 node-1 kernel: [    0.794161] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep  3 15:48:01 node-1 kernel: [    0.794196] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep  3 15:48:01 node-1 kernel: [    0.794197] vesafb: scrolling: redraw
Sep  3 15:48:01 node-1 kernel: [    0.794199] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep  3 15:48:01 node-1 kernel: [    0.815198] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep  3 15:48:01 node-1 kernel: [    0.823705] Console: switching to colour frame buffer device 80x30
Sep  3 15:48:01 node-1 kernel: [    0.832391] fb0: VESA VGA frame buffer device
Sep  3 15:48:01 node-1 kernel: [    0.832592] intel_idle: MWAIT substates: 0x2120
Sep  3 15:48:01 node-1 kernel: [    0.832593] intel_idle: v0.4 model 0x3F
Sep  3 15:48:01 node-1 kernel: [    0.832593] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep  3 15:48:01 node-1 kernel: [    0.832828] ipmi message handler version 39.2
Sep  3 15:48:01 node-1 kernel: [    0.833094] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep  3 15:48:01 node-1 kernel: [    0.833526] ACPI: AC Adapter [P111] (on-line)
Sep  3 15:48:01 node-1 kernel: [    0.838749] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep  3 15:48:01 node-1 kernel: [    0.849761] ACPI: Power Button [PWRB]
Sep  3 15:48:01 node-1 kernel: [    0.855568] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep  3 15:48:01 node-1 kernel: [    0.867295] ACPI: Power Button [PWRF]
Sep  3 15:48:01 node-1 kernel: [    0.893068] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep  3 15:48:01 node-1 kernel: [    0.904714] pstore: Registered erst as persistent store backend
Sep  3 15:48:01 node-1 kernel: [    0.910915] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep  3 15:48:01 node-1 kernel: [    0.922877] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep  3 15:48:01 node-1 kernel: [    0.949612] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep  3 15:48:01 node-1 kernel: [    0.982914] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep  3 15:48:01 node-1 kernel: [    0.996972] Linux agpgart interface v0.103
Sep  3 15:48:01 node-1 kernel: [    1.004599] brd: module loaded
Sep  3 15:48:01 node-1 kernel: [    1.011631] loop: module loaded
Sep  3 15:48:01 node-1 kernel: [    1.018352] libphy: Fixed MDIO Bus: probed
Sep  3 15:48:01 node-1 kernel: [    1.024815] tun: Universal TUN/TAP device driver, 1.6
Sep  3 15:48:01 node-1 kernel: [    1.031291] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep  3 15:48:01 node-1 kernel: [    1.037809] PPP generic driver version 2.4.2
Sep  3 15:48:01 node-1 kernel: [    1.044191] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep  3 15:48:01 node-1 kernel: [    1.050647] ehci-pci: EHCI PCI platform driver
Sep  3 15:48:01 node-1 kernel: [    1.057252] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep  3 15:48:01 node-1 kernel: [    1.063676] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep  3 15:48:01 node-1 kernel: [    1.076231] ehci-pci 0000:00:1a.0: debug port 2
Sep  3 15:48:01 node-1 kernel: [    1.086422] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep  3 15:48:01 node-1 kernel: [    1.086440] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep  3 15:48:01 node-1 kernel: [    1.102888] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep  3 15:48:01 node-1 kernel: [    1.108972] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep  3 15:48:01 node-1 kernel: [    1.115148] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep  3 15:48:01 node-1 kernel: [    1.127074] usb usb1: Product: EHCI Host Controller
Sep  3 15:48:01 node-1 kernel: [    1.133113] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep  3 15:48:01 node-1 kernel: [    1.139173] usb usb1: SerialNumber: 0000:00:1a.0
Sep  3 15:48:01 node-1 kernel: [    1.145119] hub 1-0:1.0: USB hub found
Sep  3 15:48:01 node-1 kernel: [    1.150956] hub 1-0:1.0: 2 ports detected
Sep  3 15:48:01 node-1 kernel: [    1.156773] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep  3 15:48:01 node-1 kernel: [    1.162363] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep  3 15:48:01 node-1 kernel: [    1.173262] ehci-pci 0000:00:1d.0: debug port 2
Sep  3 15:48:01 node-1 kernel: [    1.182559] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep  3 15:48:01 node-1 kernel: [    1.182562] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep  3 15:48:01 node-1 kernel: [    1.198806] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep  3 15:48:01 node-1 kernel: [    1.204032] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep  3 15:48:01 node-1 kernel: [    1.209332] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep  3 15:48:01 node-1 kernel: [    1.219886] usb usb2: Product: EHCI Host Controller
Sep  3 15:48:01 node-1 kernel: [    1.225353] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep  3 15:48:01 node-1 kernel: [    1.230885] usb usb2: SerialNumber: 0000:00:1d.0
Sep  3 15:48:01 node-1 kernel: [    1.236399] hub 2-0:1.0: USB hub found
Sep  3 15:48:01 node-1 kernel: [    1.241745] hub 2-0:1.0: 2 ports detected
Sep  3 15:48:01 node-1 kernel: [    1.247044] ehci-platform: EHCI generic platform driver
Sep  3 15:48:01 node-1 kernel: [    1.252348] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep  3 15:48:01 node-1 kernel: [    1.257727] ohci-pci: OHCI PCI platform driver
Sep  3 15:48:01 node-1 kernel: [    1.263137] ohci-platform: OHCI generic platform driver
Sep  3 15:48:01 node-1 kernel: [    1.268321] uhci_hcd: USB Universal Host Controller Interface driver
Sep  3 15:48:01 node-1 kernel: [    1.273639] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep  3 15:48:01 node-1 kernel: [    1.466586] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep  3 15:48:01 node-1 kernel: [    1.630730] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep  3 15:48:01 node-1 kernel: [    1.636256] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep  3 15:48:01 node-1 kernel: [    1.641993] hub 1-1:1.0: USB hub found
Sep  3 15:48:01 node-1 kernel: [    1.647466] hub 1-1:1.0: 6 ports detected
Sep  3 15:48:01 node-1 kernel: [    1.762327] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep  3 15:48:01 node-1 kernel: [    1.770375] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep  3 15:48:01 node-1 kernel: [    2.030390] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep  3 15:48:01 node-1 kernel: [    2.035950] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep  3 15:48:01 node-1 kernel: [    2.041784] hub 2-1:1.0: USB hub found
Sep  3 15:48:01 node-1 kernel: [    2.047378] hub 2-1:1.0: 8 ports detected
Sep  3 15:48:01 node-1 kernel: [    2.314993] i8042: No controller found
Sep  3 15:48:01 node-1 kernel: [    2.320375] mousedev: PS/2 mouse device common for all mice
Sep  3 15:48:01 node-1 kernel: [    2.325852] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep  3 15:48:01 node-1 kernel: [    2.326064] rtc_cmos 00:02: RTC can wake from S4
Sep  3 15:48:01 node-1 kernel: [    2.326763] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep  3 15:48:01 node-1 kernel: [    2.326963] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep  3 15:48:01 node-1 kernel: [    2.327019] device-mapper: uevent: version 1.0.3
Sep  3 15:48:01 node-1 kernel: [    2.327288] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep  3 15:48:01 node-1 kernel: [    2.327299] ledtrig-cpu: registered to indicate activity on CPUs
Sep  3 15:48:01 node-1 kernel: [    2.327404] TCP: cubic registered
Sep  3 15:48:01 node-1 kernel: [    2.327463] NET: Registered protocol family 10
Sep  3 15:48:01 node-1 kernel: [    2.327607] NET: Registered protocol family 17
Sep  3 15:48:01 node-1 kernel: [    2.327616] Key type dns_resolver registered
Sep  3 15:48:01 node-1 kernel: [    2.328301] Loading compiled-in X.509 certificates
Sep  3 15:48:01 node-1 kernel: [    2.328818] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep  3 15:48:01 node-1 kernel: [    2.328833] registered taskstats version 1
Sep  3 15:48:01 node-1 kernel: [    2.335204] Key type trusted registered
Sep  3 15:48:01 node-1 kernel: [    2.341403] Key type encrypted registered
Sep  3 15:48:01 node-1 kernel: [    2.341405] AppArmor: AppArmor sha1 policy hashing enabled
Sep  3 15:48:01 node-1 kernel: [    2.341407] IMA: No TPM chip found, activating TPM-bypass!
Sep  3 15:48:01 node-1 kernel: [    2.342543] regulator-dummy: disabling
Sep  3 15:48:01 node-1 kernel: [    2.343398]   Magic number: 0:71:790
Sep  3 15:48:01 node-1 kernel: [    2.454110] rtc_cmos 00:02: setting system clock to 2016-09-03 15:47:26 UTC (1472917646)
Sep  3 15:48:01 node-1 kernel: [    2.454204] hpet1: lost 7 rtc interrupts
Sep  3 15:48:01 node-1 kernel: [    2.471532] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep  3 15:48:01 node-1 kernel: [    2.477099] EDD information not available.
Sep  3 15:48:01 node-1 kernel: [    2.482692] PM: Hibernation image not present or could not be loaded.
Sep  3 15:48:01 node-1 kernel: [    2.483470] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep  3 15:48:01 node-1 kernel: [    2.494719] Write protecting the kernel read-only data: 12288k
Sep  3 15:48:01 node-1 kernel: [    2.500875] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep  3 15:48:01 node-1 kernel: [    2.513521] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep  3 15:48:01 node-1 kernel: [    2.545591] device-mapper: multipath: version 1.6.0 loaded
Sep  3 15:48:01 node-1 kernel: [    2.553363] systemd-udevd[217]: starting version 204
Sep  3 15:48:01 node-1 kernel: [    2.572788] md: linear personality registered for level -1
Sep  3 15:48:01 node-1 kernel: [    2.585796] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep  3 15:48:01 node-1 kernel: [    2.592143] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep  3 15:48:01 node-1 kernel: [    2.604729] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep  3 15:48:01 node-1 kernel: [    2.611132] usb 2-1.4: Manufacturer: Avocent
Sep  3 15:48:01 node-1 kernel: [    2.611293] md: multipath personality registered for level -4
Sep  3 15:48:01 node-1 kernel: [    2.623638] usb 2-1.4: SerialNumber: 20111102-00000001
Sep  3 15:48:01 node-1 kernel: [    2.630061] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep  3 15:48:01 node-1 kernel: [    2.636607] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep  3 15:48:01 node-1 kernel: [    2.637394] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep  3 15:48:01 node-1 kernel: [    2.637913] megasas: FW now in Ready state
Sep  3 15:48:01 node-1 kernel: [    2.637975] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.638012] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.638050] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.638085] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.638122] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.638154] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.638187] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.638224] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.638265] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.638298] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.638334] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.638366] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.638404] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.638442] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.638481] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.638518] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.638680] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep  3 15:48:01 node-1 kernel: [    2.669720] md: raid0 personality registered for level 0
Sep  3 15:48:01 node-1 kernel: [    2.678550] md: raid1 personality registered for level 1
Sep  3 15:48:01 node-1 kernel: [    2.679151] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Sep  3 15:48:01 node-1 kernel: [    2.679153] 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  3 15:48:01 node-1 kernel: [    2.679154] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep  3 15:48:01 node-1 kernel: [    2.679217] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.679247] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.679284] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.679323] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.679407] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.689486] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Sep  3 15:48:01 node-1 kernel: [    2.689488] 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  3 15:48:01 node-1 kernel: [    2.689489] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep  3 15:48:01 node-1 kernel: [    2.689585] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.689623] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.689663] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.689697] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.689802] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.700383] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Sep  3 15:48:01 node-1 kernel: [    2.700385] 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  3 15:48:01 node-1 kernel: [    2.700386] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep  3 15:48:01 node-1 kernel: [    2.700448] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.700486] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.700521] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.700558] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.700646] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.712245] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Sep  3 15:48:01 node-1 kernel: [    2.712246] 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  3 15:48:01 node-1 kernel: [    2.712247] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep  3 15:48:01 node-1 kernel: [    2.712308] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.712349] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.712388] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.712423] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.712512] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep  3 15:48:01 node-1 kernel: [    2.872183] Switched to clocksource tsc
Sep  3 15:48:01 node-1 kernel: [    2.881641] hidraw: raw HID events driver (C) Jiri Kosina
Sep  3 15:48:01 node-1 kernel: [    2.892832] usbcore: registered new interface driver usbhid
Sep  3 15:48:01 node-1 kernel: [    2.899595] usbhid: USB HID core driver
Sep  3 15:48:01 node-1 kernel: [    2.907158] 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  3 15:48:01 node-1 kernel: [    2.920692] 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  3 15:48:01 node-1 kernel: [    2.934687] 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  3 15:48:01 node-1 kernel: [    2.948659] 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  3 15:48:01 node-1 kernel: [    2.953326] raid6: sse2x1    6937 MB/s
Sep  3 15:48:01 node-1 kernel: [    2.969657] 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  3 15:48:01 node-1 kernel: [    2.984110] 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  3 15:48:01 node-1 kernel: [    3.021253] raid6: sse2x2   14623 MB/s
Sep  3 15:48:01 node-1 kernel: [    3.093190] raid6: sse2x4   17281 MB/s
Sep  3 15:48:01 node-1 kernel: [    3.165129] raid6: avx2x1   22972 MB/s
Sep  3 15:48:01 node-1 kernel: [    3.237067] raid6: avx2x2   26481 MB/s
Sep  3 15:48:01 node-1 kernel: [    3.309006] raid6: avx2x4   30997 MB/s
Sep  3 15:48:01 node-1 kernel: [    3.315619] raid6: using algorithm avx2x4 (30997 MB/s)
Sep  3 15:48:01 node-1 kernel: [    3.322206] raid6: using avx2x2 recovery algorithm
Sep  3 15:48:01 node-1 kernel: [    3.329308] xor: automatically using best checksumming function:
Sep  3 15:48:01 node-1 kernel: [    3.372950]    avx       : 35724.000 MB/sec
Sep  3 15:48:01 node-1 kernel: [    3.379734] async_tx: api initialized (async)
Sep  3 15:48:01 node-1 kernel: [    3.389536] md: raid6 personality registered for level 6
Sep  3 15:48:01 node-1 kernel: [    3.395817] md: raid5 personality registered for level 5
Sep  3 15:48:01 node-1 kernel: [    3.401912] md: raid4 personality registered for level 4
Sep  3 15:48:01 node-1 kernel: [    3.410778] md: raid10 personality registered for level 10
Sep  3 15:48:01 node-1 kernel: [    3.459931] multipathd (358): /proc/358/oom_adj is deprecated, please use /proc/358/oom_score_adj instead.
Sep  3 15:48:01 node-1 kernel: [    3.576831] megasas:IOC Init cmd success
Sep  3 15:48:01 node-1 kernel: [    3.628799] megasas: INIT adapter done
Sep  3 15:48:01 node-1 kernel: [    3.704727] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep  3 15:48:01 node-1 kernel: [    3.710228] scsi0 : LSI SAS based MegaRAID driver
Sep  3 15:48:01 node-1 kernel: [    3.717340] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep  3 15:48:01 node-1 kernel: [    3.737337] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep  3 15:48:01 node-1 kernel: [    3.750096] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep  3 15:48:01 node-1 kernel: [    3.755397] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep  3 15:48:01 node-1 kernel: [    3.766506] sd 0:2:0:0: [sda] Write Protect is off
Sep  3 15:48:01 node-1 kernel: [    3.772118] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep  3 15:48:01 node-1 kernel: [    3.772138] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep  3 15:48:01 node-1 kernel: [    3.812605]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Sep  3 15:48:01 node-1 kernel: [    3.817298] sd 0:2:0:0: [sda] Attached SCSI disk
Sep  3 15:48:01 node-1 kernel: [    3.946446] random: lvm urandom read with 27 bits of entropy available
Sep  3 15:48:01 node-1 kernel: [    4.086485] bio: create slab <bio-1> at 1
Sep  3 15:48:01 node-1 kernel: [    4.898436] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Sep  3 15:48:01 node-1 kernel: [    5.563907] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Sep  3 15:48:01 node-1 kernel: [    5.582605] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep  3 15:48:01 node-1 kernel: [    5.605460] random: nonblocking pool is initialized
Sep  3 15:48:01 node-1 kernel: [    5.717639] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep  3 15:48:01 node-1 kernel: [    5.753574] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep  3 15:48:01 node-1 kernel: [    5.841686] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep  3 15:48:01 node-1 kernel: [    6.050627] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep  3 15:48:01 node-1 kernel: [    6.077651] XFS (dm-1): Mounting Filesystem
Sep  3 15:48:01 node-1 kernel: [    6.352989] XFS (dm-1): Ending clean mount
Sep  3 15:48:01 node-1 kernel: [    6.408257] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep  3 15:48:01 node-1 kernel: [    6.433998] XFS (dm-2): Mounting Filesystem
Sep  3 15:48:01 node-1 kernel: [    6.579123] XFS (dm-2): Ending clean mount
Sep  3 15:48:01 node-1 kernel: [    6.672972] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Sep  3 15:48:01 node-1 kernel: [    8.461332] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep  3 15:48:01 node-1 kernel: [    8.487816] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep  3 15:48:01 node-1 kernel: [    8.608692] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep  3 15:48:01 node-1 kernel: [    8.608697] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep  3 15:48:01 node-1 kernel: [    8.608701] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep  3 15:48:01 node-1 kernel: [    8.608705] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep  3 15:48:01 node-1 kernel: [    8.648508] systemd-udevd[806]: starting version 204
Sep  3 15:48:01 node-1 kernel: [    8.805494] power_meter ACPI000D:00: Found ACPI power meter.
Sep  3 15:48:01 node-1 kernel: [    8.805519] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep  3 15:48:01 node-1 kernel: [    8.849720] wmi: Mapper loaded
Sep  3 15:48:01 node-1 kernel: [    8.861583] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep  3 15:48:01 node-1 kernel: [    8.861588] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep  3 15:48:01 node-1 kernel: [    8.861590] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep  3 15:48:01 node-1 kernel: [    8.861592] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep  3 15:48:01 node-1 kernel: [    8.861604] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep  3 15:48:01 node-1 kernel: [    8.864253] IPMI System Interface driver.
Sep  3 15:48:01 node-1 kernel: [    8.864303] ipmi_si: probing via ACPI
Sep  3 15:48:01 node-1 kernel: [    8.864326] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep  3 15:48:01 node-1 kernel: [    8.864328] ipmi_si: Adding ACPI-specified kcs state machine
Sep  3 15:48:01 node-1 kernel: [    8.864337] ipmi_si: probing via SMBIOS
Sep  3 15:48:01 node-1 kernel: [    8.864338] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep  3 15:48:01 node-1 kernel: [    8.864339] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep  3 15:48:01 node-1 kernel: [    8.864341] ipmi_si: probing via SPMI
Sep  3 15:48:01 node-1 kernel: [    8.864342] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep  3 15:48:01 node-1 kernel: [    8.864342] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep  3 15:48:01 node-1 kernel: [    8.864343] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep  3 15:48:01 node-1 kernel: [    8.872778] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep  3 15:48:01 node-1 kernel: [    8.948705] systemd-udevd[825]: renamed network interface eth0 to enp6s0
Sep  3 15:48:01 node-1 kernel: [    8.980582] systemd-udevd[842]: renamed network interface eth3 to enp9s0
Sep  3 15:48:01 node-1 kernel: [    9.005040] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep  3 15:48:01 node-1 kernel: [    9.005048] ipmi_si 00:09: IPMI kcs interface initialized
Sep  3 15:48:01 node-1 kernel: [    9.008555] systemd-udevd[827]: renamed network interface eth1 to enp7s0
Sep  3 15:48:01 node-1 kernel: [    9.056669] systemd-udevd[835]: renamed network interface eth2 to enp8s0
Sep  3 15:48:01 node-1 kernel: [    9.316863] type=1400 audit(1472917653.477:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1099 comm="apparmor_parser"
Sep  3 15:48:01 node-1 kernel: [    9.317023] type=1400 audit(1472917653.477:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1099 comm="apparmor_parser"
Sep  3 15:48:01 node-1 kernel: [    9.317154] type=1400 audit(1472917653.477:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1099 comm="apparmor_parser"
Sep  3 15:48:01 node-1 kernel: [    9.338094] type=1400 audit(1472917653.497:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1101 comm="apparmor_parser"
Sep  3 15:48:01 node-1 kernel: [    9.338241] type=1400 audit(1472917653.497:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1101 comm="apparmor_parser"
Sep  3 15:48:01 node-1 kernel: [    9.338365] type=1400 audit(1472917653.497:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1101 comm="apparmor_parser"
Sep  3 15:48:01 node-1 kernel: [    9.339221] type=1400 audit(1472917653.497:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1097 comm="apparmor_parser"
Sep  3 15:48:01 node-1 kernel: [    9.339458] type=1400 audit(1472917653.497:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1097 comm="apparmor_parser"
Sep  3 15:48:01 node-1 kernel: [    9.339661] type=1400 audit(1472917653.497:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1098 comm="apparmor_parser"
Sep  3 15:48:01 node-1 kernel: [    9.339693] type=1400 audit(1472917653.497:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1097 comm="apparmor_parser"
Sep  3 15:48:01 node-1 kernel: [    9.849483] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep  3 15:48:01 node-1 kernel: [    9.851329] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep  3 15:48:01 node-1 kernel: [   10.019348] enic 0000:06:00.0 enp6s0: Link UP
Sep  3 15:48:01 node-1 kernel: [   10.020473] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep  3 15:48:01 node-1 kernel: [   10.020481] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep  3 15:48:01 node-1 kernel: [   20.225754] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep  3 15:48:03 node-1 failsafe: Failsafe of 120 seconds reached.
Sep  3 15:48:03 node-1 kernel: [   39.347731] init: failsafe main process (8453) killed by TERM signal
Sep  3 15:48:03 node-1 dbus[8494]: [system] AppArmor D-Bus mediation is enabled
Sep  3 15:48:03 node-1 kernel: [   39.585490] audit_printk_skb: 30 callbacks suppressed
Sep  3 15:48:03 node-1 kernel: [   39.585492] type=1400 audit(1472917683.279:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8576 comm="apparmor_parser"
Sep  3 15:48:03 node-1 kernel: [   39.585496] type=1400 audit(1472917683.279:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8576 comm="apparmor_parser"
Sep  3 15:48:03 node-1 kernel: [   39.585499] type=1400 audit(1472917683.279:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8576 comm="apparmor_parser"
Sep  3 15:48:03 node-1 kernel: [   39.585732] type=1400 audit(1472917683.279:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8576 comm="apparmor_parser"
Sep  3 15:48:03 node-1 kernel: [   39.585734] type=1400 audit(1472917683.279:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8576 comm="apparmor_parser"
Sep  3 15:48:03 node-1 kernel: [   39.585846] type=1400 audit(1472917683.279:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8576 comm="apparmor_parser"
Sep  3 15:48:03 node-1 kernel: [   39.607533] type=1400 audit(1472917683.303:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8577 comm="apparmor_parser"
Sep  3 15:48:03 node-1 kernel: [   39.670649] type=1400 audit(1472917683.367:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8579 comm="apparmor_parser"
Sep  3 15:48:03 node-1 anacron[8645]: Anacron 2.3 started on 2016-09-03
Sep  3 15:48:03 node-1 cron[8610]: (CRON) INFO (pidfile fd = 3)
Sep  3 15:48:03 node-1 anacron[8645]: Will run job `cron.daily' in 5 min.
Sep  3 15:48:03 node-1 anacron[8645]: Will run job `cron.weekly' in 10 min.
Sep  3 15:48:03 node-1 anacron[8645]: Will run job `cron.monthly' in 15 min.
Sep  3 15:48:03 node-1 anacron[8645]: Jobs will be executed sequentially
Sep  3 15:48:03 node-1 cron[8664]: (CRON) STARTUP (fork ok)
Sep  3 15:48:03 node-1 multipathd: path checkers start up
Sep  3 15:48:03 node-1 cron[8664]: (CRON) INFO (Running @reboot jobs)
Sep  3 15:48:04 node-1 postfix/master[8790]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep  3 15:48:07 node-1 puppet-agent[8974]: Reopening log files
Sep  3 15:48:09 node-1 puppet-agent[8974]: Could not request certificate: Connection refused - connect(2)
Sep  3 15:48:21 node-1 puppet-user[9182]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep  3 15:48:21 node-1 puppet-user[9182]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Sep  3 15:48:21 node-1 puppet-user[9182]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep  3 15:48:21 node-1 puppet-user[9182]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep  3 15:48:21 node-1 puppet-user[9182]: Finished catalog run in 0.68 seconds
Sep  3 15:48:23 node-1 multipathd: uevent trigger error
Sep  3 15:48:23 node-1 puppet-user[9612]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep  3 15:48:23 node-1 puppet-user[9612]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Sep  3 15:48:23 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep  3 15:48:23 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep  3 15:48:23 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Sep  3 15:48:23 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep  3 15:48:23 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep  3 15:48:23 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep  3 15:48:23 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep  3 15:48:23 node-1 puppet-user[9612]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep  3 15:48:23 node-1 puppet-user[9612]: Finished catalog run in 0.06 seconds
Sep  3 15:48:25 node-1 puppet-user[10075]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep  3 15:48:25 node-1 puppet-user[10075]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Sep  3 15:48:25 node-1 puppet-user[10075]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep  3 15:48:25 node-1 puppet-user[10075]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep  3 15:48:25 node-1 puppet-user[10075]: Finished catalog run in 0.03 seconds
Sep  3 15:48:27 node-1 puppet-user[10540]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep  3 15:48:27 node-1 puppet-user[10540]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Sep  3 15:48:27 node-1 puppet-user[10540]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep  3 15:48:27 node-1 puppet-user[10540]: Finished catalog run in 0.03 seconds
Sep  3 15:48:28 node-1 puppet-user[11181]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep  3 15:48:28 node-1 puppet-user[11181]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Sep  3 15:48:28 node-1 puppet-user[11181]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep  3 15:48:29 node-1 puppet-user[11181]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-kvm-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-kvm-0.9/]/returns) executed successfully
Sep  3 15:48:29 node-1 puppet-user[11181]: Finished catalog run in 0.45 seconds
Sep  3 15:48:30 node-1 puppet-user[11657]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep  3 15:48:30 node-1 puppet-user[11657]: Compiled catalog for node-1.domain.tld in environment production in 0.23 seconds
Sep  3 15:48:30 node-1 puppet-user[11657]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep  3 15:48:30 node-1 puppet-user[11657]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep  3 15:48:30 node-1 puppet-user[11657]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-kvm-0.9.0]/Apt::Setting[list-fuel-plugin-kvm-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-kvm-0.9.0.list]/ensure) created
Sep  3 15:48:31 node-1 puppet-user[11657]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep  3 15:48:31 node-1 puppet-user[11657]: Finished catalog run in 0.26 seconds
Sep  3 15:48:32 node-1 puppet-user[12132]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep  3 15:48:32 node-1 puppet-user[12132]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Sep  3 15:48:32 node-1 puppet-user[12132]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep  3 15:48:32 node-1 kernel: [   68.730485] nr_pdflush_threads exported in /proc is scheduled for removal
Sep  3 15:48:32 node-1 kernel: [   68.730541] 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  3 15:48:32 node-1 puppet-user[12132]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Sep  3 15:48:32 node-1 puppet-user[12132]: Finished catalog run in 0.07 seconds
Sep  3 15:48:34 node-1 puppet-user[12586]: (Scope(Class[main])) MODULAR: sync_time
Sep  3 15:48:34 node-1 puppet-user[12586]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Sep  3 15:48:34 node-1 ntpdate[13004]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep  3 15:48:39 node-1 kernel: [   75.106947] init: plymouth-upstart-bridge main process ended, respawning
Sep  3 15:48:39 node-1 puppet-agent[8974]: Could not run: SIGTERM
Sep  3 15:48:39 node-1 kernel: [   75.409053] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep  3 15:48:39 node-1 ec2: 
Sep  3 15:48:39 node-1 ec2: #############################################################
Sep  3 15:48:39 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep  3 15:48:39 node-1 ec2: 1024 fa:67:40:74:8f:ea:57:a6:57:ef:6b:f2:53:f9:27:1e  root@node-1.domain.tld (DSA)
Sep  3 15:48:39 node-1 ec2: 256 91:96:0d:58:f2:de:e0:06:bb:78:75:20:81:6f:ab:77  root@node-1.domain.tld (ECDSA)
Sep  3 15:48:39 node-1 ec2: 256 bf:44:92:15:a1:d0:9d:e8:6d:d7:3b:f9:95:29:56:9b  root@node-1.domain.tld (ED25519)
Sep  3 15:48:39 node-1 ec2: 2048 a1:78:17:e4:8a:c2:db:95:ee:24:0a:8c:e4:85:bf:29  root@node-1.domain.tld (RSA)
Sep  3 15:48:39 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep  3 15:48:39 node-1 ec2: #############################################################
Sep  3 15:48:40 node-1 ntpdate[13004]: adjust time server 10.20.0.2 offset 0.000553 sec
Sep  3 15:48:40 node-1 puppet-user[12586]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep  3 15:48:40 node-1 puppet-user[12586]: Finished catalog run in 6.17 seconds
Sep  3 15:48:45 node-1 puppet-user[13367]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep  3 15:48:45 node-1 puppet-user[13367]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Sep  3 15:48:45 node-1 puppet-user[13367]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep  3 15:48:45 node-1 puppet-user[13367]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-kvm"]'
Sep  3 15:48:45 node-1 puppet-user[13367]: Finished catalog run in 0.07 seconds
Sep  3 15:48:46 node-1 puppet-user[13827]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep  3 15:48:48 node-1 puppet-user[13827]: Compiled catalog for node-1.domain.tld in environment production in 1.58 seconds
Sep  3 15:48:48 node-1 puppet-user[13827]: (/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  3 15:48:48 node-1 puppet-user[13827]: (/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  3 15:48:48 node-1 puppet-user[13827]: (/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  3 15:48:48 node-1 puppet-user[13827]: (/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  3 15:48:48 node-1 puppet-user[13827]: (/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  3 15:48:48 node-1 puppet-user[13827]: (/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  3 15:48:48 node-1 puppet-user[13827]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep  3 15:48:48 node-1 puppet-user[13827]: (/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  3 15:48:48 node-1 puppet-user[13827]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep  3 15:48:48 node-1 puppet-user[13827]: (/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  3 15:48:48 node-1 puppet-user[13827]: (/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  3 15:48:48 node-1 puppet-user[13827]: (/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  3 15:48:48 node-1 puppet-user[13827]: (/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  3 15:48:48 node-1 puppet-user[13827]: (/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  3 15:48:48 node-1 puppet-user[13827]: (/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  3 15:48:48 node-1 puppet-user[13827]: (/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  3 15:49:01 node-1 CRON[14767]: (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  3 15:49:07 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  3 15:49:07 node-1 nailgun-agent: I, [2016-09-03T15:49:07.077011 #14770]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep  3 15:49:20 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  3 15:49:20 node-1 nailgun-agent: I, [2016-09-03T15:49:20.209499 #14770]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep  3 15:50:01 node-1 CRON[16179]: (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  3 15:50:22 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  3 15:50:22 node-1 nailgun-agent: I, [2016-09-03T15:50:22.382629 #16182]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep  3 15:50:27 node-1 puppet-user[13827]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Sep  3 15:50:27 node-1 puppet-user[13827]: Finished catalog run in 99.21 seconds
Sep  3 15:50:29 node-1 puppet-user[16811]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep  3 15:50:29 node-1 puppet-user[16811]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Sep  3 15:50:35 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  3 15:50:35 node-1 nailgun-agent: I, [2016-09-03T15:50:35.447312 #16182]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep  3 15:50:36 node-1 puppet-user[16811]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep  3 15:51:01 node-1 CRON[17971]: (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  3 15:51:08 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  3 15:51:08 node-1 nailgun-agent: I, [2016-09-03T15:51:08.631730 #17974]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep  3 15:51:21 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  3 15:51:21 node-1 nailgun-agent: I, [2016-09-03T15:51:21.744357 #17974]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep  3 15:51:38 node-1 puppet-user[16811]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep  3 15:51:38 node-1 puppet-user[16811]: Finished catalog run in 68.62 seconds
Sep  3 15:52:01 node-1 CRON[19225]: (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  3 15:52:05 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  3 15:52:05 node-1 nailgun-agent: I, [2016-09-03T15:52:05.933616 #19228]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep  3 15:52:18 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  3 15:52:18 node-1 nailgun-agent: I, [2016-09-03T15:52:18.960921 #19228]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Sep  3 15:53:01 node-1 CRON[19540]: (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  3 15:53:03 node-1 anacron[8645]: Job `cron.daily' started
Sep  3 15:53:03 node-1 anacron[19554]: Updated timestamp for job `cron.daily' to 2016-09-03
Sep  3 15:53:07 node-1 anacron[8645]: Job `cron.daily' terminated
Sep  3 15:53:27 node-1 puppet-user[19693]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep  3 15:53:27 node-1 puppet-user[19693]: Compiled catalog for node-1.domain.tld in environment production in 0.56 seconds
Sep  3 15:53:28 node-1 puppet-user[19693]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep  3 15:53:28 node-1 puppet-user[19693]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep  3 15:53:28 node-1 puppet-user[19693]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep  3 15:53:28 node-1 puppet-user[19693]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep  3 15:53:28 node-1 puppet-user[19693]: Finished catalog run in 0.11 seconds
Sep  3 15:53:30 node-1 puppet-user[20143]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep  3 15:53:30 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  3 15:53:30 node-1 nailgun-agent: I, [2016-09-03T15:53:30.138656 #19543]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep  3 15:53:30 node-1 puppet-user[20143]: Compiled catalog for node-1.domain.tld in environment production in 0.83 seconds
Sep  3 15:53:31 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep  3 15:53:31 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep  3 15:53:31 node-1 crontab[20729]: (root) LIST (root)
Sep  3 15:53:31 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep  3 15:53:31 node-1 crontab[20730]: (root) REPLACE (root)
Sep  3 15:53:33 node-1 puppet-user[20143]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep  3 15:53:34 node-1 puppet-user[20143]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep  3 15:53:34 node-1 puppet-user[20143]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep  3 15:53:34 node-1 puppet-user[20143]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/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  3 15:53:35 node-1 puppet-user[20143]: (/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  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/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  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/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  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/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  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/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  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/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  3 15:53:35 node-1 puppet-user[20143]: (/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  3 15:53:35 node-1 puppet-user[20143]: (/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  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/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  3 15:53:35 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep  3 15:53:35 node-1 puppet-user[20143]: (/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  3 15:53:35 node-1 puppet-user[20143]: (/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  3 15:53:36 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep  3 15:53:36 node-1 puppet-user[20143]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep  3 15:53:36 node-1 puppet-user[20143]: (/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  3 15:53:36 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8426" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  3 15:53:36 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep  3 15:53:37 node-1 multipathd: uevent trigger error
<27>Sep  3 15:53:37 node-1 multipathd: uevent trigger error
<27>Sep  3 15:53:37 node-1 multipathd: uevent trigger error
<27>Sep  3 15:53:37 node-1 multipathd: uevent trigger error
<27>Sep  3 15:53:37 node-1 multipathd: uevent trigger error
<27>Sep  3 15:53:37 node-1 multipathd: uevent trigger error
<27>Sep  3 15:56:40 node-1 multipathd: uevent trigger error
<27>Sep  3 15:56:40 node-1 multipathd: uevent trigger error
<27>Sep  3 15:56:40 node-1 multipathd: uevent trigger error
<27>Sep  3 15:56:40 node-1 multipathd: uevent trigger error
<27>Sep  3 15:56:40 node-1 multipathd: uevent trigger error
<27>Sep  3 15:56:40 node-1 multipathd: uevent trigger error
<27>Sep  3 15:57:40 node-1 ntpdate[31968]: no servers can be used, exiting
<27>Sep  3 15:58:12 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:12 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:12 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:12 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:12 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:12 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:15 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:16 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:16 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:16 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:16 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:16 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:27 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:27 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:27 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:27 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:27 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:30 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:30 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:30 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:30 node-1 multipathd: uevent trigger error
<27>Sep  3 15:58:30 node-1 multipathd: uevent trigger error
<27>Sep  3 15:59:33 node-1 multipathd: uevent trigger error
<27>Sep  3 15:59:33 node-1 multipathd: uevent trigger error
<27>Sep  3 15:59:33 node-1 multipathd: uevent trigger error
<27>Sep  3 15:59:34 node-1 multipathd: uevent trigger error
<27>Sep  3 15:59:34 node-1 multipathd: uevent trigger error
<27>Sep  3 15:59:34 node-1 multipathd: uevent trigger error
<27>Sep  3 15:59:34 node-1 multipathd: uevent trigger error
<27>Sep  3 15:59:34 node-1 multipathd: uevent trigger error
<27>Sep  3 15:59:42 node-1 multipathd: uevent trigger error
<27>Sep  3 15:59:42 node-1 multipathd: uevent trigger error
<27>Sep  3 15:59:42 node-1 multipathd: uevent trigger error
<27>Sep  3 15:59:42 node-1 multipathd: uevent trigger error
<27>Sep  3 15:59:42 node-1 multipathd: uevent trigger error
<27>Sep  3 15:59:42 node-1 multipathd: uevent trigger error
<27>Sep  3 15:59:45 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  3 15:59:45 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep  3 15:59:51 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  3 15:59:51 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep  3 15:59:56 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep  3 16:00:02 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  3 16:00:02 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep  3 16:00:09 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:09 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:09 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:09 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:09 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:09 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:22 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:22 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:22 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:22 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:22 node-1 multipathd: uevent trigger error
<129>Sep  3 16:00:24 node-1 haproxy[25468]: 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  3 16:00:25 node-1 haproxy[25472]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:26 node-1 haproxy[25472]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:26 node-1 haproxy[25472]: proxy mysqld has no server available!
<27>Sep  3 16:00:28 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:28 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:28 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:28 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:28 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:31 node-1 multipathd: uevent trigger error
<129>Sep  3 16:00:34 node-1 haproxy[28005]: 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  3 16:00:34 node-1 haproxy[28005]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:34 node-1 haproxy[28005]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:34 node-1 haproxy[28005]: proxy mysqld has no server available!
<129>Sep  3 16:00:35 node-1 haproxy[28009]: 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  3 16:00:35 node-1 haproxy[28009]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:35 node-1 haproxy[28009]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:35 node-1 haproxy[28009]: proxy object-storage has no server available!
<27>Sep  3 16:00:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:37 node-1 multipathd: uevent trigger error
<129>Sep  3 16:00:39 node-1 haproxy[29358]: 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  3 16:00:39 node-1 haproxy[29358]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:40 node-1 haproxy[29364]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:40 node-1 haproxy[29364]: proxy neutron has no server available!
<129>Sep  3 16:00:40 node-1 haproxy[29364]: 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  3 16:00:40 node-1 haproxy[29364]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:40 node-1 haproxy[29364]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:40 node-1 haproxy[29364]: proxy mysqld has no server available!
<129>Sep  3 16:00:41 node-1 haproxy[29364]: 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  3 16:00:41 node-1 haproxy[29364]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:41 node-1 haproxy[29364]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:41 node-1 haproxy[29364]: proxy object-storage has no server available!
<27>Sep  3 16:00:42 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:42 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:42 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:42 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:42 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:42 node-1 multipathd: uevent trigger error
<129>Sep  3 16:00:45 node-1 haproxy[30809]: 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  3 16:00:45 node-1 haproxy[30809]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:45 node-1 haproxy[30809]: Server keystone-1/node-4 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  3 16:00:45 node-1 haproxy[30809]: proxy keystone-1 has no server available!
<129>Sep  3 16:00:45 node-1 haproxy[30809]: 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  3 16:00:46 node-1 haproxy[30816]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 2ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:46 node-1 haproxy[30816]: Server keystone-2/node-4 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  3 16:00:46 node-1 haproxy[30816]: proxy keystone-2 has no server available!
<129>Sep  3 16:00:46 node-1 haproxy[30816]: 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  3 16:00:46 node-1 haproxy[30816]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:46 node-1 haproxy[30816]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:46 node-1 haproxy[30816]: proxy neutron has no server available!
<129>Sep  3 16:00:46 node-1 haproxy[30816]: 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  3 16:00:46 node-1 haproxy[30816]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:46 node-1 haproxy[30816]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:46 node-1 haproxy[30816]: proxy mysqld has no server available!
<129>Sep  3 16:00:47 node-1 haproxy[30816]: 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  3 16:00:47 node-1 haproxy[30816]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:47 node-1 haproxy[30816]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:47 node-1 haproxy[30816]: proxy object-storage has no server available!
<27>Sep  3 16:00:48 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:48 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:48 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:48 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:48 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:48 node-1 multipathd: uevent trigger error
<129>Sep  3 16:00:50 node-1 haproxy[32169]: 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  3 16:00:51 node-1 haproxy[32173]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:51 node-1 haproxy[32173]: Server keystone-1/node-4 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  3 16:00:51 node-1 haproxy[32173]: proxy keystone-1 has no server available!
<129>Sep  3 16:00:51 node-1 haproxy[32173]: 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  3 16:00:51 node-1 haproxy[32173]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:51 node-1 haproxy[32173]: Server keystone-2/node-4 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  3 16:00:51 node-1 haproxy[32173]: proxy keystone-2 has no server available!
<129>Sep  3 16:00:51 node-1 haproxy[32173]: 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  3 16:00:51 node-1 haproxy[32173]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:51 node-1 haproxy[32173]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:51 node-1 haproxy[32173]: proxy neutron has no server available!
<129>Sep  3 16:00:51 node-1 haproxy[32173]: 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  3 16:00:52 node-1 haproxy[32173]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:52 node-1 haproxy[32173]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:52 node-1 haproxy[32173]: proxy mysqld has no server available!
<129>Sep  3 16:00:52 node-1 haproxy[32173]: 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  3 16:00:52 node-1 haproxy[32173]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:52 node-1 haproxy[32173]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:52 node-1 haproxy[32173]: proxy object-storage has no server available!
<129>Sep  3 16:00:52 node-1 haproxy[32173]: 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  3 16:00:52 node-1 haproxy[32173]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:52 node-1 haproxy[32173]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:52 node-1 haproxy[32173]: proxy aodh has no server available!
<27>Sep  3 16:00:54 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:54 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:54 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:54 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:54 node-1 multipathd: uevent trigger error
<129>Sep  3 16:00:56 node-1 haproxy[1093]: 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  3 16:00:56 node-1 haproxy[1093]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:56 node-1 haproxy[1093]: Server keystone-1/node-4 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  3 16:00:56 node-1 haproxy[1093]: proxy keystone-1 has no server available!
<129>Sep  3 16:00:56 node-1 haproxy[1093]: 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  3 16:00:56 node-1 haproxy[1093]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:56 node-1 haproxy[1093]: Server keystone-2/node-4 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  3 16:00:56 node-1 haproxy[1093]: proxy keystone-2 has no server available!
<129>Sep  3 16:00:56 node-1 haproxy[1093]: 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  3 16:00:56 node-1 haproxy[1093]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:57 node-1 haproxy[1097]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:57 node-1 haproxy[1097]: proxy neutron has no server available!
<129>Sep  3 16:00:57 node-1 haproxy[1097]: 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  3 16:00:57 node-1 haproxy[1097]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:57 node-1 haproxy[1097]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:57 node-1 haproxy[1097]: proxy mysqld has no server available!
<129>Sep  3 16:00:57 node-1 haproxy[1097]: 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  3 16:00:57 node-1 haproxy[1097]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:57 node-1 haproxy[1097]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:57 node-1 haproxy[1097]: proxy object-storage has no server available!
<129>Sep  3 16:00:57 node-1 haproxy[1097]: 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  3 16:00:57 node-1 haproxy[1097]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:57 node-1 haproxy[1097]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:57 node-1 haproxy[1097]: proxy aodh has no server available!
<129>Sep  3 16:00:58 node-1 haproxy[1097]: 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  3 16:00:58 node-1 haproxy[1097]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:00:58 node-1 haproxy[1097]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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  3 16:00:58 node-1 haproxy[1097]: proxy ceilometer has no server available!
<27>Sep  3 16:00:59 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:59 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:59 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:59 node-1 multipathd: uevent trigger error
<27>Sep  3 16:00:59 node-1 multipathd: uevent trigger error
<129>Sep  3 16:01:01 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  3 16:01:01 node-1 haproxy[2451]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:01 node-1 haproxy[2451]: Server keystone-1/node-4 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  3 16:01:01 node-1 haproxy[2451]: proxy keystone-1 has no server available!
<129>Sep  3 16:01:02 node-1 haproxy[2455]: 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  3 16:01:02 node-1 haproxy[2455]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:02 node-1 haproxy[2455]: Server keystone-2/node-4 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  3 16:01:02 node-1 haproxy[2455]: proxy keystone-2 has no server available!
<129>Sep  3 16:01:02 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  3 16:01:02 node-1 haproxy[2455]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:02 node-1 haproxy[2455]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:02 node-1 haproxy[2455]: proxy neutron has no server available!
<129>Sep  3 16:01:02 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  3 16:01:02 node-1 haproxy[2455]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:02 node-1 haproxy[2455]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:02 node-1 haproxy[2455]: proxy mysqld has no server available!
<129>Sep  3 16:01:02 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  3 16:01:02 node-1 haproxy[2455]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:03 node-1 haproxy[2455]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:03 node-1 haproxy[2455]: proxy object-storage has no server available!
<129>Sep  3 16:01:03 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  3 16:01:03 node-1 haproxy[2455]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:03 node-1 haproxy[2455]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:03 node-1 haproxy[2455]: proxy aodh has no server available!
<129>Sep  3 16:01:03 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  3 16:01:03 node-1 haproxy[2455]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:03 node-1 haproxy[2455]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:03 node-1 haproxy[2455]: proxy ceilometer has no server available!
<27>Sep  3 16:01:04 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:04 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:04 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:04 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:04 node-1 multipathd: uevent trigger error
<129>Sep  3 16:01:07 node-1 haproxy[3789]: 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  3 16:01:07 node-1 haproxy[3789]: 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  3 16:01:07 node-1 haproxy[3789]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:07 node-1 haproxy[3789]: Server keystone-1/node-4 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  3 16:01:07 node-1 haproxy[3789]: proxy keystone-1 has no server available!
<129>Sep  3 16:01:07 node-1 haproxy[3789]: 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  3 16:01:07 node-1 haproxy[3789]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:07 node-1 haproxy[3789]: Server keystone-2/node-4 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  3 16:01:07 node-1 haproxy[3789]: proxy keystone-2 has no server available!
<129>Sep  3 16:01:07 node-1 haproxy[3789]: 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  3 16:01:07 node-1 haproxy[3789]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:07 node-1 haproxy[3789]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:07 node-1 haproxy[3789]: proxy neutron has no server available!
<129>Sep  3 16:01:08 node-1 haproxy[3793]: 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  3 16:01:08 node-1 haproxy[3793]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:08 node-1 haproxy[3793]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:08 node-1 haproxy[3793]: proxy mysqld has no server available!
<129>Sep  3 16:01:08 node-1 haproxy[3793]: 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  3 16:01:08 node-1 haproxy[3793]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:08 node-1 haproxy[3793]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:08 node-1 haproxy[3793]: proxy object-storage has no server available!
<129>Sep  3 16:01:08 node-1 haproxy[3793]: 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  3 16:01:08 node-1 haproxy[3793]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:08 node-1 haproxy[3793]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:08 node-1 haproxy[3793]: proxy aodh has no server available!
<129>Sep  3 16:01:08 node-1 haproxy[3793]: 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  3 16:01:08 node-1 haproxy[3793]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:08 node-1 haproxy[3793]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:08 node-1 haproxy[3793]: proxy ceilometer has no server available!
<27>Sep  3 16:01:10 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:10 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:10 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:10 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:10 node-1 multipathd: uevent trigger error
<129>Sep  3 16:01:12 node-1 haproxy[5184]: 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  3 16:01:13 node-1 haproxy[5195]: 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  3 16:01:13 node-1 haproxy[5195]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:13 node-1 haproxy[5195]: Server keystone-1/node-4 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  3 16:01:13 node-1 haproxy[5195]: proxy keystone-1 has no server available!
<129>Sep  3 16:01:13 node-1 haproxy[5195]: 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  3 16:01:13 node-1 haproxy[5195]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:13 node-1 haproxy[5195]: Server keystone-2/node-4 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  3 16:01:13 node-1 haproxy[5195]: proxy keystone-2 has no server available!
<129>Sep  3 16:01:13 node-1 haproxy[5195]: 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  3 16:01:13 node-1 haproxy[5195]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:13 node-1 haproxy[5195]: Server glance-api/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:13 node-1 haproxy[5195]: proxy glance-api has no server available!
<129>Sep  3 16:01:13 node-1 haproxy[5195]: 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  3 16:01:13 node-1 haproxy[5195]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:13 node-1 haproxy[5195]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:13 node-1 haproxy[5195]: proxy glance-glare has no server available!
<129>Sep  3 16:01:13 node-1 haproxy[5195]: 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  3 16:01:13 node-1 haproxy[5195]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:13 node-1 haproxy[5195]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:13 node-1 haproxy[5195]: proxy neutron has no server available!
<129>Sep  3 16:01:13 node-1 haproxy[5195]: 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  3 16:01:13 node-1 haproxy[5195]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:14 node-1 haproxy[5195]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:14 node-1 haproxy[5195]: proxy glance-registry has no server available!
<129>Sep  3 16:01:14 node-1 haproxy[5195]: 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  3 16:01:14 node-1 haproxy[5195]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:14 node-1 haproxy[5195]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:14 node-1 haproxy[5195]: proxy mysqld has no server available!
<129>Sep  3 16:01:14 node-1 haproxy[5195]: 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  3 16:01:14 node-1 haproxy[5195]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:14 node-1 haproxy[5195]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:14 node-1 haproxy[5195]: proxy object-storage has no server available!
<129>Sep  3 16:01:14 node-1 haproxy[5195]: 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  3 16:01:14 node-1 haproxy[5195]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:14 node-1 haproxy[5195]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:14 node-1 haproxy[5195]: proxy aodh has no server available!
<129>Sep  3 16:01:14 node-1 haproxy[5195]: 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  3 16:01:14 node-1 haproxy[5195]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:14 node-1 haproxy[5195]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:14 node-1 haproxy[5195]: proxy ceilometer has no server available!
<27>Sep  3 16:01:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:16 node-1 multipathd: uevent trigger error
<129>Sep  3 16:01:18 node-1 haproxy[6603]: 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  3 16:01:19 node-1 haproxy[6609]: 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  3 16:01:19 node-1 haproxy[6609]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:19 node-1 haproxy[6609]: Server keystone-1/node-4 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  3 16:01:19 node-1 haproxy[6609]: proxy keystone-1 has no server available!
<129>Sep  3 16:01:19 node-1 haproxy[6609]: 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  3 16:01:19 node-1 haproxy[6609]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:19 node-1 haproxy[6609]: Server keystone-2/node-4 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  3 16:01:19 node-1 haproxy[6609]: proxy keystone-2 has no server available!
<129>Sep  3 16:01:19 node-1 haproxy[6609]: 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  3 16:01:19 node-1 haproxy[6609]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:19 node-1 haproxy[6609]: Server nova-api/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:19 node-1 haproxy[6609]: proxy nova-api has no server available!
<129>Sep  3 16:01:19 node-1 haproxy[6609]: 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  3 16:01:19 node-1 haproxy[6609]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:19 node-1 haproxy[6609]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:19 node-1 haproxy[6609]: proxy nova-metadata-api has no server available!
<129>Sep  3 16:01:19 node-1 haproxy[6609]: 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  3 16:01:19 node-1 haproxy[6609]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:19 node-1 haproxy[6609]: Server glance-api/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:19 node-1 haproxy[6609]: proxy glance-api has no server available!
<129>Sep  3 16:01:19 node-1 haproxy[6609]: 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  3 16:01:19 node-1 haproxy[6609]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:19 node-1 haproxy[6609]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:19 node-1 haproxy[6609]: proxy glance-glare has no server available!
<129>Sep  3 16:01:19 node-1 haproxy[6609]: 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  3 16:01:20 node-1 haproxy[6609]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:20 node-1 haproxy[6609]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:20 node-1 haproxy[6609]: proxy neutron has no server available!
<129>Sep  3 16:01:20 node-1 haproxy[6609]: 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  3 16:01:20 node-1 haproxy[6609]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:20 node-1 haproxy[6609]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:20 node-1 haproxy[6609]: proxy glance-registry has no server available!
<129>Sep  3 16:01:20 node-1 haproxy[6609]: 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  3 16:01:20 node-1 haproxy[6609]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:20 node-1 haproxy[6609]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:20 node-1 haproxy[6609]: proxy mysqld has no server available!
<129>Sep  3 16:01:20 node-1 haproxy[6609]: 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  3 16:01:20 node-1 haproxy[6609]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:20 node-1 haproxy[6609]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:20 node-1 haproxy[6609]: proxy object-storage has no server available!
<129>Sep  3 16:01:20 node-1 haproxy[6609]: 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  3 16:01:20 node-1 haproxy[6609]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:20 node-1 haproxy[6609]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:20 node-1 haproxy[6609]: proxy aodh has no server available!
<129>Sep  3 16:01:20 node-1 haproxy[6609]: 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  3 16:01:20 node-1 haproxy[6609]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:20 node-1 haproxy[6609]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:20 node-1 haproxy[6609]: proxy ceilometer has no server available!
<129>Sep  3 16:01:20 node-1 haproxy[6609]: 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  3 16:01:20 node-1 haproxy[6609]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:20 node-1 haproxy[6609]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:20 node-1 haproxy[6609]: proxy nova-novncproxy has no server available!
<27>Sep  3 16:01:22 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:22 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:22 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:22 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:22 node-1 multipathd: uevent trigger error
<129>Sep  3 16:01:24 node-1 haproxy[7912]: 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  3 16:01:24 node-1 haproxy[7912]: 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  3 16:01:24 node-1 haproxy[7912]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:24 node-1 haproxy[7912]: Server keystone-1/node-4 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  3 16:01:24 node-1 haproxy[7912]: proxy keystone-1 has no server available!
<129>Sep  3 16:01:24 node-1 haproxy[7912]: 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  3 16:01:24 node-1 haproxy[7912]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:24 node-1 haproxy[7912]: Server keystone-2/node-4 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  3 16:01:24 node-1 haproxy[7912]: proxy keystone-2 has no server available!
<129>Sep  3 16:01:24 node-1 haproxy[7912]: 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  3 16:01:24 node-1 haproxy[7912]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:24 node-1 haproxy[7912]: Server nova-api/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:24 node-1 haproxy[7912]: proxy nova-api has no server available!
<129>Sep  3 16:01:24 node-1 haproxy[7912]: 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  3 16:01:24 node-1 haproxy[7912]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:25 node-1 haproxy[7916]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:25 node-1 haproxy[7916]: proxy nova-metadata-api has no server available!
<129>Sep  3 16:01:25 node-1 haproxy[7916]: 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  3 16:01:25 node-1 haproxy[7916]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:25 node-1 haproxy[7916]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:25 node-1 haproxy[7916]: proxy cinder-api has no server available!
<129>Sep  3 16:01:25 node-1 haproxy[7916]: 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  3 16:01:25 node-1 haproxy[7916]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:25 node-1 haproxy[7916]: Server glance-api/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:25 node-1 haproxy[7916]: proxy glance-api has no server available!
<129>Sep  3 16:01:25 node-1 haproxy[7916]: 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  3 16:01:25 node-1 haproxy[7916]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:25 node-1 haproxy[7916]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:25 node-1 haproxy[7916]: proxy glance-glare has no server available!
<129>Sep  3 16:01:25 node-1 haproxy[7916]: 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  3 16:01:25 node-1 haproxy[7916]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:25 node-1 haproxy[7916]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:25 node-1 haproxy[7916]: proxy neutron has no server available!
<129>Sep  3 16:01:25 node-1 haproxy[7916]: 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  3 16:01:25 node-1 haproxy[7916]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:25 node-1 haproxy[7916]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:25 node-1 haproxy[7916]: proxy glance-registry has no server available!
<129>Sep  3 16:01:25 node-1 haproxy[7916]: 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  3 16:01:25 node-1 haproxy[7916]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:25 node-1 haproxy[7916]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:25 node-1 haproxy[7916]: proxy mysqld has no server available!
<129>Sep  3 16:01:25 node-1 haproxy[7916]: 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  3 16:01:25 node-1 haproxy[7916]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:25 node-1 haproxy[7916]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:25 node-1 haproxy[7916]: proxy object-storage has no server available!
<129>Sep  3 16:01:26 node-1 haproxy[7916]: 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  3 16:01:26 node-1 haproxy[7916]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:26 node-1 haproxy[7916]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:26 node-1 haproxy[7916]: proxy aodh has no server available!
<129>Sep  3 16:01:26 node-1 haproxy[7916]: 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  3 16:01:26 node-1 haproxy[7916]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:26 node-1 haproxy[7916]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:26 node-1 haproxy[7916]: proxy ceilometer has no server available!
<129>Sep  3 16:01:26 node-1 haproxy[7916]: 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  3 16:01:26 node-1 haproxy[7916]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:26 node-1 haproxy[7916]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:26 node-1 haproxy[7916]: proxy nova-novncproxy has no server available!
<27>Sep  3 16:01:27 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:27 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:27 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:27 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:27 node-1 multipathd: uevent trigger error
<129>Sep  3 16:01:30 node-1 haproxy[9451]: 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  3 16:01:30 node-1 haproxy[9451]: 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  3 16:01:30 node-1 haproxy[9451]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:30 node-1 haproxy[9451]: Server keystone-1/node-4 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  3 16:01:30 node-1 haproxy[9451]: proxy keystone-1 has no server available!
<129>Sep  3 16:01:30 node-1 haproxy[9451]: 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  3 16:01:30 node-1 haproxy[9451]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:30 node-1 haproxy[9451]: Server keystone-2/node-4 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  3 16:01:30 node-1 haproxy[9451]: proxy keystone-2 has no server available!
<129>Sep  3 16:01:30 node-1 haproxy[9451]: 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  3 16:01:30 node-1 haproxy[9451]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:30 node-1 haproxy[9451]: Server nova-api/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:30 node-1 haproxy[9451]: proxy nova-api has no server available!
<129>Sep  3 16:01:30 node-1 haproxy[9451]: 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  3 16:01:30 node-1 haproxy[9451]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:30 node-1 haproxy[9451]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:30 node-1 haproxy[9451]: proxy nova-metadata-api has no server available!
<129>Sep  3 16:01:30 node-1 haproxy[9451]: 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  3 16:01:30 node-1 haproxy[9451]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:30 node-1 haproxy[9451]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:30 node-1 haproxy[9451]: proxy cinder-api has no server available!
<129>Sep  3 16:01:30 node-1 haproxy[9451]: 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  3 16:01:30 node-1 haproxy[9451]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:30 node-1 haproxy[9451]: Server glance-api/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:30 node-1 haproxy[9451]: proxy glance-api has no server available!
<129>Sep  3 16:01:31 node-1 haproxy[9455]: 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  3 16:01:31 node-1 haproxy[9455]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:31 node-1 haproxy[9455]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:31 node-1 haproxy[9455]: proxy glance-glare has no server available!
<129>Sep  3 16:01:31 node-1 haproxy[9455]: 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  3 16:01:31 node-1 haproxy[9455]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:31 node-1 haproxy[9455]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:31 node-1 haproxy[9455]: proxy neutron has no server available!
<129>Sep  3 16:01:31 node-1 haproxy[9455]: 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  3 16:01:31 node-1 haproxy[9455]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:31 node-1 haproxy[9455]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:31 node-1 haproxy[9455]: proxy glance-registry has no server available!
<129>Sep  3 16:01:31 node-1 haproxy[9455]: 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  3 16:01:31 node-1 haproxy[9455]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:31 node-1 haproxy[9455]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:31 node-1 haproxy[9455]: proxy mysqld has no server available!
<129>Sep  3 16:01:31 node-1 haproxy[9455]: 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  3 16:01:31 node-1 haproxy[9455]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:31 node-1 haproxy[9455]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:31 node-1 haproxy[9455]: proxy object-storage has no server available!
<129>Sep  3 16:01:31 node-1 haproxy[9455]: 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  3 16:01:31 node-1 haproxy[9455]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:31 node-1 haproxy[9455]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:31 node-1 haproxy[9455]: proxy aodh has no server available!
<129>Sep  3 16:01:31 node-1 haproxy[9455]: 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  3 16:01:31 node-1 haproxy[9455]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:31 node-1 haproxy[9455]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:31 node-1 haproxy[9455]: proxy ceilometer has no server available!
<129>Sep  3 16:01:31 node-1 haproxy[9455]: 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  3 16:01:31 node-1 haproxy[9455]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:31 node-1 haproxy[9455]: Server heat-api/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:31 node-1 haproxy[9455]: proxy heat-api has no server available!
<129>Sep  3 16:01:31 node-1 haproxy[9455]: 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  3 16:01:31 node-1 haproxy[9455]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:31 node-1 haproxy[9455]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:31 node-1 haproxy[9455]: proxy heat-api-cfn has no server available!
<129>Sep  3 16:01:32 node-1 haproxy[9455]: 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  3 16:01:32 node-1 haproxy[9455]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:32 node-1 haproxy[9455]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:32 node-1 haproxy[9455]: proxy heat-api-cloudwatch has no server available!
<129>Sep  3 16:01:32 node-1 haproxy[9455]: 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  3 16:01:32 node-1 haproxy[9455]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep  3 16:01:32 node-1 haproxy[9455]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection 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  3 16:01:32 node-1 haproxy[9455]: proxy nova-novncproxy has no server available!
<27>Sep  3 16:01:33 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:33 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:33 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:33 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:33 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:01:48 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep  3 16:01:56 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  3 16:02:04 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  3 16:02:16 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  3 16:02:18 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep  3 16:03:15 node-1 multipathd: uevent trigger error
<27>Sep  3 16:03:15 node-1 multipathd: uevent trigger error
<27>Sep  3 16:03:15 node-1 multipathd: uevent trigger error
<27>Sep  3 16:03:15 node-1 multipathd: uevent trigger error
<27>Sep  3 16:03:15 node-1 multipathd: uevent trigger error
<27>Sep  3 16:03:15 node-1 multipathd: uevent trigger error
<27>Sep  3 16:05:08 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  3 16:05:38 node-1 multipathd: uevent trigger error
<27>Sep  3 16:05:38 node-1 multipathd: uevent trigger error
<27>Sep  3 16:05:38 node-1 multipathd: uevent trigger error
<27>Sep  3 16:05:38 node-1 multipathd: uevent trigger error
<27>Sep  3 16:05:38 node-1 multipathd: uevent trigger error
<27>Sep  3 16:05:38 node-1 multipathd: uevent trigger error
<27>Sep  3 16:05:38 node-1 multipathd: uevent trigger error
<27>Sep  3 16:05:45 node-1 multipathd: uevent trigger error
<27>Sep  3 16:05:45 node-1 multipathd: uevent trigger error
<27>Sep  3 16:05:45 node-1 multipathd: uevent trigger error
<27>Sep  3 16:05:45 node-1 multipathd: uevent trigger error
<27>Sep  3 16:05:45 node-1 multipathd: uevent trigger error
<43>Sep  3 16:06:07 node-1 apache2_error [Sat Sep 03 16:05:59.340400 2016] [mpm_event:notice] [pid 22079:tid 140091400968064] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep  3 16:06:07 node-1 apache2_error [Sat Sep 03 16:05:59.340546 2016] [core:notice] [pid 22079:tid 140091400968064] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep  3 16:06:07 node-1 apache2_error [Sat Sep 03 16:06:02.676555 2016] [mpm_event:notice] [pid 22079:tid 140091400968064] AH00491: caught SIGTERM, shutting down
<43>Sep  3 16:06:07 node-1 apache2_error [Sat Sep 03 16:06:03.766317 2016] [mpm_worker:notice] [pid 22456:tid 139719039051648] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep  3 16:06:07 node-1 apache2_error [Sat Sep 03 16:06:03.766376 2016] [core:notice] [pid 22456:tid 139719039051648] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  3 16:06:08 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:08 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:08 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:08 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:08 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:08 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:13 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:13 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:13 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:13 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:13 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:13 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:17 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:17 node-1 multipathd: uevent trigger error
<27>Sep  3 16:06:17 node-1 multipathd: uevent trigger error
<43>Sep  3 16:07:37 node-1 apache2_error [Sat Sep 03 16:07:31.531429 2016] [mpm_worker:notice] [pid 22456:tid 139719039051648] AH00295: caught SIGTERM, shutting down
<43>Sep  3 16:07:37 node-1 apache2_error [Sat Sep 03 16:07:32.288958 2016] [mpm_worker:notice] [pid 5995:tid 139785286686592] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  3 16:07:37 node-1 apache2_error [Sat Sep 03 16:07:32.289026 2016] [core:notice] [pid 5995:tid 139785286686592] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  3 16:08:26 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep  3 16:08:27 node-1 apache2_error [Sat Sep 03 16:08:18.105038 2016] [mpm_worker:notice] [pid 5995:tid 139785286686592] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep  3 16:08:27 node-1 apache2_error [Sat Sep 03 16:08:18.300998 2016] [mpm_worker:warn] [pid 5995:tid 139785286686592] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep  3 16:08:27 node-1 apache2_error [Sat Sep 03 16:08:18.306015 2016] [mpm_worker:notice] [pid 5995:tid 139785286686592] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  3 16:08:27 node-1 apache2_error [Sat Sep 03 16:08:18.306041 2016] [core:notice] [pid 5995:tid 139785286686592] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  3 16:09:04 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:04 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:04 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:04 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:04 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:04 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:09 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:09 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:09 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:09 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:09 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:25 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:25 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:25 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:25 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:25 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:25 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:25 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:50 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:50 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:50 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:50 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:50 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:55 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:55 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:55 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:55 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:55 node-1 multipathd: uevent trigger error
<27>Sep  3 16:09:56 node-1 multipathd: uevent trigger error
<27>Sep  3 16:10:43 node-1 multipathd: uevent trigger error
<27>Sep  3 16:10:43 node-1 multipathd: uevent trigger error
<27>Sep  3 16:10:43 node-1 multipathd: uevent trigger error
<27>Sep  3 16:10:43 node-1 multipathd: uevent trigger error
<27>Sep  3 16:10:43 node-1 multipathd: uevent trigger error
<27>Sep  3 16:10:58 node-1 multipathd: uevent trigger error
<27>Sep  3 16:10:58 node-1 multipathd: uevent trigger error
<27>Sep  3 16:10:58 node-1 multipathd: uevent trigger error
<27>Sep  3 16:10:58 node-1 multipathd: uevent trigger error
<27>Sep  3 16:10:58 node-1 multipathd: uevent trigger error
<27>Sep  3 16:11:37 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  3 16:11:52 node-1 multipathd: uevent trigger error
<27>Sep  3 16:11:52 node-1 multipathd: uevent trigger error
<27>Sep  3 16:11:52 node-1 multipathd: uevent trigger error
<27>Sep  3 16:11:52 node-1 multipathd: uevent trigger error
<27>Sep  3 16:11:52 node-1 multipathd: uevent trigger error
<27>Sep  3 16:13:07 node-1 multipathd: uevent trigger error
<27>Sep  3 16:13:07 node-1 multipathd: uevent trigger error
<27>Sep  3 16:13:07 node-1 multipathd: uevent trigger error
<27>Sep  3 16:13:07 node-1 multipathd: uevent trigger error
<27>Sep  3 16:13:07 node-1 multipathd: uevent trigger error
<27>Sep  3 16:13:07 node-1 multipathd: uevent trigger error
<27>Sep  3 16:14:10 node-1 multipathd: uevent trigger error
<27>Sep  3 16:14:10 node-1 multipathd: uevent trigger error
<27>Sep  3 16:14:10 node-1 multipathd: uevent trigger error
<27>Sep  3 16:14:10 node-1 multipathd: uevent trigger error
<27>Sep  3 16:14:10 node-1 multipathd: uevent trigger error
<27>Sep  3 16:14:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:14:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:14:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:14:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:14:32 node-1 multipathd: uevent trigger error
<27>Sep  3 16:14:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:14:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:14:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:14:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:14:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:14:40 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  3 16:17:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:17:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:17:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:17:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:17:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:17:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:17:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:17:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:17:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:17:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:17:36 node-1 multipathd: uevent trigger error
<27>Sep  3 16:17:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:17:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:17:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:17:37 node-1 multipathd: uevent trigger error
<27>Sep  3 16:17:41 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  3 16:18:20 node-1 multipathd: uevent trigger error
<27>Sep  3 16:18:20 node-1 multipathd: uevent trigger error
<27>Sep  3 16:18:20 node-1 multipathd: uevent trigger error
<27>Sep  3 16:18:20 node-1 multipathd: uevent trigger error
<27>Sep  3 16:18:20 node-1 multipathd: uevent trigger error
<27>Sep  3 16:18:25 node-1 multipathd: uevent trigger error
<27>Sep  3 16:18:25 node-1 multipathd: uevent trigger error
<27>Sep  3 16:18:25 node-1 multipathd: uevent trigger error
<27>Sep  3 16:18:25 node-1 multipathd: uevent trigger error
<27>Sep  3 16:18:25 node-1 multipathd: uevent trigger error
<27>Sep  3 16:18:26 node-1 multipathd: uevent trigger error
<27>Sep  3 16:18:50 node-1 multipathd: uevent trigger error
<27>Sep  3 16:18:50 node-1 multipathd: uevent trigger error
<27>Sep  3 16:18:50 node-1 multipathd: uevent trigger error
<27>Sep  3 16:18:50 node-1 multipathd: uevent trigger error
<27>Sep  3 16:18:50 node-1 multipathd: uevent trigger error
<27>Sep  3 16:19:34 node-1 multipathd: uevent trigger error
<27>Sep  3 16:19:34 node-1 multipathd: uevent trigger error
<27>Sep  3 16:19:34 node-1 multipathd: uevent trigger error
<27>Sep  3 16:19:34 node-1 multipathd: uevent trigger error
<27>Sep  3 16:19:34 node-1 multipathd: uevent trigger error
<27>Sep  3 16:19:41 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Sep  3 16:19:41 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Sep  3 16:19:41 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Sep  3 16:19:42 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Sep  3 16:19:42 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Sep  3 16:19:43 node-1 multipathd: uevent trigger error
<27>Sep  3 16:19:43 node-1 multipathd: uevent trigger error
<27>Sep  3 16:19:43 node-1 multipathd: uevent trigger error
<27>Sep  3 16:19:43 node-1 multipathd: uevent trigger error
<27>Sep  3 16:19:43 node-1 multipathd: uevent trigger error
<27>Sep  3 16:19:43 node-1 multipathd: uevent trigger error
<27>Sep  3 16:19:56 node-1 multipathd: uevent trigger error
<27>Sep  3 16:19:56 node-1 multipathd: uevent trigger error
<27>Sep  3 16:19:56 node-1 multipathd: uevent trigger error
<27>Sep  3 16:19:56 node-1 multipathd: uevent trigger error
<27>Sep  3 16:19:56 node-1 multipathd: uevent trigger error
<27>Sep  3 16:20:11 node-1 multipathd: uevent trigger error
<27>Sep  3 16:20:11 node-1 multipathd: uevent trigger error
<27>Sep  3 16:20:11 node-1 multipathd: uevent trigger error
<27>Sep  3 16:20:11 node-1 multipathd: uevent trigger error
<27>Sep  3 16:20:11 node-1 multipathd: uevent trigger error
<27>Sep  3 16:20:11 node-1 multipathd: uevent trigger error
<27>Sep  3 16:20:11 node-1 multipathd: uevent trigger error
<27>Sep  3 16:20:11 node-1 multipathd: uevent trigger error
<27>Sep  3 16:20:30 node-1 multipathd: uevent trigger error
<27>Sep  3 16:20:30 node-1 multipathd: uevent trigger error
<27>Sep  3 16:20:30 node-1 multipathd: uevent trigger error
<27>Sep  3 16:20:30 node-1 multipathd: uevent trigger error
<27>Sep  3 16:20:30 node-1 multipathd: uevent trigger error
<27>Sep  3 16:20:43 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  3 16:22:51 node-1 multipathd: uevent trigger error
<27>Sep  3 16:22:51 node-1 multipathd: uevent trigger error
<27>Sep  3 16:22:51 node-1 multipathd: uevent trigger error
<27>Sep  3 16:22:51 node-1 multipathd: uevent trigger error
<27>Sep  3 16:22:51 node-1 multipathd: uevent trigger error
<27>Sep  3 16:23:36 node-1 multipathd: uevent trigger error
<27>Sep  3 16:23:36 node-1 multipathd: uevent trigger error
<27>Sep  3 16:23:36 node-1 multipathd: uevent trigger error
<27>Sep  3 16:23:36 node-1 multipathd: uevent trigger error
<27>Sep  3 16:23:36 node-1 multipathd: uevent trigger error
<27>Sep  3 16:23:41 node-1 multipathd: uevent trigger error
<27>Sep  3 16:23:41 node-1 multipathd: uevent trigger error
<27>Sep  3 16:23:41 node-1 multipathd: uevent trigger error
<27>Sep  3 16:23:41 node-1 multipathd: uevent trigger error
<27>Sep  3 16:23:41 node-1 multipathd: uevent trigger error
<27>Sep  3 16:23:42 node-1 multipathd: uevent trigger error
<27>Sep  3 16:23:44 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  3 16:24:14 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:14 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:14 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:14 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:14 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:26 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:26 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:26 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:26 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:26 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:30 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:30 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:30 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:30 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:30 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:35 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:35 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:35 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:35 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:35 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:41 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:41 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:41 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:41 node-1 multipathd: uevent trigger error
<27>Sep  3 16:24:41 node-1 multipathd: uevent trigger error
<27>Sep  3 16:25:24 node-1 multipathd: uevent trigger error
<27>Sep  3 16:25:24 node-1 multipathd: uevent trigger error
<27>Sep  3 16:25:24 node-1 multipathd: uevent trigger error
<27>Sep  3 16:25:24 node-1 multipathd: uevent trigger error
<27>Sep  3 16:25:24 node-1 multipathd: uevent trigger error
<27>Sep  3 16:25:24 node-1 multipathd: uevent trigger error
<27>Sep  3 16:25:24 node-1 multipathd: uevent trigger error
<27>Sep  3 16:26:33 node-1 multipathd: uevent trigger error
<27>Sep  3 16:26:33 node-1 multipathd: uevent trigger error
<27>Sep  3 16:26:33 node-1 multipathd: uevent trigger error
<27>Sep  3 16:26:33 node-1 multipathd: uevent trigger error
<27>Sep  3 16:26:33 node-1 multipathd: uevent trigger error
<27>Sep  3 16:26:46 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  3 16:26:51 node-1 multipathd: uevent trigger error
<27>Sep  3 16:26:51 node-1 multipathd: uevent trigger error
<27>Sep  3 16:26:51 node-1 multipathd: uevent trigger error
<27>Sep  3 16:26:51 node-1 multipathd: uevent trigger error
<27>Sep  3 16:26:51 node-1 multipathd: uevent trigger error
<11>Sep  3 16:27:05 node-1 liberasurecode[6600]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:05 node-1 liberasurecode[6600]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:05 node-1 liberasurecode[6600]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:05 node-1 liberasurecode[6600]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:05 node-1 liberasurecode[6631]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:05 node-1 liberasurecode[6631]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:05 node-1 liberasurecode[6631]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:05 node-1 liberasurecode[6631]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:07 node-1 liberasurecode[7037]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:07 node-1 liberasurecode[7037]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:07 node-1 liberasurecode[7037]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:07 node-1 liberasurecode[7037]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:13 node-1 liberasurecode[7656]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:13 node-1 liberasurecode[7656]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:13 node-1 liberasurecode[7656]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:13 node-1 liberasurecode[7656]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:13 node-1 liberasurecode[7694]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:13 node-1 liberasurecode[7694]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:13 node-1 liberasurecode[7694]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:13 node-1 liberasurecode[7694]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:13 node-1 liberasurecode[7754]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:13 node-1 liberasurecode[7754]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:13 node-1 liberasurecode[7754]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:13 node-1 liberasurecode[7754]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:13 node-1 liberasurecode[7814]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:13 node-1 liberasurecode[7814]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:13 node-1 liberasurecode[7814]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:13 node-1 liberasurecode[7814]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:14 node-1 liberasurecode[7830]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:14 node-1 liberasurecode[7830]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:14 node-1 liberasurecode[7830]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:14 node-1 liberasurecode[7830]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:14 node-1 liberasurecode[7843]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:14 node-1 liberasurecode[7843]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:14 node-1 liberasurecode[7843]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:14 node-1 liberasurecode[7843]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:14 node-1 liberasurecode[7855]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:14 node-1 liberasurecode[7855]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:14 node-1 liberasurecode[7855]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:14 node-1 liberasurecode[7855]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:22 node-1 liberasurecode[8469]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:22 node-1 liberasurecode[8469]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:22 node-1 liberasurecode[8469]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:27:22 node-1 liberasurecode[8469]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep  3 16:27:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:27:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:27:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:27:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:27:31 node-1 multipathd: uevent trigger error
<43>Sep  3 16:28:19 node-1 apache2_error [Sat Sep 03 16:28:19.016520 2016] [mpm_worker:notice] [pid 5995:tid 139785286686592] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep  3 16:28:29 node-1 apache2_error [Sat Sep 03 16:28:19.399256 2016] [mpm_worker:warn] [pid 5995:tid 139785286686592] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep  3 16:28:29 node-1 apache2_error [Sat Sep 03 16:28:19.402685 2016] [mpm_worker:notice] [pid 5995:tid 139785286686592] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  3 16:28:29 node-1 apache2_error [Sat Sep 03 16:28:19.402706 2016] [core:notice] [pid 5995:tid 139785286686592] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep  3 16:28:59 node-1 apache2_error [Sat Sep 03 16:28:56.712731 2016] [mpm_worker:notice] [pid 5995:tid 139785286686592] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep  3 16:28:59 node-1 apache2_error [Sat Sep 03 16:28:56.909866 2016] [mpm_worker:warn] [pid 5995:tid 139785286686592] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep  3 16:28:59 node-1 apache2_error [Sat Sep 03 16:28:56.918866 2016] [mpm_worker:notice] [pid 5995:tid 139785286686592] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  3 16:28:59 node-1 apache2_error [Sat Sep 03 16:28:56.918898 2016] [core:notice] [pid 5995:tid 139785286686592] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  3 16:29:01 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:01 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:01 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:01 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:01 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:08 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:08 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:08 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:08 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:08 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:47 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:47 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:47 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:47 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:47 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:47 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:47 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep  3 16:29:49 node-1 apache2_error [Sat Sep 03 16:29:43.145196 2016] [mpm_worker:notice] [pid 5995:tid 139785286686592] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep  3 16:29:49 node-1 apache2_error [Sat Sep 03 16:29:43.343234 2016] [mpm_worker:warn] [pid 5995:tid 139785286686592] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep  3 16:29:49 node-1 apache2_error [Sat Sep 03 16:29:43.355214 2016] [mpm_worker:notice] [pid 5995:tid 139785286686592] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  3 16:29:49 node-1 apache2_error [Sat Sep 03 16:29:43.355243 2016] [core:notice] [pid 5995:tid 139785286686592] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  3 16:29:54 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:54 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:54 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:54 node-1 multipathd: uevent trigger error
<27>Sep  3 16:29:54 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:00 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:00 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:00 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:00 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:00 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:00 node-1 multipathd: uevent trigger error
<11>Sep  3 16:30:01 node-1 liberasurecode[6099]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:30:01 node-1 liberasurecode[6099]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:30:01 node-1 liberasurecode[6099]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:30:01 node-1 liberasurecode[6099]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep  3 16:30:17 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:17 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:17 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:17 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:17 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:17 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:40 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:48 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:48 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:48 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:48 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:48 node-1 multipathd: uevent trigger error
<27>Sep  3 16:30:55 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep  3 16:31:04 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:05 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:05 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:05 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:05 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:09 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:09 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:09 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:09 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:09 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:15 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:15 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:15 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:15 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:15 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:20 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:20 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:20 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:20 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:20 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:20 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:31 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  3 16:31:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:31 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:58 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:58 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:58 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:58 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:58 node-1 multipathd: uevent trigger error
<27>Sep  3 16:31:58 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:03 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:03 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:03 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:03 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:03 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:16 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:23 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:23 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:23 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:23 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:23 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:28 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:28 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:28 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:28 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:28 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:28 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:41 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:41 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:41 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:41 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:41 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:46 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:46 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:46 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:46 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:46 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:51 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:51 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:51 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:51 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:51 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:56 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:56 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:56 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:56 node-1 multipathd: uevent trigger error
<27>Sep  3 16:32:56 node-1 multipathd: uevent trigger error
<27>Sep  3 16:33:01 node-1 multipathd: uevent trigger error
<27>Sep  3 16:33:01 node-1 multipathd: uevent trigger error
<27>Sep  3 16:33:01 node-1 multipathd: uevent trigger error
<27>Sep  3 16:33:01 node-1 multipathd: uevent trigger error
<27>Sep  3 16:33:01 node-1 multipathd: uevent trigger error
<27>Sep  3 16:33:06 node-1 multipathd: uevent trigger error
<27>Sep  3 16:33:06 node-1 multipathd: uevent trigger error
<27>Sep  3 16:33:06 node-1 multipathd: uevent trigger error
<27>Sep  3 16:33:06 node-1 multipathd: uevent trigger error
<27>Sep  3 16:33:06 node-1 multipathd: uevent trigger error
<11>Sep  3 16:35:01 node-1 liberasurecode[6908]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:35:01 node-1 liberasurecode[6908]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:35:01 node-1 liberasurecode[6908]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  3 16:35:01 node-1 liberasurecode[6908]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
