Aug 19 18:38:58 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8387" x-info="http://www.rsyslog.com"] start
Aug 19 18:38:58 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Aug 19 18:38:58 node-1 rsyslogd: rsyslogd's groupid changed to 104
Aug 19 18:38:58 node-1 rsyslogd: rsyslogd's userid changed to 101
Aug 19 18:38:58 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Aug 19 18:38:58 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Aug 19 18:38:58 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Aug 19 18:38:58 node-1 kernel: [    0.000000] Linux version 3.13.0-93-generic (buildd@lgw01-13) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #140-Ubuntu SMP Mon Jul 18 21:21:05 UTC 2016 (Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39)
Aug 19 18:38:58 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-93-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=ae4ebd1e-f368-4f59-a651-9cdff3a4c790 nomdmonddf nomdmonisw
Aug 19 18:38:58 node-1 kernel: [    0.000000] KERNEL supported cpus:
Aug 19 18:38:58 node-1 kernel: [    0.000000]   Intel GenuineIntel
Aug 19 18:38:58 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Aug 19 18:38:58 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Aug 19 18:38:58 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Aug 19 18:38:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Aug 19 18:38:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Aug 19 18:38:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Aug 19 18:38:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Aug 19 18:38:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Aug 19 18:38:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Aug 19 18:38:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Aug 19 18:38:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Aug 19 18:38:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Aug 19 18:38:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Aug 19 18:38:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Aug 19 18:38:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Aug 19 18:38:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Aug 19 18:38:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Aug 19 18:38:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Aug 19 18:38:58 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Aug 19 18:38:58 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Aug 19 18:38:58 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Aug 19 18:38:58 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Aug 19 18:38:58 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Aug 19 18:38:58 node-1 kernel: [    0.000000] No AGP bridge found
Aug 19 18:38:58 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Aug 19 18:38:58 node-1 kernel: [    0.000000] MTRR default type: write-back
Aug 19 18:38:58 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Aug 19 18:38:58 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Aug 19 18:38:58 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Aug 19 18:38:58 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Aug 19 18:38:58 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Aug 19 18:38:58 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Aug 19 18:38:58 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Aug 19 18:38:58 node-1 kernel: [    0.000000]   2 disabled
Aug 19 18:38:58 node-1 kernel: [    0.000000]   3 disabled
Aug 19 18:38:58 node-1 kernel: [    0.000000]   4 disabled
Aug 19 18:38:58 node-1 kernel: [    0.000000]   5 disabled
Aug 19 18:38:58 node-1 kernel: [    0.000000]   6 disabled
Aug 19 18:38:58 node-1 kernel: [    0.000000]   7 disabled
Aug 19 18:38:58 node-1 kernel: [    0.000000]   8 disabled
Aug 19 18:38:58 node-1 kernel: [    0.000000]   9 disabled
Aug 19 18:38:58 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Aug 19 18:38:58 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Aug 19 18:38:58 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Aug 19 18:38:58 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Aug 19 18:38:58 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Aug 19 18:38:58 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Aug 19 18:38:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Aug 19 18:38:58 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Aug 19 18:38:58 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Aug 19 18:38:58 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Aug 19 18:38:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Aug 19 18:38:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Aug 19 18:38:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Aug 19 18:38:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Aug 19 18:38:58 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Aug 19 18:38:58 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Aug 19 18:38:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Aug 19 18:38:58 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Aug 19 18:38:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Aug 19 18:38:58 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Aug 19 18:38:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Aug 19 18:38:58 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Aug 19 18:38:58 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Aug 19 18:38:58 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Aug 19 18:38:58 node-1 kernel: [    0.000000] Zone ranges:
Aug 19 18:38:58 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] Movable zone start for each node
Aug 19 18:38:58 node-1 kernel: [    0.000000] Early memory node ranges
Aug 19 18:38:58 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Aug 19 18:38:58 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Aug 19 18:38:58 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Aug 19 18:38:58 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Aug 19 18:38:58 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Aug 19 18:38:58 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Aug 19 18:38:58 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Aug 19 18:38:58 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Aug 19 18:38:58 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Aug 19 18:38:58 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Aug 19 18:38:58 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Aug 19 18:38:58 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Aug 19 18:38:58 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Aug 19 18:38:58 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Aug 19 18:38:58 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Aug 19 18:38:58 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Aug 19 18:38:58 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Aug 19 18:38:58 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Aug 19 18:38:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Aug 19 18:38:58 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Aug 19 18:38:58 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Aug 19 18:38:58 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Aug 19 18:38:58 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Aug 19 18:38:58 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Aug 19 18:38:58 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Aug 19 18:38:58 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Aug 19 18:38:58 node-1 kernel: [    0.000000] Policy zone: Normal
Aug 19 18:38:58 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-93-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=ae4ebd1e-f368-4f59-a651-9cdff3a4c790 nomdmonddf nomdmonisw
Aug 19 18:38:58 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Aug 19 18:38:58 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Aug 19 18:38:58 node-1 kernel: [    0.000000] Checking aperture...
Aug 19 18:38:58 node-1 kernel: [    0.000000] No AGP bridge found
Aug 19 18:38:58 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Aug 19 18:38:58 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Aug 19 18:38:58 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Aug 19 18:38:58 node-1 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Aug 19 18:38:58 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Aug 19 18:38:58 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Aug 19 18:38:58 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Aug 19 18:38:58 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Aug 19 18:38:58 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Aug 19 18:38:58 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Aug 19 18:38:58 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Aug 19 18:38:58 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Aug 19 18:38:58 node-1 kernel: [    0.000000] console [tty0] enabled
Aug 19 18:38:58 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Aug 19 18:38:58 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Aug 19 18:38:58 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Aug 19 18:38:58 node-1 kernel: [    0.000000] hpet clockevent registered
Aug 19 18:38:58 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Aug 19 18:38:58 node-1 kernel: [    0.004000] tsc: Detected 3492.289 MHz processor
Aug 19 18:38:58 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.57 BogoMIPS (lpj=13969156)
Aug 19 18:38:58 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Aug 19 18:38:58 node-1 kernel: [    0.000047] Security Framework initialized
Aug 19 18:38:58 node-1 kernel: [    0.000067] AppArmor: AppArmor initialized
Aug 19 18:38:58 node-1 kernel: [    0.000068] Yama: becoming mindful.
Aug 19 18:38:58 node-1 kernel: [    0.001465] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Aug 19 18:38:58 node-1 kernel: [    0.006334] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Aug 19 18:38:58 node-1 kernel: [    0.008263] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Aug 19 18:38:58 node-1 kernel: [    0.008291] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Aug 19 18:38:58 node-1 kernel: [    0.008584] Initializing cgroup subsys memory
Aug 19 18:38:58 node-1 kernel: [    0.008593] Initializing cgroup subsys devices
Aug 19 18:38:58 node-1 kernel: [    0.008595] Initializing cgroup subsys freezer
Aug 19 18:38:58 node-1 kernel: [    0.008596] Initializing cgroup subsys blkio
Aug 19 18:38:58 node-1 kernel: [    0.008598] Initializing cgroup subsys perf_event
Aug 19 18:38:58 node-1 kernel: [    0.008600] Initializing cgroup subsys hugetlb
Aug 19 18:38:58 node-1 kernel: [    0.008619] CPU: Physical Processor ID: 0
Aug 19 18:38:58 node-1 kernel: [    0.008621] CPU: Processor Core ID: 0
Aug 19 18:38:58 node-1 kernel: [    0.008624] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Aug 19 18:38:58 node-1 kernel: [    0.008624] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Aug 19 18:38:58 node-1 kernel: [    0.009318] mce: CPU supports 22 MCE banks
Aug 19 18:38:58 node-1 kernel: [    0.009346] CPU0: Thermal monitoring enabled (TM1)
Aug 19 18:38:58 node-1 kernel: [    0.009367] process: using mwait in idle threads
Aug 19 18:38:58 node-1 kernel: [    0.009370] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Aug 19 18:38:58 node-1 kernel: [    0.009370] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Aug 19 18:38:58 node-1 kernel: [    0.009370] tlb_flushall_shift: 6
Aug 19 18:38:58 node-1 kernel: [    0.009459] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Aug 19 18:38:58 node-1 kernel: [    0.010185] ACPI: Core revision 20131115
Aug 19 18:38:58 node-1 kernel: [    0.022869] ACPI: All ACPI Tables successfully acquired
Aug 19 18:38:58 node-1 kernel: [    0.023029] ftrace: allocating 28617 entries in 112 pages
Aug 19 18:38:58 node-1 kernel: [    0.032018] dmar: Host address width 46
Aug 19 18:38:58 node-1 kernel: [    0.032021] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Aug 19 18:38:58 node-1 kernel: [    0.032027] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Aug 19 18:38:58 node-1 kernel: [    0.032028] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Aug 19 18:38:58 node-1 kernel: [    0.032032] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Aug 19 18:38:58 node-1 kernel: [    0.032034] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Aug 19 18:38:58 node-1 kernel: [    0.032035] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Aug 19 18:38:58 node-1 kernel: [    0.032036] dmar: ATSR flags: 0x0
Aug 19 18:38:58 node-1 kernel: [    0.032037] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Aug 19 18:38:58 node-1 kernel: [    0.032039] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Aug 19 18:38:58 node-1 kernel: [    0.032154] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Aug 19 18:38:58 node-1 kernel: [    0.032155] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Aug 19 18:38:58 node-1 kernel: [    0.032156] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Aug 19 18:38:58 node-1 kernel: [    0.032157] HPET id 0 under DRHD base 0xc7ffc000
Aug 19 18:38:58 node-1 kernel: [    0.032158] Your BIOS is broken and requested that x2apic be disabled.
Aug 19 18:38:58 node-1 kernel: [    0.032158] This will slightly decrease performance.
Aug 19 18:38:58 node-1 kernel: [    0.032158] Use 'intremap=no_x2apic_optout' to override BIOS request.
Aug 19 18:38:58 node-1 kernel: [    0.032590] Enabled IRQ remapping in xapic mode
Aug 19 18:38:58 node-1 kernel: [    0.032591] x2apic not enabled, IRQ remapping is in xapic mode
Aug 19 18:38:58 node-1 kernel: [    0.032595] Switched APIC routing to physical flat.
Aug 19 18:38:58 node-1 kernel: [    0.033212] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Aug 19 18:38:58 node-1 kernel: [    0.072866] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Aug 19 18:38:58 node-1 kernel: [    0.072871] TSC deadline timer enabled
Aug 19 18:38:58 node-1 kernel: [    0.072879] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Aug 19 18:38:58 node-1 kernel: [    0.072885] ... version:                3
Aug 19 18:38:58 node-1 kernel: [    0.072886] ... bit width:              48
Aug 19 18:38:58 node-1 kernel: [    0.072887] ... generic registers:      4
Aug 19 18:38:58 node-1 kernel: [    0.072888] ... value mask:             0000ffffffffffff
Aug 19 18:38:58 node-1 kernel: [    0.072889] ... max period:             0000ffffffffffff
Aug 19 18:38:58 node-1 kernel: [    0.072890] ... fixed-purpose events:   3
Aug 19 18:38:58 node-1 kernel: [    0.072891] ... event mask:             000000070000000f
Aug 19 18:38:58 node-1 kernel: [    0.074306] x86: Booting SMP configuration:
Aug 19 18:38:58 node-1 kernel: [    0.088415] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Aug 19 18:38:58 node-1 kernel: [    0.074308] .... node  #0, CPUs:        #1  #2  #3
Aug 19 18:38:58 node-1 kernel: [    0.116330] .... node  #1, CPUs:    #4  #5  #6  #7
Aug 19 18:38:58 node-1 kernel: [    0.270525] .... node  #0, CPUs:    #8  #9 #10 #11
Aug 19 18:38:58 node-1 kernel: [    0.326155] .... node  #1, CPUs:   #12 #13 #14 #15
Aug 19 18:38:58 node-1 kernel: [    0.383225] x86: Booted up 2 nodes, 16 CPUs
Aug 19 18:38:58 node-1 kernel: [    0.383228] smpboot: Total of 16 processors activated (111765.38 BogoMIPS)
Aug 19 18:38:58 node-1 kernel: [    0.407900] devtmpfs: initialized
Aug 19 18:38:58 node-1 kernel: [    0.411010] EVM: security.selinux
Aug 19 18:38:58 node-1 kernel: [    0.411011] EVM: security.SMACK64
Aug 19 18:38:58 node-1 kernel: [    0.411012] EVM: security.ima
Aug 19 18:38:58 node-1 kernel: [    0.411013] EVM: security.capability
Aug 19 18:38:58 node-1 kernel: [    0.411063] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Aug 19 18:38:58 node-1 kernel: [    0.411747] pinctrl core: initialized pinctrl subsystem
Aug 19 18:38:58 node-1 kernel: [    0.411813] regulator-dummy: no parameters
Aug 19 18:38:58 node-1 kernel: [    0.411845] RTC time: 18:38:22, date: 08/19/16
Aug 19 18:38:58 node-1 kernel: [    0.411879] NET: Registered protocol family 16
Aug 19 18:38:58 node-1 kernel: [    0.411965] cpuidle: using governor ladder
Aug 19 18:38:58 node-1 kernel: [    0.411966] cpuidle: using governor menu
Aug 19 18:38:58 node-1 kernel: [    0.412002] ACPI: bus type PCI registered
Aug 19 18:38:58 node-1 kernel: [    0.412004] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Aug 19 18:38:58 node-1 kernel: [    0.412050] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Aug 19 18:38:58 node-1 kernel: [    0.412052] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Aug 19 18:38:58 node-1 kernel: [    0.425790] PCI: Using configuration type 1 for base access
Aug 19 18:38:58 node-1 kernel: [    0.426797] bio: create slab <bio-0> at 0
Aug 19 18:38:58 node-1 kernel: [    0.427083] ACPI: Added _OSI(Module Device)
Aug 19 18:38:58 node-1 kernel: [    0.427085] ACPI: Added _OSI(Processor Device)
Aug 19 18:38:58 node-1 kernel: [    0.427086] ACPI: Added _OSI(3.0 _SCP Extensions)
Aug 19 18:38:58 node-1 kernel: [    0.427087] ACPI: Added _OSI(Processor Aggregator Device)
Aug 19 18:38:58 node-1 kernel: [    0.439779] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Aug 19 18:38:58 node-1 kernel: [    0.450254] ACPI: Interpreter enabled
Aug 19 18:38:58 node-1 kernel: [    0.450260] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Aug 19 18:38:58 node-1 kernel: [    0.450263] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Aug 19 18:38:58 node-1 kernel: [    0.450266] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Aug 19 18:38:58 node-1 kernel: [    0.450273] ACPI: (supports S0 S4 S5)
Aug 19 18:38:58 node-1 kernel: [    0.450275] ACPI: Using IOAPIC for interrupt routing
Aug 19 18:38:58 node-1 kernel: [    0.450317] HEST: Table parsing has been initialized.
Aug 19 18:38:58 node-1 kernel: [    0.450320] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Aug 19 18:38:58 node-1 kernel: [    0.450874] ACPI: No dock devices found.
Aug 19 18:38:58 node-1 kernel: [    0.462530] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Aug 19 18:38:58 node-1 kernel: [    0.462535] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 19 18:38:58 node-1 kernel: [    0.462538] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Aug 19 18:38:58 node-1 kernel: [    0.462566] PCI host bridge to bus 0000:ff
Aug 19 18:38:58 node-1 kernel: [    0.462569] pci_bus 0000:ff: root bus resource [bus ff]
Aug 19 18:38:58 node-1 kernel: [    0.462577] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.462615] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Aug 19 18:38:58 node-1 kernel: [    0.462646] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.462681] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.462711] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Aug 19 18:38:58 node-1 kernel: [    0.462740] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Aug 19 18:38:58 node-1 kernel: [    0.462771] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.462799] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.462829] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.462858] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.462885] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.462912] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.462940] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.462967] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.462994] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463021] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463050] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463078] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463105] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Aug 19 18:38:58 node-1 kernel: [    0.463134] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463160] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Aug 19 18:38:58 node-1 kernel: [    0.463186] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463213] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463243] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Aug 19 18:38:58 node-1 kernel: [    0.463279] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463311] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463341] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463372] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463404] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463435] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463466] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463498] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463529] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463561] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463598] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463630] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463665] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463696] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463724] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463756] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463790] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463831] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463867] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463901] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463931] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463960] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.463991] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464023] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464055] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464086] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464119] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464149] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464180] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464210] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464240] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464272] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464305] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464364] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Aug 19 18:38:58 node-1 kernel: [    0.464367] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 19 18:38:58 node-1 kernel: [    0.464370] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Aug 19 18:38:58 node-1 kernel: [    0.464388] PCI host bridge to bus 0000:7f
Aug 19 18:38:58 node-1 kernel: [    0.464390] pci_bus 0000:7f: root bus resource [bus 7f]
Aug 19 18:38:58 node-1 kernel: [    0.464395] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464423] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Aug 19 18:38:58 node-1 kernel: [    0.464449] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464477] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464499] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Aug 19 18:38:58 node-1 kernel: [    0.464525] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Aug 19 18:38:58 node-1 kernel: [    0.464552] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464583] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464608] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464632] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464657] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464682] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464708] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464732] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464756] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464781] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464803] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464826] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464848] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Aug 19 18:38:58 node-1 kernel: [    0.464872] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464894] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Aug 19 18:38:58 node-1 kernel: [    0.464918] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464941] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.464967] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Aug 19 18:38:58 node-1 kernel: [    0.465001] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465028] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465055] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465081] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465106] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465133] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465159] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465187] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465214] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465243] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465271] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465300] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465328] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465353] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465377] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465406] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465431] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465459] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465490] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465519] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465544] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465569] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465596] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465625] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465652] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465678] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465712] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465738] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465761] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465786] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465812] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465841] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.465868] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.467113] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Aug 19 18:38:58 node-1 kernel: [    0.467116] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 19 18:38:58 node-1 kernel: [    0.468244] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Aug 19 18:38:58 node-1 kernel: [    0.468757] PCI host bridge to bus 0000:00
Aug 19 18:38:58 node-1 kernel: [    0.468760] pci_bus 0000:00: root bus resource [bus 00-7e]
Aug 19 18:38:58 node-1 kernel: [    0.468761] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Aug 19 18:38:58 node-1 kernel: [    0.468763] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Aug 19 18:38:58 node-1 kernel: [    0.468764] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Aug 19 18:38:58 node-1 kernel: [    0.468765] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Aug 19 18:38:58 node-1 kernel: [    0.468767] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Aug 19 18:38:58 node-1 kernel: [    0.468768] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Aug 19 18:38:58 node-1 kernel: [    0.468774] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Aug 19 18:38:58 node-1 kernel: [    0.468856] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Aug 19 18:38:58 node-1 kernel: [    0.468887] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Aug 19 18:38:58 node-1 kernel: [    0.468929] pci 0000:00:01.0: System wakeup disabled by ACPI
Aug 19 18:38:58 node-1 kernel: [    0.468948] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Aug 19 18:38:58 node-1 kernel: [    0.468977] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Aug 19 18:38:58 node-1 kernel: [    0.469018] pci 0000:00:02.0: System wakeup disabled by ACPI
Aug 19 18:38:58 node-1 kernel: [    0.469037] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Aug 19 18:38:58 node-1 kernel: [    0.469067] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Aug 19 18:38:58 node-1 kernel: [    0.469107] pci 0000:00:03.0: System wakeup disabled by ACPI
Aug 19 18:38:58 node-1 kernel: [    0.469125] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.469196] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.469273] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.469349] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Aug 19 18:38:58 node-1 kernel: [    0.469354] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Aug 19 18:38:58 node-1 kernel: [    0.469439] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Aug 19 18:38:58 node-1 kernel: [    0.469586] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Aug 19 18:38:58 node-1 kernel: [    0.469604] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Aug 19 18:38:58 node-1 kernel: [    0.469682] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Aug 19 18:38:58 node-1 kernel: [    0.469737] pci 0000:00:1a.0: System wakeup disabled by ACPI
Aug 19 18:38:58 node-1 kernel: [    0.469759] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Aug 19 18:38:58 node-1 kernel: [    0.469814] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Aug 19 18:38:58 node-1 kernel: [    0.469857] pci 0000:00:1c.0: System wakeup disabled by ACPI
Aug 19 18:38:58 node-1 kernel: [    0.469885] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Aug 19 18:38:58 node-1 kernel: [    0.469940] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Aug 19 18:38:58 node-1 kernel: [    0.469983] pci 0000:00:1c.7: System wakeup disabled by ACPI
Aug 19 18:38:58 node-1 kernel: [    0.470007] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Aug 19 18:38:58 node-1 kernel: [    0.470024] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Aug 19 18:38:58 node-1 kernel: [    0.470102] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Aug 19 18:38:58 node-1 kernel: [    0.470152] pci 0000:00:1d.0: System wakeup disabled by ACPI
Aug 19 18:38:58 node-1 kernel: [    0.470178] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Aug 19 18:38:58 node-1 kernel: [    0.470426] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Aug 19 18:38:58 node-1 kernel: [    0.470432] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Aug 19 18:38:58 node-1 kernel: [    0.470438] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Aug 19 18:38:58 node-1 kernel: [    0.470443] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Aug 19 18:38:58 node-1 kernel: [    0.470451] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Aug 19 18:38:58 node-1 kernel: [    0.470481] pci 0000:01:00.0: supports D1 D2
Aug 19 18:38:58 node-1 kernel: [    0.480578] pci 0000:00:01.0: PCI bridge to [bus 01]
Aug 19 18:38:58 node-1 kernel: [    0.480584] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Aug 19 18:38:58 node-1 kernel: [    0.480589] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Aug 19 18:38:58 node-1 kernel: [    0.480853] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Aug 19 18:38:58 node-1 kernel: [    0.480913] pci 0000:02:00.0: PME# supported from D0 D3hot
Aug 19 18:38:58 node-1 kernel: [    0.488572] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Aug 19 18:38:58 node-1 kernel: [    0.488575] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Aug 19 18:38:58 node-1 kernel: [    0.488577] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Aug 19 18:38:58 node-1 kernel: [    0.488632] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Aug 19 18:38:58 node-1 kernel: [    0.488700] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Aug 19 18:38:58 node-1 kernel: [    0.488777] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Aug 19 18:38:58 node-1 kernel: [    0.488822] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Aug 19 18:38:58 node-1 kernel: [    0.488825] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Aug 19 18:38:58 node-1 kernel: [    0.488827] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Aug 19 18:38:58 node-1 kernel: [    0.488898] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Aug 19 18:38:58 node-1 kernel: [    0.489021] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Aug 19 18:38:58 node-1 kernel: [    0.489076] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Aug 19 18:38:58 node-1 kernel: [    0.489079] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Aug 19 18:38:58 node-1 kernel: [    0.489081] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Aug 19 18:38:58 node-1 kernel: [    0.489130] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Aug 19 18:38:58 node-1 kernel: [    0.489249] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Aug 19 18:38:58 node-1 kernel: [    0.489288] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Aug 19 18:38:58 node-1 kernel: [    0.489406] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Aug 19 18:38:58 node-1 kernel: [    0.489444] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Aug 19 18:38:58 node-1 kernel: [    0.489564] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Aug 19 18:38:58 node-1 kernel: [    0.489601] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Aug 19 18:38:58 node-1 kernel: [    0.489722] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Aug 19 18:38:58 node-1 kernel: [    0.489764] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Aug 19 18:38:58 node-1 kernel: [    0.489766] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Aug 19 18:38:58 node-1 kernel: [    0.489768] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Aug 19 18:38:58 node-1 kernel: [    0.489826] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Aug 19 18:38:58 node-1 kernel: [    0.489889] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Aug 19 18:38:58 node-1 kernel: [    0.489967] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Aug 19 18:38:58 node-1 kernel: [    0.490007] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Aug 19 18:38:58 node-1 kernel: [    0.490086] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Aug 19 18:38:58 node-1 kernel: [    0.490193] pci 0000:05:00.0: PCI bridge to [bus 06]
Aug 19 18:38:58 node-1 kernel: [    0.490196] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Aug 19 18:38:58 node-1 kernel: [    0.490198] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Aug 19 18:38:58 node-1 kernel: [    0.490254] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Aug 19 18:38:58 node-1 kernel: [    0.490308] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Aug 19 18:38:58 node-1 kernel: [    0.490356] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Aug 19 18:38:58 node-1 kernel: [    0.490567] pci 0000:05:01.0: PCI bridge to [bus 07]
Aug 19 18:38:58 node-1 kernel: [    0.490571] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Aug 19 18:38:58 node-1 kernel: [    0.490634] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Aug 19 18:38:58 node-1 kernel: [    0.490687] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Aug 19 18:38:58 node-1 kernel: [    0.490735] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Aug 19 18:38:58 node-1 kernel: [    0.490969] pci 0000:05:02.0: PCI bridge to [bus 08]
Aug 19 18:38:58 node-1 kernel: [    0.490973] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Aug 19 18:38:58 node-1 kernel: [    0.491031] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Aug 19 18:38:58 node-1 kernel: [    0.491095] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Aug 19 18:38:58 node-1 kernel: [    0.491147] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Aug 19 18:38:58 node-1 kernel: [    0.491372] pci 0000:05:03.0: PCI bridge to [bus 09]
Aug 19 18:38:58 node-1 kernel: [    0.491375] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Aug 19 18:38:58 node-1 kernel: [    0.491549] pci 0000:00:03.0: PCI bridge to [bus 0a]
Aug 19 18:38:58 node-1 kernel: [    0.491587] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Aug 19 18:38:58 node-1 kernel: [    0.491663] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Aug 19 18:38:58 node-1 kernel: [    0.491682] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Aug 19 18:38:58 node-1 kernel: [    0.491695] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Aug 19 18:38:58 node-1 kernel: [    0.491708] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Aug 19 18:38:58 node-1 kernel: [    0.491758] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Aug 19 18:38:58 node-1 kernel: [    0.496587] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Aug 19 18:38:58 node-1 kernel: [    0.496596] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Aug 19 18:38:58 node-1 kernel: [    0.496648] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Aug 19 18:38:58 node-1 kernel: [    0.497342] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Aug 19 18:38:58 node-1 kernel: [    0.497345] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 19 18:38:58 node-1 kernel: [    0.497464] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Aug 19 18:38:58 node-1 kernel: [    0.497572] PCI host bridge to bus 0000:80
Aug 19 18:38:58 node-1 kernel: [    0.497574] pci_bus 0000:80: root bus resource [bus 80-fe]
Aug 19 18:38:58 node-1 kernel: [    0.497576] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Aug 19 18:38:58 node-1 kernel: [    0.497577] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Aug 19 18:38:58 node-1 kernel: [    0.497585] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.497649] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.497716] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Aug 19 18:38:58 node-1 kernel: [    0.497777] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Aug 19 18:38:58 node-1 kernel: [    0.497782] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Aug 19 18:38:58 node-1 kernel: [    0.497853] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Aug 19 18:38:58 node-1 kernel: [    0.498149] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Aug 19 18:38:58 node-1 kernel: [    0.498181] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Aug 19 18:38:58 node-1 kernel: [    0.498211] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Aug 19 18:38:58 node-1 kernel: [    0.498240] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Aug 19 18:38:58 node-1 kernel: [    0.498269] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Aug 19 18:38:58 node-1 kernel: [    0.498299] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Aug 19 18:38:58 node-1 kernel: [    0.498329] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Aug 19 18:38:58 node-1 kernel: [    0.498359] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Aug 19 18:38:58 node-1 kernel: [    0.498443] ACPI: Enabled 3 GPEs in block 00 to 3F
Aug 19 18:38:58 node-1 kernel: [    0.498447] ACPI: \_SB_.UNC1: notify handler is installed
Aug 19 18:38:58 node-1 kernel: [    0.498449] ACPI: \_SB_.UNC0: notify handler is installed
Aug 19 18:38:58 node-1 kernel: [    0.498464] ACPI: \_SB_.PCI0: notify handler is installed
Aug 19 18:38:58 node-1 kernel: [    0.498516] ACPI: \_SB_.PCI1: notify handler is installed
Aug 19 18:38:58 node-1 kernel: [    0.498596] Found 4 acpi root devices
Aug 19 18:38:58 node-1 kernel: [    0.498701] vgaarb: setting as boot device: PCI:0000:0c:00.0
Aug 19 18:38:58 node-1 kernel: [    0.498703] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Aug 19 18:38:58 node-1 kernel: [    0.498705] vgaarb: loaded
Aug 19 18:38:58 node-1 kernel: [    0.498706] vgaarb: bridge control possible 0000:0c:00.0
Aug 19 18:38:58 node-1 kernel: [    0.498823] SCSI subsystem initialized
Aug 19 18:38:58 node-1 kernel: [    0.498898] libata version 3.00 loaded.
Aug 19 18:38:58 node-1 kernel: [    0.498913] ACPI: bus type USB registered
Aug 19 18:38:58 node-1 kernel: [    0.498923] usbcore: registered new interface driver usbfs
Aug 19 18:38:58 node-1 kernel: [    0.498928] usbcore: registered new interface driver hub
Aug 19 18:38:58 node-1 kernel: [    0.498950] usbcore: registered new device driver usb
Aug 19 18:38:58 node-1 kernel: [    0.499131] PCI: Using ACPI for IRQ routing
Aug 19 18:38:58 node-1 kernel: [    0.502725] PCI: pci_cache_line_size set to 64 bytes
Aug 19 18:38:58 node-1 kernel: [    0.502937] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Aug 19 18:38:58 node-1 kernel: [    0.502938] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Aug 19 18:38:58 node-1 kernel: [    0.502939] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Aug 19 18:38:58 node-1 kernel: [    0.503002] NetLabel: Initializing
Aug 19 18:38:58 node-1 kernel: [    0.503003] NetLabel:  domain hash size = 128
Aug 19 18:38:58 node-1 kernel: [    0.503004] NetLabel:  protocols = UNLABELED CIPSOv4
Aug 19 18:38:58 node-1 kernel: [    0.503014] NetLabel:  unlabeled traffic allowed by default
Aug 19 18:38:58 node-1 kernel: [    0.503069] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Aug 19 18:38:58 node-1 kernel: [    0.503073] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Aug 19 18:38:58 node-1 kernel: [    0.505130] Switched to clocksource hpet
Aug 19 18:38:58 node-1 kernel: [    0.509052] AppArmor: AppArmor Filesystem Enabled
Aug 19 18:38:58 node-1 kernel: [    0.509066] pnp: PnP ACPI init
Aug 19 18:38:58 node-1 kernel: [    0.509073] ACPI: bus type PNP registered
Aug 19 18:38:58 node-1 kernel: [    0.509194] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Aug 19 18:38:58 node-1 kernel: [    0.509202] pnp 00:01: [dma 4]
Aug 19 18:38:58 node-1 kernel: [    0.509214] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Aug 19 18:38:58 node-1 kernel: [    0.509240] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Aug 19 18:38:58 node-1 kernel: [    0.509259] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Aug 19 18:38:58 node-1 kernel: [    0.509277] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Aug 19 18:38:58 node-1 kernel: [    0.509310] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Aug 19 18:38:58 node-1 kernel: [    0.509363] system 00:06: [io  0x0500-0x057f] has been reserved
Aug 19 18:38:58 node-1 kernel: [    0.509365] system 00:06: [io  0x0400-0x047f] could not be reserved
Aug 19 18:38:58 node-1 kernel: [    0.509367] system 00:06: [io  0x0580-0x059f] has been reserved
Aug 19 18:38:58 node-1 kernel: [    0.509368] system 00:06: [io  0x0600-0x061f] has been reserved
Aug 19 18:38:58 node-1 kernel: [    0.509370] system 00:06: [io  0x0880-0x0883] has been reserved
Aug 19 18:38:58 node-1 kernel: [    0.509375] system 00:06: [io  0x0800-0x081f] has been reserved
Aug 19 18:38:58 node-1 kernel: [    0.509377] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Aug 19 18:38:58 node-1 kernel: [    0.509379] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Aug 19 18:38:58 node-1 kernel: [    0.509380] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Aug 19 18:38:58 node-1 kernel: [    0.509382] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Aug 19 18:38:58 node-1 kernel: [    0.509383] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Aug 19 18:38:58 node-1 kernel: [    0.509385] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Aug 19 18:38:58 node-1 kernel: [    0.509386] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Aug 19 18:38:58 node-1 kernel: [    0.509388] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Aug 19 18:38:58 node-1 kernel: [    0.509471] pnp 00:07: [dma 0 disabled]
Aug 19 18:38:58 node-1 kernel: [    0.509500] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Aug 19 18:38:58 node-1 kernel: [    0.509574] pnp 00:08: [dma 0 disabled]
Aug 19 18:38:58 node-1 kernel: [    0.509607] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Aug 19 18:38:58 node-1 kernel: [    0.509659] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Aug 19 18:38:58 node-1 kernel: [    0.510010] pnp: PnP ACPI: found 10 devices
Aug 19 18:38:58 node-1 kernel: [    0.510011] ACPI: bus type PNP unregistered
Aug 19 18:38:58 node-1 kernel: [    0.516283] pci 0000:00:01.0: PCI bridge to [bus 01]
Aug 19 18:38:58 node-1 kernel: [    0.516286] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Aug 19 18:38:58 node-1 kernel: [    0.516288] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Aug 19 18:38:58 node-1 kernel: [    0.516293] pci 0000:05:00.0: PCI bridge to [bus 06]
Aug 19 18:38:58 node-1 kernel: [    0.516294] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Aug 19 18:38:58 node-1 kernel: [    0.516309] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Aug 19 18:38:58 node-1 kernel: [    0.516338] pci 0000:05:01.0: PCI bridge to [bus 07]
Aug 19 18:38:58 node-1 kernel: [    0.516352] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Aug 19 18:38:58 node-1 kernel: [    0.516381] pci 0000:05:02.0: PCI bridge to [bus 08]
Aug 19 18:38:58 node-1 kernel: [    0.516396] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Aug 19 18:38:58 node-1 kernel: [    0.516425] pci 0000:05:03.0: PCI bridge to [bus 09]
Aug 19 18:38:58 node-1 kernel: [    0.516439] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Aug 19 18:38:58 node-1 kernel: [    0.516468] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Aug 19 18:38:58 node-1 kernel: [    0.516470] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Aug 19 18:38:58 node-1 kernel: [    0.516484] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Aug 19 18:38:58 node-1 kernel: [    0.516513] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Aug 19 18:38:58 node-1 kernel: [    0.516515] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Aug 19 18:38:58 node-1 kernel: [    0.516529] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Aug 19 18:38:58 node-1 kernel: [    0.516561] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Aug 19 18:38:58 node-1 kernel: [    0.516563] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Aug 19 18:38:58 node-1 kernel: [    0.516565] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Aug 19 18:38:58 node-1 kernel: [    0.516569] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Aug 19 18:38:58 node-1 kernel: [    0.516571] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Aug 19 18:38:58 node-1 kernel: [    0.516574] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Aug 19 18:38:58 node-1 kernel: [    0.516577] pci 0000:00:03.0: PCI bridge to [bus 0a]
Aug 19 18:38:58 node-1 kernel: [    0.516582] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Aug 19 18:38:58 node-1 kernel: [    0.516590] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Aug 19 18:38:58 node-1 kernel: [    0.516593] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Aug 19 18:38:58 node-1 kernel: [    0.516600] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Aug 19 18:38:58 node-1 kernel: [    0.516601] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Aug 19 18:38:58 node-1 kernel: [    0.516601] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Aug 19 18:38:58 node-1 kernel: [    0.516602] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Aug 19 18:38:58 node-1 kernel: [    0.516603] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Aug 19 18:38:58 node-1 kernel: [    0.516604] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Aug 19 18:38:58 node-1 kernel: [    0.516605] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Aug 19 18:38:58 node-1 kernel: [    0.516606] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Aug 19 18:38:58 node-1 kernel: [    0.516607] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Aug 19 18:38:58 node-1 kernel: [    0.516608] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Aug 19 18:38:58 node-1 kernel: [    0.516608] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Aug 19 18:38:58 node-1 kernel: [    0.516609] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Aug 19 18:38:58 node-1 kernel: [    0.516610] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Aug 19 18:38:58 node-1 kernel: [    0.516611] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Aug 19 18:38:58 node-1 kernel: [    0.516612] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Aug 19 18:38:58 node-1 kernel: [    0.516613] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Aug 19 18:38:58 node-1 kernel: [    0.516614] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Aug 19 18:38:58 node-1 kernel: [    0.516614] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Aug 19 18:38:58 node-1 kernel: [    0.516615] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Aug 19 18:38:58 node-1 kernel: [    0.516617] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Aug 19 18:38:58 node-1 kernel: [    0.516617] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Aug 19 18:38:58 node-1 kernel: [    0.516618] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Aug 19 18:38:58 node-1 kernel: [    0.516620] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Aug 19 18:38:58 node-1 kernel: [    0.516621] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Aug 19 18:38:58 node-1 kernel: [    0.516657] NET: Registered protocol family 2
Aug 19 18:38:58 node-1 kernel: [    0.516912] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Aug 19 18:38:58 node-1 kernel: [    0.517248] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Aug 19 18:38:58 node-1 kernel: [    0.517394] TCP: Hash tables configured (established 262144 bind 65536)
Aug 19 18:38:58 node-1 kernel: [    0.517430] TCP: reno registered
Aug 19 18:38:58 node-1 kernel: [    0.517460] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Aug 19 18:38:58 node-1 kernel: [    0.517554] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Aug 19 18:38:58 node-1 kernel: [    0.517700] NET: Registered protocol family 1
Aug 19 18:38:58 node-1 kernel: [    0.557237] pci 0000:0c:00.0: Video device with shadowed ROM
Aug 19 18:38:58 node-1 kernel: [    0.557252] PCI: CLS 64 bytes, default 64
Aug 19 18:38:58 node-1 kernel: [    0.557328] Trying to unpack rootfs image as initramfs...
Aug 19 18:38:58 node-1 kernel: [    0.777503] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Aug 19 18:38:58 node-1 kernel: [    0.777550] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Aug 19 18:38:58 node-1 kernel: [    0.777552] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Aug 19 18:38:58 node-1 kernel: [    0.777980] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Aug 19 18:38:58 node-1 kernel: [    0.777986] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Aug 19 18:38:58 node-1 kernel: [    0.777991] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Aug 19 18:38:58 node-1 kernel: [    0.777996] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Aug 19 18:38:58 node-1 kernel: [    0.778006] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Aug 19 18:38:58 node-1 kernel: [    0.778017] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Aug 19 18:38:58 node-1 kernel: [    0.778026] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Aug 19 18:38:58 node-1 kernel: [    0.778034] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Aug 19 18:38:58 node-1 kernel: [    0.778042] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Aug 19 18:38:58 node-1 kernel: [    0.778052] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Aug 19 18:38:58 node-1 kernel: [    0.778058] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Aug 19 18:38:58 node-1 kernel: [    0.778064] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Aug 19 18:38:58 node-1 kernel: [    0.778070] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Aug 19 18:38:58 node-1 kernel: [    0.778078] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Aug 19 18:38:58 node-1 kernel: [    0.778085] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Aug 19 18:38:58 node-1 kernel: [    0.778093] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Aug 19 18:38:58 node-1 kernel: [    0.778134] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Aug 19 18:38:58 node-1 kernel: [    0.778138] Scanning for low memory corruption every 60 seconds
Aug 19 18:38:58 node-1 kernel: [    0.778443] Initialise system trusted keyring
Aug 19 18:38:58 node-1 kernel: [    0.778487] audit: initializing netlink socket (disabled)
Aug 19 18:38:58 node-1 kernel: [    0.778496] type=2000 audit(1471631902.732:1): initialized
Aug 19 18:38:58 node-1 kernel: [    0.796309] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Aug 19 18:38:58 node-1 kernel: [    0.797787] zbud: loaded
Aug 19 18:38:58 node-1 kernel: [    0.797900] VFS: Disk quotas dquot_6.5.2
Aug 19 18:38:58 node-1 kernel: [    0.797944] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Aug 19 18:38:58 node-1 kernel: [    0.798314] fuse init (API version 7.22)
Aug 19 18:38:58 node-1 kernel: [    0.798369] msgmni has been set to 32768
Aug 19 18:38:58 node-1 kernel: [    0.798412] Key type big_key registered
Aug 19 18:38:58 node-1 kernel: [    0.798908] Key type asymmetric registered
Aug 19 18:38:58 node-1 kernel: [    0.798912] Asymmetric key parser 'x509' registered
Aug 19 18:38:58 node-1 kernel: [    0.798948] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Aug 19 18:38:58 node-1 kernel: [    0.799005] io scheduler noop registered
Aug 19 18:38:58 node-1 kernel: [    0.799006] io scheduler deadline registered (default)
Aug 19 18:38:58 node-1 kernel: [    0.799023] io scheduler cfq registered
Aug 19 18:38:58 node-1 kernel: [    0.799344] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    0.799435] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    0.799522] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    0.799609] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    0.799703] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    0.799770] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    0.800031] aer 0000:00:01.0:pcie02: service driver aer loaded
Aug 19 18:38:58 node-1 kernel: [    0.800049] aer 0000:00:02.0:pcie02: service driver aer loaded
Aug 19 18:38:58 node-1 kernel: [    0.800062] aer 0000:00:03.0:pcie02: service driver aer loaded
Aug 19 18:38:58 node-1 kernel: [    0.800071] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800073] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800075] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Aug 19 18:38:58 node-1 kernel: [    0.800079] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800080] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800082] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800083] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800084] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800086] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800087] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800089] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800090] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800091] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800093] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800094] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800096] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Aug 19 18:38:58 node-1 kernel: [    0.800100] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800102] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Aug 19 18:38:58 node-1 kernel: [    0.800110] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800113] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Aug 19 18:38:58 node-1 kernel: [    0.800122] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800124] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Aug 19 18:38:58 node-1 kernel: [    0.800127] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Aug 19 18:38:58 node-1 kernel: [    0.800139] ioapic: probe of 0000:00:05.4 failed with error -22
Aug 19 18:38:58 node-1 kernel: [    0.800229] ioapic: probe of 0000:80:05.4 failed with error -22
Aug 19 18:38:58 node-1 kernel: [    0.800233] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Aug 19 18:38:58 node-1 kernel: [    0.800242] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Aug 19 18:38:58 node-1 kernel: [    0.800279] vesafb: mode is 640x480x32, linelength=2560, pages=0
Aug 19 18:38:58 node-1 kernel: [    0.800280] vesafb: scrolling: redraw
Aug 19 18:38:58 node-1 kernel: [    0.800282] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Aug 19 18:38:58 node-1 kernel: [    0.821106] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Aug 19 18:38:58 node-1 kernel: [    0.829640] Console: switching to colour frame buffer device 80x30
Aug 19 18:38:58 node-1 kernel: [    0.838373] fb0: VESA VGA frame buffer device
Aug 19 18:38:58 node-1 kernel: [    0.838572] intel_idle: MWAIT substates: 0x2120
Aug 19 18:38:58 node-1 kernel: [    0.838573] intel_idle: v0.4 model 0x3F
Aug 19 18:38:58 node-1 kernel: [    0.838574] intel_idle: lapic_timer_reliable_states 0xffffffff
Aug 19 18:38:58 node-1 kernel: [    0.838796] ipmi message handler version 39.2
Aug 19 18:38:58 node-1 kernel: [    0.839057] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Aug 19 18:38:58 node-1 kernel: [    0.839491] ACPI: AC Adapter [P111] (on-line)
Aug 19 18:38:58 node-1 kernel: [    0.844752] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Aug 19 18:38:58 node-1 kernel: [    0.855817] ACPI: Power Button [PWRB]
Aug 19 18:38:58 node-1 kernel: [    0.861610] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Aug 19 18:38:58 node-1 kernel: [    0.873312] ACPI: Power Button [PWRF]
Aug 19 18:38:58 node-1 kernel: [    0.898755] ERST: Error Record Serialization Table (ERST) support is initialized.
Aug 19 18:38:58 node-1 kernel: [    0.910480] pstore: Registered erst as persistent store backend
Aug 19 18:38:58 node-1 kernel: [    0.916727] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Aug 19 18:38:58 node-1 kernel: [    0.928865] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Aug 19 18:38:58 node-1 kernel: [    0.955733] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Aug 19 18:38:58 node-1 kernel: [    0.989050] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Aug 19 18:38:58 node-1 kernel: [    1.003128] Linux agpgart interface v0.103
Aug 19 18:38:58 node-1 kernel: [    1.010781] brd: module loaded
Aug 19 18:38:58 node-1 kernel: [    1.017822] loop: module loaded
Aug 19 18:38:58 node-1 kernel: [    1.024565] libphy: Fixed MDIO Bus: probed
Aug 19 18:38:58 node-1 kernel: [    1.031034] tun: Universal TUN/TAP device driver, 1.6
Aug 19 18:38:58 node-1 kernel: [    1.037548] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Aug 19 18:38:58 node-1 kernel: [    1.044156] PPP generic driver version 2.4.2
Aug 19 18:38:58 node-1 kernel: [    1.050609] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Aug 19 18:38:58 node-1 kernel: [    1.057065] ehci-pci: EHCI PCI platform driver
Aug 19 18:38:58 node-1 kernel: [    1.063720] ehci-pci 0000:00:1a.0: EHCI Host Controller
Aug 19 18:38:58 node-1 kernel: [    1.070191] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Aug 19 18:38:58 node-1 kernel: [    1.082727] ehci-pci 0000:00:1a.0: debug port 2
Aug 19 18:38:58 node-1 kernel: [    1.092945] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Aug 19 18:38:58 node-1 kernel: [    1.092963] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Aug 19 18:38:58 node-1 kernel: [    1.108623] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Aug 19 18:38:58 node-1 kernel: [    1.114686] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Aug 19 18:38:58 node-1 kernel: [    1.120856] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Aug 19 18:38:58 node-1 kernel: [    1.132746] usb usb1: Product: EHCI Host Controller
Aug 19 18:38:58 node-1 kernel: [    1.138752] usb usb1: Manufacturer: Linux 3.13.0-93-generic ehci_hcd
Aug 19 18:38:58 node-1 kernel: [    1.144784] usb usb1: SerialNumber: 0000:00:1a.0
Aug 19 18:38:58 node-1 kernel: [    1.150721] hub 1-0:1.0: USB hub found
Aug 19 18:38:58 node-1 kernel: [    1.156477] hub 1-0:1.0: 2 ports detected
Aug 19 18:38:58 node-1 kernel: [    1.162260] ehci-pci 0000:00:1d.0: EHCI Host Controller
Aug 19 18:38:58 node-1 kernel: [    1.167836] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Aug 19 18:38:58 node-1 kernel: [    1.178705] ehci-pci 0000:00:1d.0: debug port 2
Aug 19 18:38:58 node-1 kernel: [    1.188015] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Aug 19 18:38:58 node-1 kernel: [    1.188018] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Aug 19 18:38:58 node-1 kernel: [    1.204543] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Aug 19 18:38:58 node-1 kernel: [    1.209841] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Aug 19 18:38:58 node-1 kernel: [    1.215139] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Aug 19 18:38:58 node-1 kernel: [    1.225708] usb usb2: Product: EHCI Host Controller
Aug 19 18:38:58 node-1 kernel: [    1.231174] usb usb2: Manufacturer: Linux 3.13.0-93-generic ehci_hcd
Aug 19 18:38:58 node-1 kernel: [    1.236716] usb usb2: SerialNumber: 0000:00:1d.0
Aug 19 18:38:58 node-1 kernel: [    1.242229] hub 2-0:1.0: USB hub found
Aug 19 18:38:58 node-1 kernel: [    1.247625] hub 2-0:1.0: 2 ports detected
Aug 19 18:38:58 node-1 kernel: [    1.252956] ehci-platform: EHCI generic platform driver
Aug 19 18:38:58 node-1 kernel: [    1.258174] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Aug 19 18:38:58 node-1 kernel: [    1.263479] ohci-pci: OHCI PCI platform driver
Aug 19 18:38:58 node-1 kernel: [    1.268771] ohci-platform: OHCI generic platform driver
Aug 19 18:38:58 node-1 kernel: [    1.273976] uhci_hcd: USB Universal Host Controller Interface driver
Aug 19 18:38:58 node-1 kernel: [    1.279306] i8042: PNP: No PS/2 controller found. Probing ports directly.
Aug 19 18:38:58 node-1 kernel: [    1.472324] usb 1-1: new high-speed USB device number 2 using ehci-pci
Aug 19 18:38:58 node-1 kernel: [    1.636500] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Aug 19 18:38:58 node-1 kernel: [    1.642083] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 19 18:38:58 node-1 kernel: [    1.647888] hub 1-1:1.0: USB hub found
Aug 19 18:38:58 node-1 kernel: [    1.653362] hub 1-1:1.0: 6 ports detected
Aug 19 18:38:58 node-1 kernel: [    1.768063] usb 2-1: new high-speed USB device number 2 using ehci-pci
Aug 19 18:38:58 node-1 kernel: [    1.776132] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Aug 19 18:38:58 node-1 kernel: [    2.036160] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Aug 19 18:38:58 node-1 kernel: [    2.041698] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 19 18:38:58 node-1 kernel: [    2.047553] hub 2-1:1.0: USB hub found
Aug 19 18:38:58 node-1 kernel: [    2.053272] hub 2-1:1.0: 8 ports detected
Aug 19 18:38:58 node-1 kernel: [    2.321183] i8042: No controller found
Aug 19 18:38:58 node-1 kernel: [    2.326598] mousedev: PS/2 mouse device common for all mice
Aug 19 18:38:58 node-1 kernel: [    2.331700] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Aug 19 18:38:58 node-1 kernel: [    2.337669] rtc_cmos 00:02: RTC can wake from S4
Aug 19 18:38:58 node-1 kernel: [    2.343399] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Aug 19 18:38:58 node-1 kernel: [    2.349008] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Aug 19 18:38:58 node-1 kernel: [    2.360074] device-mapper: uevent: version 1.0.3
Aug 19 18:38:58 node-1 kernel: [    2.365682] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Aug 19 18:38:58 node-1 kernel: [    2.376872] ledtrig-cpu: registered to indicate activity on CPUs
Aug 19 18:38:58 node-1 kernel: [    2.382795] TCP: cubic registered
Aug 19 18:38:58 node-1 kernel: [    2.388663] NET: Registered protocol family 10
Aug 19 18:38:58 node-1 kernel: [    2.394632] NET: Registered protocol family 17
Aug 19 18:38:58 node-1 kernel: [    2.400298] Key type dns_resolver registered
Aug 19 18:38:58 node-1 kernel: [    2.406254] Loading compiled-in X.509 certificates
Aug 19 18:38:58 node-1 kernel: [    2.412423] Loaded X.509 cert 'Magrathea: Glacier signing key: d5fcc7f0ec194773d05665948935931e3b1336a9'
Aug 19 18:38:58 node-1 kernel: [    2.423791] registered taskstats version 1
Aug 19 18:38:58 node-1 kernel: [    2.431750] Key type trusted registered
Aug 19 18:38:58 node-1 kernel: [    2.439289] Key type encrypted registered
Aug 19 18:38:58 node-1 kernel: [    2.444754] AppArmor: AppArmor sha1 policy hashing enabled
Aug 19 18:38:58 node-1 kernel: [    2.450240] IMA: No TPM chip found, activating TPM-bypass!
Aug 19 18:38:58 node-1 kernel: [    2.456394] regulator-dummy: disabling
Aug 19 18:38:58 node-1 kernel: [    2.461971]   Magic number: 12:929:645
Aug 19 18:38:58 node-1 kernel: [    2.467684] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Aug 19 18:38:58 node-1 kernel: [    2.467781] rtc_cmos 00:02: setting system clock to 2016-08-19 18:38:24 UTC (1471631904)
Aug 19 18:38:58 node-1 kernel: [    2.484267] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 19 18:38:58 node-1 kernel: [    2.495849] usb 2-1.4: Product: Cisco USB Composite Device-0
Aug 19 18:38:58 node-1 kernel: [    2.501805] usb 2-1.4: Manufacturer: Avocent
Aug 19 18:38:58 node-1 kernel: [    2.507629] usb 2-1.4: SerialNumber: 20111102-00000001
Aug 19 18:38:58 node-1 kernel: [    2.508026] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Aug 19 18:38:58 node-1 kernel: [    2.508026] EDD information not available.
Aug 19 18:38:58 node-1 kernel: [    2.508061] PM: Hibernation image not present or could not be loaded.
Aug 19 18:38:58 node-1 kernel: [    2.525923] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Aug 19 18:38:58 node-1 kernel: [    2.537542] Write protecting the kernel read-only data: 12288k
Aug 19 18:38:58 node-1 kernel: [    2.543944] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Aug 19 18:38:58 node-1 kernel: [    2.556653] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Aug 19 18:38:58 node-1 kernel: [    2.589079] device-mapper: multipath: version 1.6.0 loaded
Aug 19 18:38:58 node-1 kernel: [    2.597135] systemd-udevd[218]: starting version 204
Aug 19 18:38:58 node-1 kernel: [    2.621132] md: linear personality registered for level -1
Aug 19 18:38:58 node-1 kernel: [    2.635981] md: multipath personality registered for level -4
Aug 19 18:38:58 node-1 kernel: [    2.643990] md: raid0 personality registered for level 0
Aug 19 18:38:58 node-1 kernel: [    2.652954] md: raid1 personality registered for level 1
Aug 19 18:38:58 node-1 kernel: [    2.659455] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Aug 19 18:38:58 node-1 kernel: [    2.665949] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Aug 19 18:38:58 node-1 kernel: [    2.672437] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Aug 19 18:38:58 node-1 kernel: [    2.673073] megasas: FW now in Ready state
Aug 19 18:38:58 node-1 kernel: [    2.673171] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.673209] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.673263] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.673312] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.673348] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.673392] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.673428] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.673474] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.673509] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.673552] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.673584] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.673615] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.673657] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.673696] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.673730] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.673769] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.673946] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Aug 19 18:38:58 node-1 kernel: [    2.698335] hidraw: raw HID events driver (C) Jiri Kosina
Aug 19 18:38:58 node-1 kernel: [    2.707786] usbcore: registered new interface driver usbhid
Aug 19 18:38:58 node-1 kernel: [    2.708296] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Aug 19 18:38:58 node-1 kernel: [    2.708298] 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
Aug 19 18:38:58 node-1 kernel: [    2.708299] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Aug 19 18:38:58 node-1 kernel: [    2.708734] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.708842] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.708953] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.709097] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.709308] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.728875] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Aug 19 18:38:58 node-1 kernel: [    2.728889] 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
Aug 19 18:38:58 node-1 kernel: [    2.728890] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Aug 19 18:38:58 node-1 kernel: [    2.729150] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.729279] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.729367] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.729495] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.729649] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.744610] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Aug 19 18:38:58 node-1 kernel: [    2.744611] 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
Aug 19 18:38:58 node-1 kernel: [    2.744612] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Aug 19 18:38:58 node-1 kernel: [    2.744993] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.745123] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.745248] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.745361] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.745700] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.759323] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Aug 19 18:38:58 node-1 kernel: [    2.759324] 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
Aug 19 18:38:58 node-1 kernel: [    2.759334] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Aug 19 18:38:58 node-1 kernel: [    2.759639] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.759685] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.759831] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.759979] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.760342] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Aug 19 18:38:58 node-1 kernel: [    2.763315] raid6: sse2x1   11143 MB/s
Aug 19 18:38:58 node-1 kernel: [    2.831255] raid6: sse2x2   14462 MB/s
Aug 19 18:38:58 node-1 kernel: [    2.899173] raid6: sse2x4   13738 MB/s
Aug 19 18:38:58 node-1 kernel: [    2.922166] usbhid: USB HID core driver
Aug 19 18:38:58 node-1 kernel: [    2.967062] raid6: avx2x1   17755 MB/s
Aug 19 18:38:58 node-1 kernel: [    3.038995] raid6: avx2x2   18859 MB/s
Aug 19 18:38:58 node-1 kernel: [    3.110928] raid6: avx2x4   21386 MB/s
Aug 19 18:38:58 node-1 kernel: [    3.116944] raid6: using algorithm avx2x4 (21386 MB/s)
Aug 19 18:38:58 node-1 kernel: [    3.122863] raid6: using avx2x2 recovery algorithm
Aug 19 18:38:58 node-1 kernel: [    3.128627] Switched to clocksource tsc
Aug 19 18:38:58 node-1 kernel: [    3.128634] megasas:IOC Init cmd success
Aug 19 18:38:58 node-1 kernel: [    3.139920] 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
Aug 19 18:38:58 node-1 kernel: [    3.150913] megasas: INIT adapter done
Aug 19 18:38:58 node-1 kernel: [    3.156588] xor: automatically using best checksumming function:
Aug 19 18:38:58 node-1 kernel: [    3.156971] 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
Aug 19 18:38:58 node-1 kernel: [    3.157962] 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
Aug 19 18:38:58 node-1 kernel: [    3.158490] 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
Aug 19 18:38:58 node-1 kernel: [    3.159304] 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
Aug 19 18:38:58 node-1 kernel: [    3.159957] 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
Aug 19 18:38:58 node-1 kernel: [    3.222870] megaraid_sas 0000:01:00.0: Controller type: iMR
Aug 19 18:38:58 node-1 kernel: [    3.228855] scsi0 : LSI SAS based MegaRAID driver
Aug 19 18:38:58 node-1 kernel: [    3.236214] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Aug 19 18:38:58 node-1 kernel: [    3.253171] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Aug 19 18:38:58 node-1 kernel: [    3.258808]    avx       : 36461.000 MB/sec
Aug 19 18:38:58 node-1 kernel: [    3.272513] async_tx: api initialized (async)
Aug 19 18:38:58 node-1 kernel: [    3.275432] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Aug 19 18:38:58 node-1 kernel: [    3.275602] sd 0:2:0:0: Attached scsi generic sg0 type 0
Aug 19 18:38:58 node-1 kernel: [    3.275742] sd 0:2:0:0: [sda] Write Protect is off
Aug 19 18:38:58 node-1 kernel: [    3.275743] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Aug 19 18:38:58 node-1 kernel: [    3.275814] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Aug 19 18:38:58 node-1 kernel: [    3.304418]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Aug 19 18:38:58 node-1 kernel: [    3.305808] sd 0:2:0:0: [sda] Attached SCSI disk
Aug 19 18:38:58 node-1 kernel: [    3.336803] md: raid6 personality registered for level 6
Aug 19 18:38:58 node-1 kernel: [    3.343653] md: raid5 personality registered for level 5
Aug 19 18:38:58 node-1 kernel: [    3.350341] md: raid4 personality registered for level 4
Aug 19 18:38:58 node-1 kernel: [    3.360033] md: raid10 personality registered for level 10
Aug 19 18:38:58 node-1 kernel: [    3.411747] multipathd (359): /proc/359/oom_adj is deprecated, please use /proc/359/oom_score_adj instead.
Aug 19 18:38:58 node-1 kernel: [    3.467212] random: lvm urandom read with 29 bits of entropy available
Aug 19 18:38:58 node-1 kernel: [    3.586737] bio: create slab <bio-1> at 1
Aug 19 18:38:58 node-1 kernel: [    4.357064] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Aug 19 18:38:58 node-1 kernel: [    4.996956] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Aug 19 18:38:58 node-1 kernel: [    5.020816] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Aug 19 18:38:58 node-1 kernel: [    5.108883] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Aug 19 18:38:58 node-1 kernel: [    5.162786] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Aug 19 18:38:58 node-1 kernel: [    5.263848] random: nonblocking pool is initialized
Aug 19 18:38:58 node-1 kernel: [    5.274753] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Aug 19 18:38:58 node-1 kernel: [    5.448217] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Aug 19 18:38:58 node-1 kernel: [    5.491978] XFS (dm-0): Mounting Filesystem
Aug 19 18:38:58 node-1 kernel: [    5.833964] XFS (dm-0): Ending clean mount
Aug 19 18:38:58 node-1 kernel: [    5.895195] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Aug 19 18:38:58 node-1 kernel: [    5.919808] XFS (dm-1): Mounting Filesystem
Aug 19 18:38:58 node-1 kernel: [    6.031091] XFS (dm-1): Ending clean mount
Aug 19 18:38:58 node-1 kernel: [    7.823900] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Aug 19 18:38:58 node-1 kernel: [    7.837817] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Aug 19 18:38:58 node-1 kernel: [    7.982939] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 19 18:38:58 node-1 kernel: [    7.982953] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Aug 19 18:38:58 node-1 kernel: [    7.982963] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Aug 19 18:38:58 node-1 kernel: [    7.982972] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Aug 19 18:38:58 node-1 kernel: [    8.027392] systemd-udevd[776]: starting version 204
Aug 19 18:38:58 node-1 kernel: [    8.220067] IPMI System Interface driver.
Aug 19 18:38:58 node-1 kernel: [    8.220125] ipmi_si: probing via ACPI
Aug 19 18:38:58 node-1 kernel: [    8.220141] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Aug 19 18:38:58 node-1 kernel: [    8.220142] ipmi_si: Adding ACPI-specified kcs state machine
Aug 19 18:38:58 node-1 kernel: [    8.220151] ipmi_si: probing via SMBIOS
Aug 19 18:38:58 node-1 kernel: [    8.220152] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Aug 19 18:38:58 node-1 kernel: [    8.220153] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Aug 19 18:38:58 node-1 kernel: [    8.220154] ipmi_si: probing via SPMI
Aug 19 18:38:58 node-1 kernel: [    8.220155] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Aug 19 18:38:58 node-1 kernel: [    8.220156] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Aug 19 18:38:58 node-1 kernel: [    8.220157] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Aug 19 18:38:58 node-1 kernel: [    8.230323] power_meter ACPI000D:00: Found ACPI power meter.
Aug 19 18:38:58 node-1 kernel: [    8.230330] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Aug 19 18:38:58 node-1 kernel: [    8.238585] wmi: Mapper loaded
Aug 19 18:38:58 node-1 kernel: [    8.264198] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Aug 19 18:38:58 node-1 kernel: [    8.264203] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Aug 19 18:38:58 node-1 kernel: [    8.264205] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Aug 19 18:38:58 node-1 kernel: [    8.264207] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Aug 19 18:38:58 node-1 kernel: [    8.264220] lpc_ich: Resource conflict(s) found affecting gpio_ich
Aug 19 18:38:58 node-1 kernel: [    8.269106] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Aug 19 18:38:58 node-1 kernel: [    8.350969] systemd-udevd[804]: renamed network interface eth0 to enp6s0
Aug 19 18:38:58 node-1 kernel: [    8.358986] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Aug 19 18:38:58 node-1 kernel: [    8.358991] ipmi_si 00:09: IPMI kcs interface initialized
Aug 19 18:38:58 node-1 kernel: [    8.374836] systemd-udevd[807]: renamed network interface eth3 to enp9s0
Aug 19 18:38:58 node-1 kernel: [    8.402864] systemd-udevd[797]: renamed network interface eth2 to enp8s0
Aug 19 18:38:58 node-1 kernel: [    8.434779] systemd-udevd[794]: renamed network interface eth1 to enp7s0
Aug 19 18:38:58 node-1 kernel: [    8.664518] type=1400 audit(1471631910.699:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1044 comm="apparmor_parser"
Aug 19 18:38:58 node-1 kernel: [    8.664672] type=1400 audit(1471631910.699:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1044 comm="apparmor_parser"
Aug 19 18:38:58 node-1 kernel: [    8.664796] type=1400 audit(1471631910.699:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1044 comm="apparmor_parser"
Aug 19 18:38:58 node-1 kernel: [    8.672892] type=1400 audit(1471631910.707:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1068 comm="apparmor_parser"
Aug 19 18:38:58 node-1 kernel: [    8.673043] type=1400 audit(1471631910.707:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1068 comm="apparmor_parser"
Aug 19 18:38:58 node-1 kernel: [    8.673163] type=1400 audit(1471631910.707:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1068 comm="apparmor_parser"
Aug 19 18:38:58 node-1 kernel: [    8.691752] type=1400 audit(1471631910.727:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1052 comm="apparmor_parser"
Aug 19 18:38:58 node-1 kernel: [    8.691893] type=1400 audit(1471631910.727:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1052 comm="apparmor_parser"
Aug 19 18:38:58 node-1 kernel: [    8.692011] type=1400 audit(1471631910.727:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1052 comm="apparmor_parser"
Aug 19 18:38:58 node-1 kernel: [    8.696173] type=1400 audit(1471631910.731:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1042 comm="apparmor_parser"
Aug 19 18:38:58 node-1 kernel: [    9.169980] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Aug 19 18:38:58 node-1 kernel: [    9.170732] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Aug 19 18:38:58 node-1 kernel: [    9.362728] enic 0000:06:00.0 enp6s0: Link UP
Aug 19 18:38:58 node-1 kernel: [    9.363848] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Aug 19 18:38:58 node-1 kernel: [    9.363857] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Aug 19 18:38:58 node-1 kernel: [   18.899184] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Aug 19 18:38:59 node-1 failsafe: Failsafe of 120 seconds reached.
Aug 19 18:38:59 node-1 kernel: [   37.344026] init: failsafe main process (8414) killed by TERM signal
Aug 19 18:38:59 node-1 dbus[8448]: [system] AppArmor D-Bus mediation is enabled
Aug 19 18:38:59 node-1 kernel: [   37.562139] audit_printk_skb: 30 callbacks suppressed
Aug 19 18:38:59 node-1 kernel: [   37.562141] type=1400 audit(1471631939.981:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8538 comm="apparmor_parser"
Aug 19 18:38:59 node-1 kernel: [   37.562232] type=1400 audit(1471631939.981:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8537 comm="apparmor_parser"
Aug 19 18:38:59 node-1 kernel: [   37.562237] type=1400 audit(1471631939.981:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8537 comm="apparmor_parser"
Aug 19 18:38:59 node-1 kernel: [   37.562250] type=1400 audit(1471631939.981:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8537 comm="apparmor_parser"
Aug 19 18:38:59 node-1 kernel: [   37.562477] type=1400 audit(1471631939.981:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8537 comm="apparmor_parser"
Aug 19 18:38:59 node-1 kernel: [   37.562479] type=1400 audit(1471631939.981:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8537 comm="apparmor_parser"
Aug 19 18:38:59 node-1 kernel: [   37.562594] type=1400 audit(1471631939.981:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8537 comm="apparmor_parser"
Aug 19 18:39:00 node-1 kernel: [   37.651703] type=1400 audit(1471631940.069:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8540 comm="apparmor_parser"
Aug 19 18:39:00 node-1 anacron[8606]: Anacron 2.3 started on 2016-08-19
Aug 19 18:39:00 node-1 cron[8570]: (CRON) INFO (pidfile fd = 3)
Aug 19 18:39:00 node-1 anacron[8606]: Will run job `cron.daily' in 5 min.
Aug 19 18:39:00 node-1 anacron[8606]: Will run job `cron.weekly' in 10 min.
Aug 19 18:39:00 node-1 anacron[8606]: Will run job `cron.monthly' in 15 min.
Aug 19 18:39:00 node-1 anacron[8606]: Jobs will be executed sequentially
Aug 19 18:39:00 node-1 cron[8614]: (CRON) STARTUP (fork ok)
Aug 19 18:39:00 node-1 multipathd: path checkers start up
Aug 19 18:39:00 node-1 cron[8614]: (CRON) INFO (Running @reboot jobs)
Aug 19 18:39:00 node-1 postfix/master[8751]: daemon started -- version 2.11.0, configuration /etc/postfix
Aug 19 18:39:03 node-1 puppet-agent[8936]: Reopening log files
Aug 19 18:39:04 node-1 puppet-agent[8936]: Could not request certificate: Connection refused - connect(2)
Aug 19 18:39:19 node-1 puppet-user[9144]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Aug 19 18:39:19 node-1 puppet-user[9144]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Aug 19 18:39:20 node-1 puppet-user[9144]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Aug 19 18:39:20 node-1 puppet-user[9144]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Aug 19 18:39:20 node-1 puppet-user[9144]: Finished catalog run in 0.91 seconds
Aug 19 18:39:21 node-1 multipathd: uevent trigger error
Aug 19 18:39:21 node-1 puppet-user[9569]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Aug 19 18:39:21 node-1 puppet-user[9569]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Aug 19 18:39:22 node-1 puppet-user[9569]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Aug 19 18:39:22 node-1 puppet-user[9569]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Aug 19 18:39:22 node-1 puppet-user[9569]: (/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"]'
Aug 19 18:39:22 node-1 puppet-user[9569]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Aug 19 18:39:22 node-1 puppet-user[9569]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Aug 19 18:39:22 node-1 puppet-user[9569]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Aug 19 18:39:22 node-1 puppet-user[9569]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Aug 19 18:39:22 node-1 puppet-user[9569]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Aug 19 18:39:22 node-1 puppet-user[9569]: Finished catalog run in 0.06 seconds
Aug 19 18:39:23 node-1 puppet-user[10021]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Aug 19 18:39:23 node-1 puppet-user[10021]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Aug 19 18:39:23 node-1 puppet-user[10021]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Aug 19 18:39:23 node-1 puppet-user[10021]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Aug 19 18:39:23 node-1 puppet-user[10021]: Finished catalog run in 0.02 seconds
Aug 19 18:39:24 node-1 puppet-user[10479]: (Scope(Class[main])) MODULAR: configuration_symlink
Aug 19 18:39:24 node-1 puppet-user[10479]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Aug 19 18:39:25 node-1 puppet-user[10479]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Aug 19 18:39:25 node-1 puppet-user[10479]: Finished catalog run in 0.04 seconds
Aug 19 18:39:26 node-1 puppet-user[10924]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Aug 19 18:39:26 node-1 puppet-user[10924]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Aug 19 18:39:26 node-1 puppet-user[10924]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Aug 19 18:39:26 node-1 kernel: [   64.474366] nr_pdflush_threads exported in /proc is scheduled for removal
Aug 19 18:39:26 node-1 kernel: [   64.474415] 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.
Aug 19 18:39:26 node-1 puppet-user[10924]: (/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'
Aug 19 18:39:26 node-1 puppet-user[10924]: Finished catalog run in 0.05 seconds
Aug 19 18:39:28 node-1 puppet-user[11395]: (Scope(Class[main])) MODULAR: sync_time
Aug 19 18:39:28 node-1 puppet-user[11395]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Aug 19 18:39:28 node-1 ntpdate[11985]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Aug 19 18:39:34 node-1 ntpdate[11985]: adjust time server 10.20.0.2 offset -0.179462 sec
Aug 19 18:39:34 node-1 puppet-user[11395]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Aug 19 18:39:34 node-1 puppet-user[11395]: Finished catalog run in 6.18 seconds
Aug 19 18:39:39 node-1 puppet-user[12187]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Aug 19 18:39:40 node-1 puppet-user[12187]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Aug 19 18:39:40 node-1 puppet-user[12187]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Aug 19 18:39:40 node-1 puppet-user[12187]: Finished catalog run in 0.06 seconds
Aug 19 18:39:40 node-1 kernel: [   78.398659] init: plymouth-upstart-bridge main process ended, respawning
Aug 19 18:39:41 node-1 puppet-agent[8936]: Could not run: SIGTERM
Aug 19 18:39:41 node-1 kernel: [   78.689103] ip_tables: (C) 2000-2006 Netfilter Core Team
Aug 19 18:39:41 node-1 ec2: 
Aug 19 18:39:41 node-1 ec2: #############################################################
Aug 19 18:39:41 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Aug 19 18:39:41 node-1 ec2: 1024 33:4f:cf:cf:9e:3b:1f:00:aa:e6:75:e3:09:75:e6:36  root@node-1.domain.tld (DSA)
Aug 19 18:39:41 node-1 ec2: 256 ee:71:93:34:c5:61:2d:6c:9e:a4:5c:9c:51:d5:2b:41  root@node-1.domain.tld (ECDSA)
Aug 19 18:39:41 node-1 ec2: 256 9e:b8:4f:78:5d:ae:ac:57:00:5b:a9:78:ce:52:b6:48  root@node-1.domain.tld (ED25519)
Aug 19 18:39:41 node-1 ec2: 2048 9c:99:f1:91:f6:9d:78:ef:6b:c6:0d:7a:9e:36:97:11  root@node-1.domain.tld (RSA)
Aug 19 18:39:41 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Aug 19 18:39:41 node-1 ec2: #############################################################
Aug 19 18:39:41 node-1 puppet-user[12639]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Aug 19 18:39:42 node-1 puppet-user[12639]: Compiled catalog for node-1.domain.tld in environment production in 0.93 seconds
Aug 19 18:39:42 node-1 puppet-user[12639]: (/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
Aug 19 18:39:42 node-1 puppet-user[12639]: (/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
Aug 19 18:39:42 node-1 puppet-user[12639]: (/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
Aug 19 18:39:42 node-1 puppet-user[12639]: (/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
Aug 19 18:39:42 node-1 puppet-user[12639]: (/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
Aug 19 18:39:42 node-1 puppet-user[12639]: (/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
Aug 19 18:39:42 node-1 puppet-user[12639]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Aug 19 18:39:42 node-1 puppet-user[12639]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Aug 19 18:39:42 node-1 puppet-user[12639]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Aug 19 18:39:42 node-1 puppet-user[12639]: (/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
Aug 19 18:39:42 node-1 puppet-user[12639]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Aug 19 18:39:42 node-1 puppet-user[12639]: (/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
Aug 19 18:39:42 node-1 puppet-user[12639]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Aug 19 18:39:42 node-1 puppet-user[12639]: (/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
Aug 19 18:39:42 node-1 puppet-user[12639]: (/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
Aug 19 18:39:42 node-1 puppet-user[12639]: (/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
Aug 19 18:39:42 node-1 puppet-user[12639]: (/Stage[main]/Apt/File[preferences]/ensure) created
Aug 19 18:39:42 node-1 puppet-user[12639]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Aug 19 18:40:01 node-1 CRON[13874]: (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")
Aug 19 18:40:01 node-1 puppet-user[12639]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Aug 19 18:40:01 node-1 puppet-user[12639]: Finished catalog run in 19.17 seconds
Aug 19 18:40:03 node-1 puppet-user[13928]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Aug 19 18:40:04 node-1 puppet-user[13928]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Aug 19 18:40:08 node-1 puppet-user[13928]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Aug 19 18:40:24 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Aug 19 18:40:24 node-1 nailgun-agent: I, [2016-08-19T18:40:24.467457 #13877]  INFO -- : API URL is https://10.20.0.2:8443/api
Aug 19 18:40:37 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Aug 19 18:40:37 node-1 nailgun-agent: I, [2016-08-19T18:40:37.612518 #13877]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Aug 19 18:40:38 node-1 puppet-user[13928]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Aug 19 18:40:39 node-1 puppet-user[13928]: Finished catalog run in 34.75 seconds
Aug 19 18:40:40 node-1 puppet-user[16665]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Aug 19 18:40:41 node-1 puppet-user[16665]: Compiled catalog for node-1.domain.tld in environment production in 0.62 seconds
Aug 19 18:40:41 node-1 puppet-user[16665]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Aug 19 18:40:41 node-1 puppet-user[16665]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Aug 19 18:40:41 node-1 puppet-user[16665]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Aug 19 18:40:41 node-1 puppet-user[16665]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Aug 19 18:40:41 node-1 puppet-user[16665]: Finished catalog run in 0.10 seconds
Aug 19 18:40:43 node-1 puppet-user[17124]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Aug 19 18:40:44 node-1 puppet-user[17124]: Compiled catalog for node-1.domain.tld in environment production in 0.81 seconds
Aug 19 18:40:44 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Aug 19 18:40:44 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Aug 19 18:40:44 node-1 crontab[17570]: (root) LIST (root)
Aug 19 18:40:44 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Aug 19 18:40:44 node-1 crontab[17571]: (root) REPLACE (root)
Aug 19 18:40:46 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/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
Aug 19 18:40:48 node-1 puppet-user[17124]: (/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
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/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
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/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
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/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
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/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
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Aug 19 18:40:48 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Aug 19 18:40:49 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Aug 19 18:40:49 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Aug 19 18:40:49 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Aug 19 18:40:49 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Aug 19 18:40:49 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Aug 19 18:40:49 node-1 puppet-user[17124]: (/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
Aug 19 18:40:49 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Aug 19 18:40:49 node-1 puppet-user[17124]: (/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
Aug 19 18:40:49 node-1 puppet-user[17124]: (/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
Aug 19 18:40:49 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Aug 19 18:40:49 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Aug 19 18:40:49 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Aug 19 18:40:49 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8387" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 19 18:40:49 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Aug 19 18:40:51 node-1 multipathd: uevent trigger error
<27>Aug 19 18:40:51 node-1 multipathd: uevent trigger error
<27>Aug 19 18:40:51 node-1 multipathd: uevent trigger error
<27>Aug 19 18:40:51 node-1 multipathd: uevent trigger error
<27>Aug 19 18:40:51 node-1 multipathd: uevent trigger error
<27>Aug 19 18:41:09 node-1 multipathd: uevent trigger error
<27>Aug 19 18:41:09 node-1 multipathd: uevent trigger error
<27>Aug 19 18:41:09 node-1 multipathd: uevent trigger error
<27>Aug 19 18:41:09 node-1 multipathd: uevent trigger error
<27>Aug 19 18:41:09 node-1 multipathd: uevent trigger error
<27>Aug 19 18:41:12 node-1 multipathd: uevent trigger error
<27>Aug 19 18:41:12 node-1 multipathd: uevent trigger error
<27>Aug 19 18:41:12 node-1 multipathd: uevent trigger error
<27>Aug 19 18:41:12 node-1 multipathd: uevent trigger error
<27>Aug 19 18:41:12 node-1 multipathd: uevent trigger error
<27>Aug 19 18:42:12 node-1 ntpdate[28969]: no servers can be used, exiting
<27>Aug 19 18:42:12 node-1 ntpdate[29223]: no servers can be used, exiting
<27>Aug 19 18:42:43 node-1 multipathd: uevent trigger error
<27>Aug 19 18:42:43 node-1 multipathd: uevent trigger error
<27>Aug 19 18:42:43 node-1 multipathd: uevent trigger error
<27>Aug 19 18:42:43 node-1 multipathd: uevent trigger error
<27>Aug 19 18:42:43 node-1 multipathd: uevent trigger error
<27>Aug 19 18:42:46 node-1 multipathd: uevent trigger error
<27>Aug 19 18:42:47 node-1 multipathd: uevent trigger error
<27>Aug 19 18:42:47 node-1 multipathd: uevent trigger error
<27>Aug 19 18:42:47 node-1 multipathd: uevent trigger error
<27>Aug 19 18:42:47 node-1 multipathd: uevent trigger error
<27>Aug 19 18:42:58 node-1 multipathd: uevent trigger error
<27>Aug 19 18:42:58 node-1 multipathd: uevent trigger error
<27>Aug 19 18:42:58 node-1 multipathd: uevent trigger error
<27>Aug 19 18:42:58 node-1 multipathd: uevent trigger error
<27>Aug 19 18:42:58 node-1 multipathd: uevent trigger error
<27>Aug 19 18:43:01 node-1 multipathd: uevent trigger error
<27>Aug 19 18:43:01 node-1 multipathd: uevent trigger error
<27>Aug 19 18:43:01 node-1 multipathd: uevent trigger error
<27>Aug 19 18:43:01 node-1 multipathd: uevent trigger error
<27>Aug 19 18:43:01 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:01 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:01 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:01 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:01 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:10 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:10 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:10 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:10 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:10 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:12 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 19 18:44:12 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 19 18:44:18 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 19 18:44:18 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 19 18:44:24 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 19 18:44:29 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 19 18:44:29 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 19 18:44:36 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:36 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:36 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:36 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:36 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:49 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:49 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:49 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:49 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:49 node-1 multipathd: uevent trigger error
<129>Aug 19 18:44:51 node-1 haproxy[16785]: 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>Aug 19 18:44:52 node-1 haproxy[16790]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:44:53 node-1 haproxy[16790]: 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>Aug 19 18:44:53 node-1 haproxy[16790]: proxy mysqld has no server available!
<27>Aug 19 18:44:55 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:55 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:55 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:55 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:55 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:58 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:58 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:58 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:58 node-1 multipathd: uevent trigger error
<27>Aug 19 18:44:58 node-1 multipathd: uevent trigger error
<129>Aug 19 18:45:01 node-1 haproxy[19406]: 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>Aug 19 18:45:01 node-1 haproxy[19406]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:01 node-1 haproxy[19406]: 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>Aug 19 18:45:01 node-1 haproxy[19406]: proxy mysqld has no server available!
<129>Aug 19 18:45:02 node-1 haproxy[19410]: 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>Aug 19 18:45:02 node-1 haproxy[19410]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:02 node-1 haproxy[19410]: 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>Aug 19 18:45:02 node-1 haproxy[19410]: proxy object-storage has no server available!
<27>Aug 19 18:45:04 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:04 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:04 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:04 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:04 node-1 multipathd: uevent trigger error
<129>Aug 19 18:45:06 node-1 haproxy[20786]: 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>Aug 19 18:45:06 node-1 haproxy[20786]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:06 node-1 haproxy[20786]: 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>Aug 19 18:45:06 node-1 haproxy[20786]: proxy neutron has no server available!
<129>Aug 19 18:45:07 node-1 haproxy[20792]: 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>Aug 19 18:45:07 node-1 haproxy[20792]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:07 node-1 haproxy[20792]: 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>Aug 19 18:45:07 node-1 haproxy[20792]: proxy mysqld has no server available!
<129>Aug 19 18:45:07 node-1 haproxy[20792]: 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>Aug 19 18:45:08 node-1 haproxy[20792]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:08 node-1 haproxy[20792]: 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>Aug 19 18:45:08 node-1 haproxy[20792]: proxy object-storage has no server available!
<27>Aug 19 18:45:09 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:09 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:09 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:09 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:09 node-1 multipathd: uevent trigger error
<129>Aug 19 18:45:11 node-1 haproxy[22142]: 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>Aug 19 18:45:12 node-1 haproxy[22146]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:12 node-1 haproxy[22146]: 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>Aug 19 18:45:12 node-1 haproxy[22146]: proxy keystone-1 has no server available!
<129>Aug 19 18:45:12 node-1 haproxy[22146]: 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>Aug 19 18:45:12 node-1 haproxy[22146]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:12 node-1 haproxy[22146]: 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>Aug 19 18:45:12 node-1 haproxy[22146]: proxy keystone-2 has no server available!
<129>Aug 19 18:45:12 node-1 haproxy[22146]: 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>Aug 19 18:45:12 node-1 haproxy[22146]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:13 node-1 haproxy[22146]: 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>Aug 19 18:45:13 node-1 haproxy[22146]: proxy neutron has no server available!
<129>Aug 19 18:45:13 node-1 haproxy[22146]: 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>Aug 19 18:45:13 node-1 haproxy[22146]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:13 node-1 haproxy[22146]: 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>Aug 19 18:45:13 node-1 haproxy[22146]: proxy mysqld has no server available!
<129>Aug 19 18:45:13 node-1 haproxy[22146]: 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>Aug 19 18:45:13 node-1 haproxy[22146]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:13 node-1 haproxy[22146]: 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>Aug 19 18:45:13 node-1 haproxy[22146]: proxy object-storage has no server available!
<27>Aug 19 18:45:15 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:15 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:15 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:15 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:15 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:15 node-1 multipathd: uevent trigger error
<129>Aug 19 18:45:17 node-1 haproxy[23598]: 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>Aug 19 18:45:17 node-1 haproxy[23598]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:17 node-1 haproxy[23598]: 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>Aug 19 18:45:17 node-1 haproxy[23598]: proxy keystone-1 has no server available!
<129>Aug 19 18:45:17 node-1 haproxy[23598]: 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>Aug 19 18:45:17 node-1 haproxy[23598]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:17 node-1 haproxy[23598]: 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>Aug 19 18:45:17 node-1 haproxy[23598]: proxy keystone-2 has no server available!
<129>Aug 19 18:45:18 node-1 haproxy[23618]: 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>Aug 19 18:45:18 node-1 haproxy[23618]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:18 node-1 haproxy[23618]: 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>Aug 19 18:45:18 node-1 haproxy[23618]: proxy neutron has no server available!
<129>Aug 19 18:45:18 node-1 haproxy[23618]: 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>Aug 19 18:45:18 node-1 haproxy[23618]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:18 node-1 haproxy[23618]: 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>Aug 19 18:45:18 node-1 haproxy[23618]: proxy mysqld has no server available!
<129>Aug 19 18:45:18 node-1 haproxy[23618]: 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>Aug 19 18:45:18 node-1 haproxy[23618]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:18 node-1 haproxy[23618]: 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>Aug 19 18:45:18 node-1 haproxy[23618]: proxy object-storage has no server available!
<129>Aug 19 18:45:19 node-1 haproxy[23618]: 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>Aug 19 18:45:19 node-1 haproxy[23618]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:19 node-1 haproxy[23618]: 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>Aug 19 18:45:19 node-1 haproxy[23618]: proxy aodh has no server available!
<27>Aug 19 18:45:20 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:20 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:20 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:20 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:20 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:20 node-1 multipathd: uevent trigger error
<129>Aug 19 18:45:22 node-1 haproxy[25036]: 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>Aug 19 18:45:23 node-1 haproxy[25040]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:23 node-1 haproxy[25040]: 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>Aug 19 18:45:23 node-1 haproxy[25040]: proxy keystone-1 has no server available!
<129>Aug 19 18:45:23 node-1 haproxy[25040]: 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>Aug 19 18:45:23 node-1 haproxy[25040]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:23 node-1 haproxy[25040]: 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>Aug 19 18:45:23 node-1 haproxy[25040]: proxy keystone-2 has no server available!
<129>Aug 19 18:45:23 node-1 haproxy[25040]: 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>Aug 19 18:45:23 node-1 haproxy[25040]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:23 node-1 haproxy[25040]: 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>Aug 19 18:45:23 node-1 haproxy[25040]: proxy neutron has no server available!
<129>Aug 19 18:45:23 node-1 haproxy[25040]: 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>Aug 19 18:45:23 node-1 haproxy[25040]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:23 node-1 haproxy[25040]: 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>Aug 19 18:45:23 node-1 haproxy[25040]: proxy mysqld has no server available!
<129>Aug 19 18:45:24 node-1 haproxy[25040]: 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>Aug 19 18:45:24 node-1 haproxy[25040]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:24 node-1 haproxy[25040]: 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>Aug 19 18:45:24 node-1 haproxy[25040]: proxy object-storage has no server available!
<129>Aug 19 18:45:24 node-1 haproxy[25040]: 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>Aug 19 18:45:24 node-1 haproxy[25040]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:24 node-1 haproxy[25040]: 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>Aug 19 18:45:24 node-1 haproxy[25040]: proxy aodh has no server available!
<129>Aug 19 18:45:24 node-1 haproxy[25040]: 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>Aug 19 18:45:24 node-1 haproxy[25040]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:24 node-1 haproxy[25040]: 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>Aug 19 18:45:24 node-1 haproxy[25040]: proxy ceilometer has no server available!
<27>Aug 19 18:45:26 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:26 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:26 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:26 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:26 node-1 multipathd: uevent trigger error
<129>Aug 19 18:45:28 node-1 haproxy[26390]: 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>Aug 19 18:45:28 node-1 haproxy[26390]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:28 node-1 haproxy[26390]: 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>Aug 19 18:45:28 node-1 haproxy[26390]: proxy keystone-1 has no server available!
<129>Aug 19 18:45:28 node-1 haproxy[26390]: 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>Aug 19 18:45:28 node-1 haproxy[26390]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:28 node-1 haproxy[26390]: 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>Aug 19 18:45:28 node-1 haproxy[26390]: proxy keystone-2 has no server available!
<129>Aug 19 18:45:28 node-1 haproxy[26390]: 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>Aug 19 18:45:29 node-1 haproxy[26394]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:29 node-1 haproxy[26394]: 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>Aug 19 18:45:29 node-1 haproxy[26394]: proxy neutron has no server available!
<129>Aug 19 18:45:29 node-1 haproxy[26394]: 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>Aug 19 18:45:29 node-1 haproxy[26394]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:29 node-1 haproxy[26394]: 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>Aug 19 18:45:29 node-1 haproxy[26394]: proxy mysqld has no server available!
<129>Aug 19 18:45:29 node-1 haproxy[26394]: 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>Aug 19 18:45:29 node-1 haproxy[26394]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:29 node-1 haproxy[26394]: 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>Aug 19 18:45:29 node-1 haproxy[26394]: proxy object-storage has no server available!
<129>Aug 19 18:45:29 node-1 haproxy[26394]: 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>Aug 19 18:45:29 node-1 haproxy[26394]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:29 node-1 haproxy[26394]: 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>Aug 19 18:45:29 node-1 haproxy[26394]: proxy aodh has no server available!
<129>Aug 19 18:45:30 node-1 haproxy[26394]: 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>Aug 19 18:45:30 node-1 haproxy[26394]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:30 node-1 haproxy[26394]: 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>Aug 19 18:45:30 node-1 haproxy[26394]: proxy ceilometer has no server available!
<27>Aug 19 18:45:31 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:31 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:31 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:31 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:31 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:31 node-1 multipathd: uevent trigger error
<129>Aug 19 18:45:33 node-1 haproxy[27931]: 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>Aug 19 18:45:34 node-1 haproxy[27935]: 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>Aug 19 18:45:34 node-1 haproxy[27935]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:34 node-1 haproxy[27935]: 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>Aug 19 18:45:34 node-1 haproxy[27935]: proxy keystone-1 has no server available!
<129>Aug 19 18:45:34 node-1 haproxy[27935]: 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>Aug 19 18:45:34 node-1 haproxy[27935]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:34 node-1 haproxy[27935]: 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>Aug 19 18:45:34 node-1 haproxy[27935]: proxy keystone-2 has no server available!
<129>Aug 19 18:45:34 node-1 haproxy[27935]: 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>Aug 19 18:45:34 node-1 haproxy[27935]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:34 node-1 haproxy[27935]: 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>Aug 19 18:45:34 node-1 haproxy[27935]: proxy neutron has no server available!
<129>Aug 19 18:45:34 node-1 haproxy[27935]: 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>Aug 19 18:45:34 node-1 haproxy[27935]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:34 node-1 haproxy[27935]: 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>Aug 19 18:45:34 node-1 haproxy[27935]: proxy mysqld has no server available!
<129>Aug 19 18:45:35 node-1 haproxy[27935]: 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>Aug 19 18:45:35 node-1 haproxy[27935]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:35 node-1 haproxy[27935]: 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>Aug 19 18:45:35 node-1 haproxy[27935]: proxy object-storage has no server available!
<129>Aug 19 18:45:35 node-1 haproxy[27935]: 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>Aug 19 18:45:35 node-1 haproxy[27935]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:35 node-1 haproxy[27935]: 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>Aug 19 18:45:35 node-1 haproxy[27935]: proxy aodh has no server available!
<129>Aug 19 18:45:35 node-1 haproxy[27935]: 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>Aug 19 18:45:35 node-1 haproxy[27935]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:35 node-1 haproxy[27935]: 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>Aug 19 18:45:35 node-1 haproxy[27935]: proxy ceilometer has no server available!
<27>Aug 19 18:45:36 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:36 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:36 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:36 node-1 multipathd: uevent trigger error
<129>Aug 19 18:45:39 node-1 haproxy[29296]: 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>Aug 19 18:45:39 node-1 haproxy[29296]: 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>Aug 19 18:45:39 node-1 haproxy[29296]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:39 node-1 haproxy[29296]: 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>Aug 19 18:45:39 node-1 haproxy[29296]: proxy keystone-1 has no server available!
<129>Aug 19 18:45:39 node-1 haproxy[29296]: 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>Aug 19 18:45:40 node-1 haproxy[29300]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:40 node-1 haproxy[29300]: 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>Aug 19 18:45:40 node-1 haproxy[29300]: proxy keystone-2 has no server available!
<129>Aug 19 18:45:40 node-1 haproxy[29300]: 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>Aug 19 18:45:40 node-1 haproxy[29300]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:40 node-1 haproxy[29300]: 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>Aug 19 18:45:40 node-1 haproxy[29300]: proxy glance-api has no server available!
<129>Aug 19 18:45:40 node-1 haproxy[29300]: 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>Aug 19 18:45:40 node-1 haproxy[29300]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:40 node-1 haproxy[29300]: 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>Aug 19 18:45:40 node-1 haproxy[29300]: proxy glance-glare has no server available!
<129>Aug 19 18:45:40 node-1 haproxy[29300]: 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>Aug 19 18:45:40 node-1 haproxy[29300]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:40 node-1 haproxy[29300]: 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>Aug 19 18:45:40 node-1 haproxy[29300]: proxy neutron has no server available!
<129>Aug 19 18:45:40 node-1 haproxy[29300]: 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>Aug 19 18:45:40 node-1 haproxy[29300]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:40 node-1 haproxy[29300]: 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>Aug 19 18:45:40 node-1 haproxy[29300]: proxy glance-registry has no server available!
<129>Aug 19 18:45:40 node-1 haproxy[29300]: 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>Aug 19 18:45:40 node-1 haproxy[29300]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:40 node-1 haproxy[29300]: 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>Aug 19 18:45:40 node-1 haproxy[29300]: proxy mysqld has no server available!
<129>Aug 19 18:45:41 node-1 haproxy[29300]: 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>Aug 19 18:45:41 node-1 haproxy[29300]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:41 node-1 haproxy[29300]: 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>Aug 19 18:45:41 node-1 haproxy[29300]: proxy object-storage has no server available!
<129>Aug 19 18:45:41 node-1 haproxy[29300]: 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>Aug 19 18:45:41 node-1 haproxy[29300]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:41 node-1 haproxy[29300]: 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>Aug 19 18:45:41 node-1 haproxy[29300]: proxy aodh has no server available!
<129>Aug 19 18:45:41 node-1 haproxy[29300]: 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>Aug 19 18:45:41 node-1 haproxy[29300]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:41 node-1 haproxy[29300]: 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>Aug 19 18:45:41 node-1 haproxy[29300]: proxy ceilometer has no server available!
<27>Aug 19 18:45:42 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:42 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:42 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:42 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:42 node-1 multipathd: uevent trigger error
<129>Aug 19 18:45:45 node-1 haproxy[30713]: 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>Aug 19 18:45:45 node-1 haproxy[30713]: 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>Aug 19 18:45:45 node-1 haproxy[30713]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:45 node-1 haproxy[30713]: 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>Aug 19 18:45:45 node-1 haproxy[30713]: proxy keystone-1 has no server available!
<129>Aug 19 18:45:45 node-1 haproxy[30713]: 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>Aug 19 18:45:45 node-1 haproxy[30713]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:45 node-1 haproxy[30713]: 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>Aug 19 18:45:45 node-1 haproxy[30713]: proxy keystone-2 has no server available!
<129>Aug 19 18:45:45 node-1 haproxy[30713]: 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>Aug 19 18:45:45 node-1 haproxy[30713]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:45 node-1 haproxy[30713]: 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>Aug 19 18:45:45 node-1 haproxy[30713]: proxy nova-api has no server available!
<129>Aug 19 18:45:45 node-1 haproxy[30713]: 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>Aug 19 18:45:46 node-1 haproxy[30717]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:46 node-1 haproxy[30717]: 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>Aug 19 18:45:46 node-1 haproxy[30717]: proxy nova-metadata-api has no server available!
<129>Aug 19 18:45:46 node-1 haproxy[30717]: 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>Aug 19 18:45:46 node-1 haproxy[30717]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:46 node-1 haproxy[30717]: 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>Aug 19 18:45:46 node-1 haproxy[30717]: proxy glance-api has no server available!
<129>Aug 19 18:45:46 node-1 haproxy[30717]: 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>Aug 19 18:45:46 node-1 haproxy[30717]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:46 node-1 haproxy[30717]: 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>Aug 19 18:45:46 node-1 haproxy[30717]: proxy glance-glare has no server available!
<129>Aug 19 18:45:46 node-1 haproxy[30717]: 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>Aug 19 18:45:46 node-1 haproxy[30717]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:46 node-1 haproxy[30717]: 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>Aug 19 18:45:46 node-1 haproxy[30717]: proxy neutron has no server available!
<129>Aug 19 18:45:46 node-1 haproxy[30717]: 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>Aug 19 18:45:46 node-1 haproxy[30717]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:46 node-1 haproxy[30717]: 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>Aug 19 18:45:46 node-1 haproxy[30717]: proxy glance-registry has no server available!
<129>Aug 19 18:45:46 node-1 haproxy[30717]: 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>Aug 19 18:45:46 node-1 haproxy[30717]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:46 node-1 haproxy[30717]: 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>Aug 19 18:45:46 node-1 haproxy[30717]: proxy mysqld has no server available!
<129>Aug 19 18:45:46 node-1 haproxy[30717]: 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>Aug 19 18:45:46 node-1 haproxy[30717]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:46 node-1 haproxy[30717]: 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>Aug 19 18:45:46 node-1 haproxy[30717]: proxy object-storage has no server available!
<129>Aug 19 18:45:46 node-1 haproxy[30717]: 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>Aug 19 18:45:47 node-1 haproxy[30717]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:47 node-1 haproxy[30717]: 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>Aug 19 18:45:47 node-1 haproxy[30717]: proxy aodh has no server available!
<129>Aug 19 18:45:47 node-1 haproxy[30717]: 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>Aug 19 18:45:47 node-1 haproxy[30717]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:47 node-1 haproxy[30717]: 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>Aug 19 18:45:47 node-1 haproxy[30717]: proxy ceilometer has no server available!
<129>Aug 19 18:45:47 node-1 haproxy[30717]: 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>Aug 19 18:45:47 node-1 haproxy[30717]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:47 node-1 haproxy[30717]: 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>Aug 19 18:45:47 node-1 haproxy[30717]: proxy nova-novncproxy has no server available!
<27>Aug 19 18:45:48 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:48 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:48 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:48 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:48 node-1 multipathd: uevent trigger error
<129>Aug 19 18:45:50 node-1 haproxy[32052]: 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>Aug 19 18:45:51 node-1 haproxy[32064]: 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>Aug 19 18:45:51 node-1 haproxy[32064]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:51 node-1 haproxy[32064]: 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>Aug 19 18:45:51 node-1 haproxy[32064]: proxy keystone-1 has no server available!
<129>Aug 19 18:45:51 node-1 haproxy[32064]: 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>Aug 19 18:45:51 node-1 haproxy[32064]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:51 node-1 haproxy[32064]: 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>Aug 19 18:45:51 node-1 haproxy[32064]: proxy keystone-2 has no server available!
<129>Aug 19 18:45:51 node-1 haproxy[32064]: 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>Aug 19 18:45:51 node-1 haproxy[32064]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:51 node-1 haproxy[32064]: 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>Aug 19 18:45:51 node-1 haproxy[32064]: proxy nova-api has no server available!
<129>Aug 19 18:45:51 node-1 haproxy[32064]: 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>Aug 19 18:45:51 node-1 haproxy[32064]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:51 node-1 haproxy[32064]: 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>Aug 19 18:45:51 node-1 haproxy[32064]: proxy nova-metadata-api has no server available!
<129>Aug 19 18:45:51 node-1 haproxy[32064]: 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>Aug 19 18:45:51 node-1 haproxy[32064]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:51 node-1 haproxy[32064]: 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>Aug 19 18:45:51 node-1 haproxy[32064]: proxy cinder-api has no server available!
<129>Aug 19 18:45:51 node-1 haproxy[32064]: 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>Aug 19 18:45:51 node-1 haproxy[32064]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:51 node-1 haproxy[32064]: 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>Aug 19 18:45:51 node-1 haproxy[32064]: proxy glance-api has no server available!
<129>Aug 19 18:45:51 node-1 haproxy[32064]: 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>Aug 19 18:45:51 node-1 haproxy[32064]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:51 node-1 haproxy[32064]: 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>Aug 19 18:45:51 node-1 haproxy[32064]: proxy glance-glare has no server available!
<129>Aug 19 18:45:51 node-1 haproxy[32064]: 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>Aug 19 18:45:52 node-1 haproxy[32064]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:52 node-1 haproxy[32064]: 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>Aug 19 18:45:52 node-1 haproxy[32064]: proxy neutron has no server available!
<129>Aug 19 18:45:52 node-1 haproxy[32064]: 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>Aug 19 18:45:52 node-1 haproxy[32064]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:52 node-1 haproxy[32064]: 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>Aug 19 18:45:52 node-1 haproxy[32064]: proxy glance-registry has no server available!
<129>Aug 19 18:45:52 node-1 haproxy[32064]: 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>Aug 19 18:45:52 node-1 haproxy[32064]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:52 node-1 haproxy[32064]: 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>Aug 19 18:45:52 node-1 haproxy[32064]: proxy mysqld has no server available!
<129>Aug 19 18:45:52 node-1 haproxy[32064]: 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>Aug 19 18:45:52 node-1 haproxy[32064]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:52 node-1 haproxy[32064]: 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>Aug 19 18:45:52 node-1 haproxy[32064]: proxy object-storage has no server available!
<129>Aug 19 18:45:52 node-1 haproxy[32064]: 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>Aug 19 18:45:52 node-1 haproxy[32064]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:52 node-1 haproxy[32064]: 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>Aug 19 18:45:52 node-1 haproxy[32064]: proxy aodh has no server available!
<129>Aug 19 18:45:52 node-1 haproxy[32064]: 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>Aug 19 18:45:52 node-1 haproxy[32064]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:52 node-1 haproxy[32064]: 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>Aug 19 18:45:52 node-1 haproxy[32064]: proxy ceilometer has no server available!
<129>Aug 19 18:45:52 node-1 haproxy[32064]: 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>Aug 19 18:45:52 node-1 haproxy[32064]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:52 node-1 haproxy[32064]: 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>Aug 19 18:45:52 node-1 haproxy[32064]: proxy nova-novncproxy has no server available!
<27>Aug 19 18:45:53 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:53 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:53 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:54 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:54 node-1 multipathd: uevent trigger error
<129>Aug 19 18:45:56 node-1 haproxy[1005]: 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>Aug 19 18:45:56 node-1 haproxy[1005]: 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>Aug 19 18:45:56 node-1 haproxy[1005]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:56 node-1 haproxy[1005]: 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>Aug 19 18:45:56 node-1 haproxy[1005]: proxy keystone-1 has no server available!
<129>Aug 19 18:45:56 node-1 haproxy[1005]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: proxy keystone-2 has no server available!
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: proxy nova-api has no server available!
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: proxy nova-metadata-api has no server available!
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: proxy cinder-api has no server available!
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: proxy glance-api has no server available!
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: proxy glance-glare has no server available!
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: proxy neutron has no server available!
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: proxy glance-registry has no server available!
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:57 node-1 haproxy[1009]: proxy mysqld has no server available!
<129>Aug 19 18:45:57 node-1 haproxy[1009]: 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>Aug 19 18:45:58 node-1 haproxy[1009]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:58 node-1 haproxy[1009]: 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>Aug 19 18:45:58 node-1 haproxy[1009]: proxy object-storage has no server available!
<129>Aug 19 18:45:58 node-1 haproxy[1009]: 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>Aug 19 18:45:58 node-1 haproxy[1009]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:58 node-1 haproxy[1009]: 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>Aug 19 18:45:58 node-1 haproxy[1009]: proxy aodh has no server available!
<129>Aug 19 18:45:58 node-1 haproxy[1009]: 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>Aug 19 18:45:58 node-1 haproxy[1009]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:58 node-1 haproxy[1009]: 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>Aug 19 18:45:58 node-1 haproxy[1009]: proxy ceilometer has no server available!
<129>Aug 19 18:45:58 node-1 haproxy[1009]: 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>Aug 19 18:45:58 node-1 haproxy[1009]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:58 node-1 haproxy[1009]: 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>Aug 19 18:45:58 node-1 haproxy[1009]: proxy heat-api has no server available!
<129>Aug 19 18:45:58 node-1 haproxy[1009]: 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>Aug 19 18:45:58 node-1 haproxy[1009]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:58 node-1 haproxy[1009]: 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>Aug 19 18:45:58 node-1 haproxy[1009]: proxy heat-api-cfn has no server available!
<129>Aug 19 18:45:58 node-1 haproxy[1009]: 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>Aug 19 18:45:58 node-1 haproxy[1009]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:58 node-1 haproxy[1009]: 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>Aug 19 18:45:58 node-1 haproxy[1009]: proxy heat-api-cloudwatch has no server available!
<129>Aug 19 18:45:58 node-1 haproxy[1009]: 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>Aug 19 18:45:58 node-1 haproxy[1009]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Aug 19 18:45:58 node-1 haproxy[1009]: 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>Aug 19 18:45:58 node-1 haproxy[1009]: proxy nova-novncproxy has no server available!
<27>Aug 19 18:45:59 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:59 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:59 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:59 node-1 multipathd: uevent trigger error
<27>Aug 19 18:45:59 node-1 multipathd: uevent trigger error
<27>Aug 19 18:46:03 node-1 multipathd: uevent trigger error
<27>Aug 19 18:46:03 node-1 multipathd: uevent trigger error
<27>Aug 19 18:46:03 node-1 multipathd: uevent trigger error
<27>Aug 19 18:46:03 node-1 multipathd: uevent trigger error
<27>Aug 19 18:46:03 node-1 multipathd: uevent trigger error
<27>Aug 19 18:46:03 node-1 multipathd: uevent trigger error
<27>Aug 19 18:46:13 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Aug 19 18:46:38 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>Aug 19 18:46:40 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Aug 19 18:47:08 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 19 18:47:15 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 19 18:47:37 node-1 multipathd: uevent trigger error
<27>Aug 19 18:47:37 node-1 multipathd: uevent trigger error
<27>Aug 19 18:47:37 node-1 multipathd: uevent trigger error
<27>Aug 19 18:47:37 node-1 multipathd: uevent trigger error
<27>Aug 19 18:47:37 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:03 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:03 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:03 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:03 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:03 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:03 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:10 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 19 18:50:10 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:10 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:10 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:10 node-1 multipathd: uevent trigger error
<43>Aug 19 18:50:30 node-1 apache2_error [Fri Aug 19 18:50:23.010232 2016] [mpm_event:notice] [pid 10942:tid 140378387494784] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Aug 19 18:50:30 node-1 apache2_error [Fri Aug 19 18:50:23.010373 2016] [core:notice] [pid 10942:tid 140378387494784] AH00094: Command line: '/usr/sbin/apache2'
<43>Aug 19 18:50:30 node-1 apache2_error [Fri Aug 19 18:50:24.974924 2016] [mpm_event:notice] [pid 10942:tid 140378387494784] AH00491: caught SIGTERM, shutting down
<43>Aug 19 18:50:30 node-1 apache2_error [Fri Aug 19 18:50:26.055206 2016] [mpm_worker:notice] [pid 11277:tid 140580669466496] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Aug 19 18:50:30 node-1 apache2_error [Fri Aug 19 18:50:26.055287 2016] [core:notice] [pid 11277:tid 140580669466496] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 19 18:50:30 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:30 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:30 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:30 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:30 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:30 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:35 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:35 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:35 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:35 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:38 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:38 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:38 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:38 node-1 multipathd: uevent trigger error
<27>Aug 19 18:50:38 node-1 multipathd: uevent trigger error
<43>Aug 19 18:51:50 node-1 apache2_error [Fri Aug 19 18:51:47.632044 2016] [mpm_worker:notice] [pid 11277:tid 140580669466496] AH00295: caught SIGTERM, shutting down
<43>Aug 19 18:51:50 node-1 apache2_error [Fri Aug 19 18:51:48.383108 2016] [mpm_worker:notice] [pid 25309:tid 140692226459520] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 19 18:51:50 node-1 apache2_error [Fri Aug 19 18:51:48.383145 2016] [core:notice] [pid 25309:tid 140692226459520] AH00094: Command line: '/usr/sbin/apache2'
<43>Aug 19 18:52:40 node-1 apache2_error [Fri Aug 19 18:52:32.455892 2016] [mpm_worker:notice] [pid 25309:tid 140692226459520] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Aug 19 18:52:40 node-1 apache2_error [Fri Aug 19 18:52:32.651438 2016] [mpm_worker:warn] [pid 25309:tid 140692226459520] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Aug 19 18:52:40 node-1 apache2_error [Fri Aug 19 18:52:32.655392 2016] [mpm_worker:notice] [pid 25309:tid 140692226459520] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 19 18:52:40 node-1 apache2_error [Fri Aug 19 18:52:32.655405 2016] [core:notice] [pid 25309:tid 140692226459520] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 19 18:53:11 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 19 18:53:17 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:17 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:17 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:17 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:17 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:21 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:21 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:21 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:21 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:21 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:26 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:26 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:26 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:26 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:26 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:41 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:41 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:41 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:41 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:59 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:59 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:59 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:59 node-1 multipathd: uevent trigger error
<27>Aug 19 18:53:59 node-1 multipathd: uevent trigger error
<27>Aug 19 18:54:04 node-1 multipathd: uevent trigger error
<27>Aug 19 18:54:04 node-1 multipathd: uevent trigger error
<27>Aug 19 18:54:04 node-1 multipathd: uevent trigger error
<27>Aug 19 18:54:04 node-1 multipathd: uevent trigger error
<27>Aug 19 18:54:21 node-1 multipathd: uevent trigger error
<27>Aug 19 18:54:21 node-1 multipathd: uevent trigger error
<27>Aug 19 18:54:21 node-1 multipathd: uevent trigger error
<27>Aug 19 18:54:21 node-1 multipathd: uevent trigger error
<27>Aug 19 18:54:21 node-1 multipathd: uevent trigger error
<27>Aug 19 18:54:21 node-1 multipathd: uevent trigger error
<27>Aug 19 18:55:19 node-1 multipathd: uevent trigger error
<27>Aug 19 18:55:19 node-1 multipathd: uevent trigger error
<27>Aug 19 18:55:19 node-1 multipathd: uevent trigger error
<27>Aug 19 18:55:19 node-1 multipathd: uevent trigger error
<27>Aug 19 18:56:13 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 19 18:56:32 node-1 multipathd: uevent trigger error
<27>Aug 19 18:56:32 node-1 multipathd: uevent trigger error
<27>Aug 19 18:56:32 node-1 multipathd: uevent trigger error
<27>Aug 19 18:56:32 node-1 multipathd: uevent trigger error
<27>Aug 19 18:56:32 node-1 multipathd: uevent trigger error
<27>Aug 19 18:57:31 node-1 multipathd: uevent trigger error
<27>Aug 19 18:57:31 node-1 multipathd: uevent trigger error
<27>Aug 19 18:57:31 node-1 multipathd: uevent trigger error
<27>Aug 19 18:57:31 node-1 multipathd: uevent trigger error
<27>Aug 19 18:57:31 node-1 multipathd: uevent trigger error
<27>Aug 19 18:57:52 node-1 multipathd: uevent trigger error
<27>Aug 19 18:57:53 node-1 multipathd: uevent trigger error
<27>Aug 19 18:57:53 node-1 multipathd: uevent trigger error
<27>Aug 19 18:57:53 node-1 multipathd: uevent trigger error
<27>Aug 19 18:57:58 node-1 multipathd: uevent trigger error
<27>Aug 19 18:57:58 node-1 multipathd: uevent trigger error
<27>Aug 19 18:57:58 node-1 multipathd: uevent trigger error
<27>Aug 19 18:57:58 node-1 multipathd: uevent trigger error
<27>Aug 19 18:57:58 node-1 multipathd: uevent trigger error
<27>Aug 19 18:59:15 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 19 19:00:26 node-1 multipathd: uevent trigger error
<27>Aug 19 19:00:26 node-1 multipathd: uevent trigger error
<27>Aug 19 19:00:26 node-1 multipathd: uevent trigger error
<27>Aug 19 19:00:26 node-1 multipathd: uevent trigger error
<27>Aug 19 19:00:26 node-1 multipathd: uevent trigger error
<27>Aug 19 19:00:26 node-1 multipathd: uevent trigger error
<27>Aug 19 19:00:45 node-1 multipathd: uevent trigger error
<27>Aug 19 19:00:45 node-1 multipathd: uevent trigger error
<27>Aug 19 19:00:45 node-1 multipathd: uevent trigger error
<27>Aug 19 19:00:45 node-1 multipathd: uevent trigger error
<27>Aug 19 19:00:56 node-1 multipathd: uevent trigger error
<27>Aug 19 19:00:56 node-1 multipathd: uevent trigger error
<27>Aug 19 19:00:56 node-1 multipathd: uevent trigger error
<27>Aug 19 19:00:56 node-1 multipathd: uevent trigger error
<27>Aug 19 19:00:56 node-1 multipathd: uevent trigger error
<27>Aug 19 19:01:02 node-1 multipathd: uevent trigger error
<27>Aug 19 19:01:02 node-1 multipathd: uevent trigger error
<27>Aug 19 19:01:02 node-1 multipathd: uevent trigger error
<27>Aug 19 19:01:02 node-1 multipathd: uevent trigger error
<27>Aug 19 19:01:02 node-1 multipathd: uevent trigger error
<27>Aug 19 19:01:44 node-1 multipathd: uevent trigger error
<27>Aug 19 19:01:44 node-1 multipathd: uevent trigger error
<27>Aug 19 19:01:44 node-1 multipathd: uevent trigger error
<27>Aug 19 19:01:44 node-1 multipathd: uevent trigger error
<27>Aug 19 19:01:44 node-1 multipathd: uevent trigger error
<27>Aug 19 19:01:49 node-1 multipathd: uevent trigger error
<27>Aug 19 19:01:49 node-1 multipathd: uevent trigger error
<27>Aug 19 19:01:49 node-1 multipathd: uevent trigger error
<27>Aug 19 19:01:49 node-1 multipathd: uevent trigger error
<27>Aug 19 19:02:10 node-1 multipathd: uevent trigger error
<27>Aug 19 19:02:10 node-1 multipathd: uevent trigger error
<27>Aug 19 19:02:10 node-1 multipathd: uevent trigger error
<27>Aug 19 19:02:10 node-1 multipathd: uevent trigger error
<27>Aug 19 19:02:10 node-1 multipathd: uevent trigger error
<27>Aug 19 19:02:17 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 19 19:02:57 node-1 multipathd: uevent trigger error
<27>Aug 19 19:02:57 node-1 multipathd: uevent trigger error
<27>Aug 19 19:02:57 node-1 multipathd: uevent trigger error
<27>Aug 19 19:02:57 node-1 multipathd: uevent trigger error
<27>Aug 19 19:02:57 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:05 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Aug 19 19:03:05 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Aug 19 19:03:05 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Aug 19 19:03:06 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Aug 19 19:03:06 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Aug 19 19:03:07 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:07 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:07 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:07 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:07 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:07 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:20 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:20 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:20 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:20 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:34 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:34 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:34 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:34 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:52 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:52 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:53 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:53 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:53 node-1 multipathd: uevent trigger error
<27>Aug 19 19:03:53 node-1 multipathd: uevent trigger error
<27>Aug 19 19:05:19 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 19 19:06:17 node-1 multipathd: uevent trigger error
<27>Aug 19 19:06:17 node-1 multipathd: uevent trigger error
<27>Aug 19 19:06:17 node-1 multipathd: uevent trigger error
<27>Aug 19 19:06:17 node-1 multipathd: uevent trigger error
<27>Aug 19 19:06:17 node-1 multipathd: uevent trigger error
<27>Aug 19 19:06:17 node-1 multipathd: uevent trigger error
<27>Aug 19 19:06:51 node-1 multipathd: uevent trigger error
<27>Aug 19 19:06:51 node-1 multipathd: uevent trigger error
<27>Aug 19 19:06:51 node-1 multipathd: uevent trigger error
<27>Aug 19 19:06:51 node-1 multipathd: uevent trigger error
<27>Aug 19 19:06:56 node-1 multipathd: uevent trigger error
<27>Aug 19 19:06:56 node-1 multipathd: uevent trigger error
<27>Aug 19 19:06:56 node-1 multipathd: uevent trigger error
<27>Aug 19 19:06:56 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:16 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:16 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:16 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:16 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:20 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:20 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:20 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:20 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:20 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:24 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:24 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:24 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:24 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:37 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:37 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:37 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:37 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:43 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:43 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:43 node-1 multipathd: uevent trigger error
<27>Aug 19 19:07:43 node-1 multipathd: uevent trigger error
<27>Aug 19 19:08:20 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 19 19:08:29 node-1 multipathd: uevent trigger error
<27>Aug 19 19:08:29 node-1 multipathd: uevent trigger error
<27>Aug 19 19:08:29 node-1 multipathd: uevent trigger error
<27>Aug 19 19:08:29 node-1 multipathd: uevent trigger error
<27>Aug 19 19:09:39 node-1 multipathd: uevent trigger error
<27>Aug 19 19:09:39 node-1 multipathd: uevent trigger error
<27>Aug 19 19:09:39 node-1 multipathd: uevent trigger error
<27>Aug 19 19:09:39 node-1 multipathd: uevent trigger error
<27>Aug 19 19:09:58 node-1 multipathd: uevent trigger error
<27>Aug 19 19:09:58 node-1 multipathd: uevent trigger error
<27>Aug 19 19:09:58 node-1 multipathd: uevent trigger error
<27>Aug 19 19:09:58 node-1 multipathd: uevent trigger error
<27>Aug 19 19:09:58 node-1 multipathd: uevent trigger error
<11>Aug 19 19:10:12 node-1 liberasurecode[18629]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:12 node-1 liberasurecode[18629]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:12 node-1 liberasurecode[18629]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:12 node-1 liberasurecode[18629]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:12 node-1 liberasurecode[18665]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:12 node-1 liberasurecode[18665]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:12 node-1 liberasurecode[18665]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:12 node-1 liberasurecode[18665]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:14 node-1 liberasurecode[19152]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:14 node-1 liberasurecode[19152]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:14 node-1 liberasurecode[19152]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:14 node-1 liberasurecode[19152]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19777]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19777]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19777]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19777]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19818]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19818]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19818]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19818]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19862]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19862]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19862]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19862]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19926]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19926]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19926]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19926]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19940]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19940]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19940]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19940]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19952]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19952]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19952]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19952]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19964]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19964]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19964]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:20 node-1 liberasurecode[19964]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:30 node-1 liberasurecode[21911]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:30 node-1 liberasurecode[21911]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:30 node-1 liberasurecode[21911]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:10:30 node-1 liberasurecode[21911]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Aug 19 19:10:38 node-1 multipathd: uevent trigger error
<27>Aug 19 19:10:39 node-1 multipathd: uevent trigger error
<27>Aug 19 19:10:39 node-1 multipathd: uevent trigger error
<27>Aug 19 19:10:39 node-1 multipathd: uevent trigger error
<27>Aug 19 19:10:39 node-1 multipathd: uevent trigger error
<27>Aug 19 19:11:22 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Aug 19 19:11:31 node-1 apache2_error [Fri Aug 19 19:11:26.372785 2016] [mpm_worker:notice] [pid 25309:tid 140692226459520] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Aug 19 19:11:31 node-1 apache2_error [Fri Aug 19 19:11:26.757599 2016] [mpm_worker:warn] [pid 25309:tid 140692226459520] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Aug 19 19:11:31 node-1 apache2_error [Fri Aug 19 19:11:26.764604 2016] [mpm_worker:notice] [pid 25309:tid 140692226459520] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 19 19:11:31 node-1 apache2_error [Fri Aug 19 19:11:26.764648 2016] [core:notice] [pid 25309:tid 140692226459520] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 19 19:12:07 node-1 multipathd: uevent trigger error
<27>Aug 19 19:12:07 node-1 multipathd: uevent trigger error
<27>Aug 19 19:12:07 node-1 multipathd: uevent trigger error
<27>Aug 19 19:12:07 node-1 multipathd: uevent trigger error
<43>Aug 19 19:12:11 node-1 apache2_error [Fri Aug 19 19:12:03.907397 2016] [mpm_worker:notice] [pid 25309:tid 140692226459520] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Aug 19 19:12:11 node-1 apache2_error [Fri Aug 19 19:12:04.102085 2016] [mpm_worker:warn] [pid 25309:tid 140692226459520] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Aug 19 19:12:11 node-1 apache2_error [Fri Aug 19 19:12:04.111856 2016] [mpm_worker:notice] [pid 25309:tid 140692226459520] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 19 19:12:11 node-1 apache2_error [Fri Aug 19 19:12:04.111886 2016] [core:notice] [pid 25309:tid 140692226459520] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 19 19:12:15 node-1 multipathd: uevent trigger error
<27>Aug 19 19:12:15 node-1 multipathd: uevent trigger error
<27>Aug 19 19:12:15 node-1 multipathd: uevent trigger error
<27>Aug 19 19:12:15 node-1 multipathd: uevent trigger error
<43>Aug 19 19:12:51 node-1 apache2_error [Fri Aug 19 19:12:49.365179 2016] [mpm_worker:notice] [pid 25309:tid 140692226459520] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Aug 19 19:12:51 node-1 apache2_error [Fri Aug 19 19:12:50.876692 2016] [mpm_worker:warn] [pid 25309:tid 140692226459520] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Aug 19 19:12:51 node-1 apache2_error [Fri Aug 19 19:12:50.887181 2016] [mpm_worker:notice] [pid 25309:tid 140692226459520] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 19 19:12:51 node-1 apache2_error [Fri Aug 19 19:12:50.887239 2016] [core:notice] [pid 25309:tid 140692226459520] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 19 19:12:53 node-1 multipathd: uevent trigger error
<27>Aug 19 19:12:53 node-1 multipathd: uevent trigger error
<27>Aug 19 19:12:53 node-1 multipathd: uevent trigger error
<27>Aug 19 19:12:53 node-1 multipathd: uevent trigger error
<27>Aug 19 19:12:53 node-1 multipathd: uevent trigger error
<27>Aug 19 19:12:59 node-1 multipathd: uevent trigger error
<27>Aug 19 19:12:59 node-1 multipathd: uevent trigger error
<27>Aug 19 19:12:59 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:00 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:05 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:05 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:05 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:05 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:05 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:24 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:24 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:24 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:24 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:24 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:43 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:51 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:51 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:51 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:51 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:51 node-1 multipathd: uevent trigger error
<27>Aug 19 19:13:58 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Aug 19 19:14:07 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:07 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:07 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:07 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:12 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:12 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:12 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:12 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:18 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:18 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:18 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:18 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:30 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:30 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:30 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:30 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:35 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:35 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:35 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:35 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:35 node-1 multipathd: uevent trigger error
<27>Aug 19 19:14:53 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<11>Aug 19 19:15:01 node-1 liberasurecode[17111]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:15:01 node-1 liberasurecode[17111]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:15:01 node-1 liberasurecode[17111]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 19 19:15:01 node-1 liberasurecode[17111]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Aug 19 19:15:02 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:02 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:02 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:02 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:02 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:15 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:15 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:15 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:15 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:15 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:22 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:22 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:22 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:22 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:27 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:27 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:27 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:27 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:27 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:40 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:40 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:40 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:40 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:40 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:45 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:45 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:45 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:45 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:50 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:50 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:50 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:50 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:50 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:54 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:54 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:54 node-1 multipathd: uevent trigger error
<27>Aug 19 19:15:54 node-1 multipathd: uevent trigger error
