Jul 28 20:59:14 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8359" x-info="http://www.rsyslog.com"] start
Jul 28 20:59:14 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 28 20:59:14 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 28 20:59:14 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 28 20:59:14 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 28 20:59:14 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 28 20:59:14 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 28 20:59:14 node-1 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 28 20:59:14 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=16d6e46a-7615-4f2a-af39-e6bf04743009 nomdmonddf nomdmonisw
Jul 28 20:59:14 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 28 20:59:14 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 28 20:59:14 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 28 20:59:14 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 28 20:59:14 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 28 20:59:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 28 20:59:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 28 20:59:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 28 20:59:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Jul 28 20:59:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Jul 28 20:59:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Jul 28 20:59:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Jul 28 20:59:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Jul 28 20:59:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 28 20:59:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 28 20:59:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 28 20:59:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 28 20:59:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 28 20:59:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 28 20:59:14 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 28 20:59:14 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 28 20:59:14 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 28 20:59:14 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
Jul 28 20:59:14 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 28 20:59:14 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 28 20:59:14 node-1 kernel: [    0.000000] No AGP bridge found
Jul 28 20:59:14 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 28 20:59:14 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 28 20:59:14 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 28 20:59:14 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 28 20:59:14 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 28 20:59:14 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 28 20:59:14 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 28 20:59:14 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 28 20:59:14 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 28 20:59:14 node-1 kernel: [    0.000000]   2 disabled
Jul 28 20:59:14 node-1 kernel: [    0.000000]   3 disabled
Jul 28 20:59:14 node-1 kernel: [    0.000000]   4 disabled
Jul 28 20:59:14 node-1 kernel: [    0.000000]   5 disabled
Jul 28 20:59:14 node-1 kernel: [    0.000000]   6 disabled
Jul 28 20:59:14 node-1 kernel: [    0.000000]   7 disabled
Jul 28 20:59:14 node-1 kernel: [    0.000000]   8 disabled
Jul 28 20:59:14 node-1 kernel: [    0.000000]   9 disabled
Jul 28 20:59:14 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 28 20:59:14 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 28 20:59:14 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 28 20:59:14 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 28 20:59:14 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 28 20:59:14 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 28 20:59:14 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 28 20:59:14 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 28 20:59:14 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 28 20:59:14 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 28 20:59:14 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 28 20:59:14 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 28 20:59:14 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 28 20:59:14 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 28 20:59:14 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 28 20:59:14 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Jul 28 20:59:14 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 28 20:59:14 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 28 20:59:14 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 28 20:59:14 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 28 20:59:14 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 28 20:59:14 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 28 20:59:14 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 28 20:59:14 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 28 20:59:14 node-1 kernel: [    0.000000] Zone ranges:
Jul 28 20:59:14 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 28 20:59:14 node-1 kernel: [    0.000000] Early memory node ranges
Jul 28 20:59:14 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Jul 28 20:59:14 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 28 20:59:14 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 28 20:59:14 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 28 20:59:14 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Jul 28 20:59:14 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Jul 28 20:59:14 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 28 20:59:14 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 28 20:59:14 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 28 20:59:14 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 28 20:59:14 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 28 20:59:14 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 28 20:59:14 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 28 20:59:14 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 28 20:59:14 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 28 20:59:14 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 28 20:59:14 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 28 20:59:14 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 28 20:59:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 28 20:59:14 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 28 20:59:14 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 28 20:59:14 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 28 20:59:14 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 28 20:59:14 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 28 20:59:14 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 
Jul 28 20:59:14 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Jul 28 20:59:14 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 28 20:59:14 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=16d6e46a-7615-4f2a-af39-e6bf04743009 nomdmonddf nomdmonisw
Jul 28 20:59:14 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 28 20:59:14 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 28 20:59:14 node-1 kernel: [    0.000000] Checking aperture...
Jul 28 20:59:14 node-1 kernel: [    0.000000] No AGP bridge found
Jul 28 20:59:14 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 28 20:59:14 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 28 20:59:14 node-1 kernel: [    0.000000] Memory: 32653460K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Jul 28 20:59:14 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 28 20:59:14 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 28 20:59:14 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 28 20:59:14 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 28 20:59:14 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 28 20:59:14 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 28 20:59:14 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 28 20:59:14 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 28 20:59:14 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 28 20:59:14 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 28 20:59:14 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 28 20:59:14 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 28 20:59:14 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 28 20:59:14 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 28 20:59:14 node-1 kernel: [    0.004000] tsc: Detected 3492.122 MHz processor
Jul 28 20:59:14 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.24 BogoMIPS (lpj=13968488)
Jul 28 20:59:14 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 28 20:59:14 node-1 kernel: [    0.000043] Security Framework initialized
Jul 28 20:59:14 node-1 kernel: [    0.000061] AppArmor: AppArmor initialized
Jul 28 20:59:14 node-1 kernel: [    0.000063] Yama: becoming mindful.
Jul 28 20:59:14 node-1 kernel: [    0.001448] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 28 20:59:14 node-1 kernel: [    0.006314] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 28 20:59:14 node-1 kernel: [    0.008247] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 28 20:59:14 node-1 kernel: [    0.008275] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 28 20:59:14 node-1 kernel: [    0.008561] Initializing cgroup subsys memory
Jul 28 20:59:14 node-1 kernel: [    0.008568] Initializing cgroup subsys devices
Jul 28 20:59:14 node-1 kernel: [    0.008570] Initializing cgroup subsys freezer
Jul 28 20:59:14 node-1 kernel: [    0.008572] Initializing cgroup subsys blkio
Jul 28 20:59:14 node-1 kernel: [    0.008573] Initializing cgroup subsys perf_event
Jul 28 20:59:14 node-1 kernel: [    0.008575] Initializing cgroup subsys hugetlb
Jul 28 20:59:14 node-1 kernel: [    0.008595] CPU: Physical Processor ID: 0
Jul 28 20:59:14 node-1 kernel: [    0.008596] CPU: Processor Core ID: 0
Jul 28 20:59:14 node-1 kernel: [    0.008600] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 28 20:59:14 node-1 kernel: [    0.008600] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 28 20:59:14 node-1 kernel: [    0.009294] mce: CPU supports 22 MCE banks
Jul 28 20:59:14 node-1 kernel: [    0.009321] CPU0: Thermal monitoring enabled (TM1)
Jul 28 20:59:14 node-1 kernel: [    0.009342] process: using mwait in idle threads
Jul 28 20:59:14 node-1 kernel: [    0.009345] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 28 20:59:14 node-1 kernel: [    0.009345] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 28 20:59:14 node-1 kernel: [    0.009345] tlb_flushall_shift: 6
Jul 28 20:59:14 node-1 kernel: [    0.009434] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 28 20:59:14 node-1 kernel: [    0.010157] ACPI: Core revision 20131115
Jul 28 20:59:14 node-1 kernel: [    0.022822] ACPI: All ACPI Tables successfully acquired
Jul 28 20:59:14 node-1 kernel: [    0.022984] ftrace: allocating 28617 entries in 112 pages
Jul 28 20:59:14 node-1 kernel: [    0.031797] dmar: Host address width 46
Jul 28 20:59:14 node-1 kernel: [    0.031799] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 28 20:59:14 node-1 kernel: [    0.031805] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 28 20:59:14 node-1 kernel: [    0.031806] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 28 20:59:14 node-1 kernel: [    0.031810] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 28 20:59:14 node-1 kernel: [    0.031812] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 28 20:59:14 node-1 kernel: [    0.031813] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 28 20:59:14 node-1 kernel: [    0.031814] dmar: ATSR flags: 0x0
Jul 28 20:59:14 node-1 kernel: [    0.031815] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 28 20:59:14 node-1 kernel: [    0.031816] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 28 20:59:14 node-1 kernel: [    0.031932] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 28 20:59:14 node-1 kernel: [    0.031934] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 28 20:59:14 node-1 kernel: [    0.031935] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 28 20:59:14 node-1 kernel: [    0.031936] HPET id 0 under DRHD base 0xc7ffc000
Jul 28 20:59:14 node-1 kernel: [    0.031937] Your BIOS is broken and requested that x2apic be disabled.
Jul 28 20:59:14 node-1 kernel: [    0.031937] This will slightly decrease performance.
Jul 28 20:59:14 node-1 kernel: [    0.031937] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 28 20:59:14 node-1 kernel: [    0.032367] Enabled IRQ remapping in xapic mode
Jul 28 20:59:14 node-1 kernel: [    0.032368] x2apic not enabled, IRQ remapping is in xapic mode
Jul 28 20:59:14 node-1 kernel: [    0.032372] Switched APIC routing to physical flat.
Jul 28 20:59:14 node-1 kernel: [    0.032943] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 28 20:59:14 node-1 kernel: [    0.072595] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 28 20:59:14 node-1 kernel: [    0.072600] TSC deadline timer enabled
Jul 28 20:59:14 node-1 kernel: [    0.072607] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 28 20:59:14 node-1 kernel: [    0.072613] ... version:                3
Jul 28 20:59:14 node-1 kernel: [    0.072614] ... bit width:              48
Jul 28 20:59:14 node-1 kernel: [    0.072614] ... generic registers:      4
Jul 28 20:59:14 node-1 kernel: [    0.072615] ... value mask:             0000ffffffffffff
Jul 28 20:59:14 node-1 kernel: [    0.072616] ... max period:             0000ffffffffffff
Jul 28 20:59:14 node-1 kernel: [    0.072617] ... fixed-purpose events:   3
Jul 28 20:59:14 node-1 kernel: [    0.072618] ... event mask:             000000070000000f
Jul 28 20:59:14 node-1 kernel: [    0.074047] x86: Booting SMP configuration:
Jul 28 20:59:14 node-1 kernel: [    0.088153] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 28 20:59:14 node-1 kernel: [    0.074049] .... node  #0, CPUs:        #1  #2  #3
Jul 28 20:59:14 node-1 kernel: [    0.116063] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 28 20:59:14 node-1 kernel: [    0.270223] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 28 20:59:14 node-1 kernel: [    0.325837] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 28 20:59:14 node-1 kernel: [    0.382691] x86: Booted up 2 nodes, 16 CPUs
Jul 28 20:59:14 node-1 kernel: [    0.382695] smpboot: Total of 16 processors activated (111759.30 BogoMIPS)
Jul 28 20:59:14 node-1 kernel: [    0.406591] devtmpfs: initialized
Jul 28 20:59:14 node-1 kernel: [    0.409696] EVM: security.selinux
Jul 28 20:59:14 node-1 kernel: [    0.409698] EVM: security.SMACK64
Jul 28 20:59:14 node-1 kernel: [    0.409699] EVM: security.ima
Jul 28 20:59:14 node-1 kernel: [    0.409700] EVM: security.capability
Jul 28 20:59:14 node-1 kernel: [    0.409750] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Jul 28 20:59:14 node-1 kernel: [    0.410432] pinctrl core: initialized pinctrl subsystem
Jul 28 20:59:14 node-1 kernel: [    0.410494] regulator-dummy: no parameters
Jul 28 20:59:14 node-1 kernel: [    0.410525] RTC time: 20:58:37, date: 07/28/16
Jul 28 20:59:14 node-1 kernel: [    0.410559] NET: Registered protocol family 16
Jul 28 20:59:14 node-1 kernel: [    0.410645] cpuidle: using governor ladder
Jul 28 20:59:14 node-1 kernel: [    0.410646] cpuidle: using governor menu
Jul 28 20:59:14 node-1 kernel: [    0.410681] ACPI: bus type PCI registered
Jul 28 20:59:14 node-1 kernel: [    0.410683] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 28 20:59:14 node-1 kernel: [    0.410730] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 28 20:59:14 node-1 kernel: [    0.410732] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 28 20:59:14 node-1 kernel: [    0.424463] PCI: Using configuration type 1 for base access
Jul 28 20:59:14 node-1 kernel: [    0.425466] bio: create slab <bio-0> at 0
Jul 28 20:59:14 node-1 kernel: [    0.425744] ACPI: Added _OSI(Module Device)
Jul 28 20:59:14 node-1 kernel: [    0.425745] ACPI: Added _OSI(Processor Device)
Jul 28 20:59:14 node-1 kernel: [    0.425747] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 28 20:59:14 node-1 kernel: [    0.425748] ACPI: Added _OSI(Processor Aggregator Device)
Jul 28 20:59:14 node-1 kernel: [    0.438442] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 28 20:59:14 node-1 kernel: [    0.452916] ACPI: Interpreter enabled
Jul 28 20:59:14 node-1 kernel: [    0.452922] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 28 20:59:14 node-1 kernel: [    0.452926] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 28 20:59:14 node-1 kernel: [    0.452928] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 28 20:59:14 node-1 kernel: [    0.452935] ACPI: (supports S0 S4 S5)
Jul 28 20:59:14 node-1 kernel: [    0.452936] ACPI: Using IOAPIC for interrupt routing
Jul 28 20:59:14 node-1 kernel: [    0.452979] HEST: Table parsing has been initialized.
Jul 28 20:59:14 node-1 kernel: [    0.452982] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 28 20:59:14 node-1 kernel: [    0.453532] ACPI: No dock devices found.
Jul 28 20:59:14 node-1 kernel: [    0.465109] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 28 20:59:14 node-1 kernel: [    0.465114] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 20:59:14 node-1 kernel: [    0.465117] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 28 20:59:14 node-1 kernel: [    0.465144] PCI host bridge to bus 0000:ff
Jul 28 20:59:14 node-1 kernel: [    0.465146] pci_bus 0000:ff: root bus resource [bus ff]
Jul 28 20:59:14 node-1 kernel: [    0.465154] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465191] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 28 20:59:14 node-1 kernel: [    0.465221] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465256] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465285] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 28 20:59:14 node-1 kernel: [    0.465314] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 28 20:59:14 node-1 kernel: [    0.465344] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465372] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465401] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465429] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465455] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465481] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465509] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465535] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465561] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465587] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465616] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465643] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465671] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 28 20:59:14 node-1 kernel: [    0.465698] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465724] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 28 20:59:14 node-1 kernel: [    0.465749] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465775] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465805] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 28 20:59:14 node-1 kernel: [    0.465839] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465870] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465899] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465930] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465960] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.465991] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466021] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466052] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466084] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466116] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466148] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466181] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466213] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466243] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466270] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466302] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466334] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466370] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466404] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466437] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466466] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466495] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466525] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466553] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466583] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466613] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466644] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466673] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466701] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466728] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466757] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466787] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466818] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466874] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 28 20:59:14 node-1 kernel: [    0.466876] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 20:59:14 node-1 kernel: [    0.466879] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 28 20:59:14 node-1 kernel: [    0.466896] PCI host bridge to bus 0000:7f
Jul 28 20:59:14 node-1 kernel: [    0.466898] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 28 20:59:14 node-1 kernel: [    0.466903] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466930] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 28 20:59:14 node-1 kernel: [    0.466957] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.466986] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467008] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 28 20:59:14 node-1 kernel: [    0.467032] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 28 20:59:14 node-1 kernel: [    0.467057] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467083] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467106] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467129] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467151] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467173] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467196] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467218] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467246] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467275] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467296] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467321] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467345] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 28 20:59:14 node-1 kernel: [    0.467370] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467391] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 28 20:59:14 node-1 kernel: [    0.467413] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467435] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467461] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 28 20:59:14 node-1 kernel: [    0.467494] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467520] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467546] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467571] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467596] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467622] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467648] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467675] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467700] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467727] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467755] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467782] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467810] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467836] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467862] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467889] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467914] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467942] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467971] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.467999] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.468025] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.468050] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.468075] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.468104] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.468130] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.468156] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.468185] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.468210] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.468232] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.468257] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.468282] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.468312] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.468338] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.469596] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 28 20:59:14 node-1 kernel: [    0.469599] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 20:59:14 node-1 kernel: [    0.470717] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 28 20:59:14 node-1 kernel: [    0.471230] PCI host bridge to bus 0000:00
Jul 28 20:59:14 node-1 kernel: [    0.471233] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 28 20:59:14 node-1 kernel: [    0.471234] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 28 20:59:14 node-1 kernel: [    0.471235] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 28 20:59:14 node-1 kernel: [    0.471237] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 28 20:59:14 node-1 kernel: [    0.471238] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 28 20:59:14 node-1 kernel: [    0.471240] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 28 20:59:14 node-1 kernel: [    0.471241] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 28 20:59:14 node-1 kernel: [    0.471247] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 28 20:59:14 node-1 kernel: [    0.471331] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 28 20:59:14 node-1 kernel: [    0.471361] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 28 20:59:14 node-1 kernel: [    0.471403] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 28 20:59:14 node-1 kernel: [    0.471423] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 28 20:59:14 node-1 kernel: [    0.471452] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 28 20:59:14 node-1 kernel: [    0.471492] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 28 20:59:14 node-1 kernel: [    0.471511] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 28 20:59:14 node-1 kernel: [    0.471540] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 28 20:59:14 node-1 kernel: [    0.471580] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 28 20:59:14 node-1 kernel: [    0.471598] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.471669] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.471746] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.471824] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 28 20:59:14 node-1 kernel: [    0.471828] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 28 20:59:14 node-1 kernel: [    0.471914] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 28 20:59:14 node-1 kernel: [    0.472062] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 28 20:59:14 node-1 kernel: [    0.472079] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 28 20:59:14 node-1 kernel: [    0.472158] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 28 20:59:14 node-1 kernel: [    0.472213] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 28 20:59:14 node-1 kernel: [    0.472238] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 28 20:59:14 node-1 kernel: [    0.472293] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 28 20:59:14 node-1 kernel: [    0.472337] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 28 20:59:14 node-1 kernel: [    0.472365] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 28 20:59:14 node-1 kernel: [    0.472421] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 28 20:59:14 node-1 kernel: [    0.472464] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 28 20:59:14 node-1 kernel: [    0.472489] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 28 20:59:14 node-1 kernel: [    0.472506] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 28 20:59:14 node-1 kernel: [    0.472584] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 28 20:59:14 node-1 kernel: [    0.472634] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 28 20:59:14 node-1 kernel: [    0.472661] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 28 20:59:14 node-1 kernel: [    0.472909] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 28 20:59:14 node-1 kernel: [    0.472915] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 28 20:59:14 node-1 kernel: [    0.472921] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 28 20:59:14 node-1 kernel: [    0.472927] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 28 20:59:14 node-1 kernel: [    0.472934] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 28 20:59:14 node-1 kernel: [    0.472964] pci 0000:01:00.0: supports D1 D2
Jul 28 20:59:14 node-1 kernel: [    0.479237] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 28 20:59:14 node-1 kernel: [    0.479244] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 28 20:59:14 node-1 kernel: [    0.479248] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 28 20:59:14 node-1 kernel: [    0.479413] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 28 20:59:14 node-1 kernel: [    0.479446] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 28 20:59:14 node-1 kernel: [    0.487235] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 28 20:59:14 node-1 kernel: [    0.487241] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 28 20:59:14 node-1 kernel: [    0.487245] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 20:59:14 node-1 kernel: [    0.487330] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 28 20:59:14 node-1 kernel: [    0.487403] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 28 20:59:14 node-1 kernel: [    0.487493] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 28 20:59:14 node-1 kernel: [    0.487537] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 28 20:59:14 node-1 kernel: [    0.487541] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 20:59:14 node-1 kernel: [    0.487543] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 20:59:14 node-1 kernel: [    0.487594] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 28 20:59:14 node-1 kernel: [    0.487717] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 28 20:59:14 node-1 kernel: [    0.487769] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 28 20:59:14 node-1 kernel: [    0.487772] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 20:59:14 node-1 kernel: [    0.487774] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 20:59:14 node-1 kernel: [    0.487823] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 28 20:59:14 node-1 kernel: [    0.487966] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 28 20:59:14 node-1 kernel: [    0.488008] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 28 20:59:14 node-1 kernel: [    0.488127] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 28 20:59:14 node-1 kernel: [    0.488165] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 28 20:59:14 node-1 kernel: [    0.488284] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 28 20:59:14 node-1 kernel: [    0.488320] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 28 20:59:14 node-1 kernel: [    0.488441] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 28 20:59:14 node-1 kernel: [    0.488482] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 28 20:59:14 node-1 kernel: [    0.488484] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 20:59:14 node-1 kernel: [    0.488486] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 20:59:14 node-1 kernel: [    0.488545] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 28 20:59:14 node-1 kernel: [    0.488608] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 28 20:59:14 node-1 kernel: [    0.488660] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 28 20:59:14 node-1 kernel: [    0.488702] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 28 20:59:14 node-1 kernel: [    0.488784] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 28 20:59:14 node-1 kernel: [    0.488902] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 28 20:59:14 node-1 kernel: [    0.488905] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 20:59:14 node-1 kernel: [    0.488907] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 28 20:59:14 node-1 kernel: [    0.488964] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 28 20:59:14 node-1 kernel: [    0.489024] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 28 20:59:14 node-1 kernel: [    0.489072] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 28 20:59:14 node-1 kernel: [    0.489285] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 28 20:59:14 node-1 kernel: [    0.489289] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 28 20:59:14 node-1 kernel: [    0.489351] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 28 20:59:14 node-1 kernel: [    0.489404] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 28 20:59:14 node-1 kernel: [    0.489453] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 28 20:59:14 node-1 kernel: [    0.489663] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 28 20:59:14 node-1 kernel: [    0.489667] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 28 20:59:14 node-1 kernel: [    0.489725] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 28 20:59:14 node-1 kernel: [    0.489785] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 28 20:59:14 node-1 kernel: [    0.489837] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 28 20:59:14 node-1 kernel: [    0.490083] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 28 20:59:14 node-1 kernel: [    0.490086] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 28 20:59:14 node-1 kernel: [    0.490260] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 28 20:59:14 node-1 kernel: [    0.490298] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 28 20:59:14 node-1 kernel: [    0.490374] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 28 20:59:14 node-1 kernel: [    0.490393] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 28 20:59:14 node-1 kernel: [    0.490406] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 28 20:59:14 node-1 kernel: [    0.490419] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 28 20:59:14 node-1 kernel: [    0.490469] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 28 20:59:14 node-1 kernel: [    0.495235] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 28 20:59:14 node-1 kernel: [    0.495240] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 28 20:59:14 node-1 kernel: [    0.495271] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 28 20:59:14 node-1 kernel: [    0.495760] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 28 20:59:14 node-1 kernel: [    0.495763] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 20:59:14 node-1 kernel: [    0.495882] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 28 20:59:14 node-1 kernel: [    0.495988] PCI host bridge to bus 0000:80
Jul 28 20:59:14 node-1 kernel: [    0.495990] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 28 20:59:14 node-1 kernel: [    0.495992] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 28 20:59:14 node-1 kernel: [    0.495993] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 28 20:59:14 node-1 kernel: [    0.496001] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.496064] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.496131] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 28 20:59:14 node-1 kernel: [    0.496192] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 28 20:59:14 node-1 kernel: [    0.496197] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 28 20:59:14 node-1 kernel: [    0.496267] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 28 20:59:14 node-1 kernel: [    0.496580] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 28 20:59:14 node-1 kernel: [    0.496611] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 28 20:59:14 node-1 kernel: [    0.496640] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 28 20:59:14 node-1 kernel: [    0.496669] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 28 20:59:14 node-1 kernel: [    0.496698] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 20:59:14 node-1 kernel: [    0.496728] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 20:59:14 node-1 kernel: [    0.496758] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 20:59:14 node-1 kernel: [    0.496787] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 20:59:14 node-1 kernel: [    0.496872] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 28 20:59:14 node-1 kernel: [    0.496876] ACPI: \_SB_.UNC1: notify handler is installed
Jul 28 20:59:14 node-1 kernel: [    0.496877] ACPI: \_SB_.UNC0: notify handler is installed
Jul 28 20:59:14 node-1 kernel: [    0.496892] ACPI: \_SB_.PCI0: notify handler is installed
Jul 28 20:59:14 node-1 kernel: [    0.496945] ACPI: \_SB_.PCI1: notify handler is installed
Jul 28 20:59:14 node-1 kernel: [    0.497025] Found 4 acpi root devices
Jul 28 20:59:14 node-1 kernel: [    0.497132] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 28 20:59:14 node-1 kernel: [    0.497134] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 28 20:59:14 node-1 kernel: [    0.497136] vgaarb: loaded
Jul 28 20:59:14 node-1 kernel: [    0.497137] vgaarb: bridge control possible 0000:0c:00.0
Jul 28 20:59:14 node-1 kernel: [    0.497252] SCSI subsystem initialized
Jul 28 20:59:14 node-1 kernel: [    0.497323] libata version 3.00 loaded.
Jul 28 20:59:14 node-1 kernel: [    0.497338] ACPI: bus type USB registered
Jul 28 20:59:14 node-1 kernel: [    0.497348] usbcore: registered new interface driver usbfs
Jul 28 20:59:14 node-1 kernel: [    0.497353] usbcore: registered new interface driver hub
Jul 28 20:59:14 node-1 kernel: [    0.497374] usbcore: registered new device driver usb
Jul 28 20:59:14 node-1 kernel: [    0.497554] PCI: Using ACPI for IRQ routing
Jul 28 20:59:14 node-1 kernel: [    0.501172] PCI: pci_cache_line_size set to 64 bytes
Jul 28 20:59:14 node-1 kernel: [    0.501380] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 28 20:59:14 node-1 kernel: [    0.501381] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Jul 28 20:59:14 node-1 kernel: [    0.501382] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 28 20:59:14 node-1 kernel: [    0.501447] NetLabel: Initializing
Jul 28 20:59:14 node-1 kernel: [    0.501448] NetLabel:  domain hash size = 128
Jul 28 20:59:14 node-1 kernel: [    0.501449] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 28 20:59:14 node-1 kernel: [    0.501458] NetLabel:  unlabeled traffic allowed by default
Jul 28 20:59:14 node-1 kernel: [    0.501526] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 28 20:59:14 node-1 kernel: [    0.501530] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 28 20:59:14 node-1 kernel: [    0.503600] Switched to clocksource hpet
Jul 28 20:59:14 node-1 kernel: [    0.508088] AppArmor: AppArmor Filesystem Enabled
Jul 28 20:59:14 node-1 kernel: [    0.508126] pnp: PnP ACPI init
Jul 28 20:59:14 node-1 kernel: [    0.508139] ACPI: bus type PNP registered
Jul 28 20:59:14 node-1 kernel: [    0.508318] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 28 20:59:14 node-1 kernel: [    0.508329] pnp 00:01: [dma 4]
Jul 28 20:59:14 node-1 kernel: [    0.508347] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 28 20:59:14 node-1 kernel: [    0.508382] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 28 20:59:14 node-1 kernel: [    0.508406] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 28 20:59:14 node-1 kernel: [    0.508428] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 28 20:59:14 node-1 kernel: [    0.508474] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 28 20:59:14 node-1 kernel: [    0.508589] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 28 20:59:14 node-1 kernel: [    0.508592] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 28 20:59:14 node-1 kernel: [    0.508593] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 28 20:59:14 node-1 kernel: [    0.508595] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 28 20:59:14 node-1 kernel: [    0.508597] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 28 20:59:14 node-1 kernel: [    0.508598] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 28 20:59:14 node-1 kernel: [    0.508601] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 28 20:59:14 node-1 kernel: [    0.508603] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 28 20:59:14 node-1 kernel: [    0.508605] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 28 20:59:14 node-1 kernel: [    0.508606] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 28 20:59:14 node-1 kernel: [    0.508608] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 28 20:59:14 node-1 kernel: [    0.508609] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 28 20:59:14 node-1 kernel: [    0.508611] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 28 20:59:14 node-1 kernel: [    0.508613] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 28 20:59:14 node-1 kernel: [    0.508715] pnp 00:07: [dma 0 disabled]
Jul 28 20:59:14 node-1 kernel: [    0.508748] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 28 20:59:14 node-1 kernel: [    0.508829] pnp 00:08: [dma 0 disabled]
Jul 28 20:59:14 node-1 kernel: [    0.508864] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 28 20:59:14 node-1 kernel: [    0.508921] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 28 20:59:14 node-1 kernel: [    0.509367] pnp: PnP ACPI: found 10 devices
Jul 28 20:59:14 node-1 kernel: [    0.509369] ACPI: bus type PNP unregistered
Jul 28 20:59:14 node-1 kernel: [    0.515337] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 28 20:59:14 node-1 kernel: [    0.515341] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 28 20:59:14 node-1 kernel: [    0.515344] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 28 20:59:14 node-1 kernel: [    0.515349] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 28 20:59:14 node-1 kernel: [    0.515351] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 20:59:14 node-1 kernel: [    0.515366] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 28 20:59:14 node-1 kernel: [    0.515396] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 28 20:59:14 node-1 kernel: [    0.515410] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 28 20:59:14 node-1 kernel: [    0.515439] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 28 20:59:14 node-1 kernel: [    0.515454] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 28 20:59:14 node-1 kernel: [    0.515483] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 28 20:59:14 node-1 kernel: [    0.515497] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 28 20:59:14 node-1 kernel: [    0.515526] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 28 20:59:14 node-1 kernel: [    0.515528] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 20:59:14 node-1 kernel: [    0.515543] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 20:59:14 node-1 kernel: [    0.515572] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 28 20:59:14 node-1 kernel: [    0.515579] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 20:59:14 node-1 kernel: [    0.515593] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 20:59:14 node-1 kernel: [    0.515625] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 28 20:59:14 node-1 kernel: [    0.515627] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 20:59:14 node-1 kernel: [    0.515630] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 20:59:14 node-1 kernel: [    0.515635] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 28 20:59:14 node-1 kernel: [    0.515636] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 28 20:59:14 node-1 kernel: [    0.515639] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 20:59:14 node-1 kernel: [    0.515644] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 28 20:59:14 node-1 kernel: [    0.515650] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 28 20:59:14 node-1 kernel: [    0.515659] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 28 20:59:14 node-1 kernel: [    0.515662] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 28 20:59:14 node-1 kernel: [    0.515670] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 28 20:59:14 node-1 kernel: [    0.515671] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 28 20:59:14 node-1 kernel: [    0.515672] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 28 20:59:14 node-1 kernel: [    0.515672] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 28 20:59:14 node-1 kernel: [    0.515673] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 28 20:59:14 node-1 kernel: [    0.515674] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 28 20:59:14 node-1 kernel: [    0.515675] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 28 20:59:14 node-1 kernel: [    0.515676] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 28 20:59:14 node-1 kernel: [    0.515677] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 28 20:59:14 node-1 kernel: [    0.515678] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 28 20:59:14 node-1 kernel: [    0.515679] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 28 20:59:14 node-1 kernel: [    0.515680] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 28 20:59:14 node-1 kernel: [    0.515681] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 28 20:59:14 node-1 kernel: [    0.515682] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 28 20:59:14 node-1 kernel: [    0.515683] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 28 20:59:14 node-1 kernel: [    0.515684] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 28 20:59:14 node-1 kernel: [    0.515685] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 28 20:59:14 node-1 kernel: [    0.515686] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 28 20:59:14 node-1 kernel: [    0.515687] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 28 20:59:14 node-1 kernel: [    0.515688] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 28 20:59:14 node-1 kernel: [    0.515690] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 28 20:59:14 node-1 kernel: [    0.515691] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 28 20:59:14 node-1 kernel: [    0.515693] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 28 20:59:14 node-1 kernel: [    0.515694] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 28 20:59:14 node-1 kernel: [    0.515734] NET: Registered protocol family 2
Jul 28 20:59:14 node-1 kernel: [    0.516029] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 28 20:59:14 node-1 kernel: [    0.516398] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 28 20:59:14 node-1 kernel: [    0.516567] TCP: Hash tables configured (established 262144 bind 65536)
Jul 28 20:59:14 node-1 kernel: [    0.516613] TCP: reno registered
Jul 28 20:59:14 node-1 kernel: [    0.516644] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 28 20:59:14 node-1 kernel: [    0.516761] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 28 20:59:14 node-1 kernel: [    0.516921] NET: Registered protocol family 1
Jul 28 20:59:14 node-1 kernel: [    0.555689] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 28 20:59:14 node-1 kernel: [    0.555697] PCI: CLS 64 bytes, default 64
Jul 28 20:59:14 node-1 kernel: [    0.555743] Trying to unpack rootfs image as initramfs...
Jul 28 20:59:14 node-1 kernel: [    0.777428] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Jul 28 20:59:14 node-1 kernel: [    0.777479] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 28 20:59:14 node-1 kernel: [    0.777482] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Jul 28 20:59:14 node-1 kernel: [    0.777927] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 20:59:14 node-1 kernel: [    0.777942] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 20:59:14 node-1 kernel: [    0.777956] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 20:59:14 node-1 kernel: [    0.777969] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 20:59:14 node-1 kernel: [    0.777981] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 20:59:14 node-1 kernel: [    0.777990] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 20:59:14 node-1 kernel: [    0.777996] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 20:59:14 node-1 kernel: [    0.778001] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 20:59:14 node-1 kernel: [    0.778009] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 20:59:14 node-1 kernel: [    0.778021] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 20:59:14 node-1 kernel: [    0.778037] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 20:59:14 node-1 kernel: [    0.778050] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 20:59:14 node-1 kernel: [    0.778060] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 20:59:14 node-1 kernel: [    0.778067] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 20:59:14 node-1 kernel: [    0.778073] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 20:59:14 node-1 kernel: [    0.778079] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 20:59:14 node-1 kernel: [    0.778128] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 28 20:59:14 node-1 kernel: [    0.778130] Scanning for low memory corruption every 60 seconds
Jul 28 20:59:14 node-1 kernel: [    0.778453] Initialise system trusted keyring
Jul 28 20:59:14 node-1 kernel: [    0.778500] audit: initializing netlink socket (disabled)
Jul 28 20:59:14 node-1 kernel: [    0.778510] type=2000 audit(1469739517.732:1): initialized
Jul 28 20:59:14 node-1 kernel: [    0.796415] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 28 20:59:14 node-1 kernel: [    0.797875] zbud: loaded
Jul 28 20:59:14 node-1 kernel: [    0.798003] VFS: Disk quotas dquot_6.5.2
Jul 28 20:59:14 node-1 kernel: [    0.798042] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 28 20:59:14 node-1 kernel: [    0.798398] fuse init (API version 7.22)
Jul 28 20:59:14 node-1 kernel: [    0.798456] msgmni has been set to 32768
Jul 28 20:59:14 node-1 kernel: [    0.798502] Key type big_key registered
Jul 28 20:59:14 node-1 kernel: [    0.799047] Key type asymmetric registered
Jul 28 20:59:14 node-1 kernel: [    0.799049] Asymmetric key parser 'x509' registered
Jul 28 20:59:14 node-1 kernel: [    0.799072] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 28 20:59:14 node-1 kernel: [    0.799142] io scheduler noop registered
Jul 28 20:59:14 node-1 kernel: [    0.799143] io scheduler deadline registered (default)
Jul 28 20:59:14 node-1 kernel: [    0.799161] io scheduler cfq registered
Jul 28 20:59:14 node-1 kernel: [    0.799737] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    0.799867] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    0.799982] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    0.800106] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    0.800218] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    0.800309] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    0.800699] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 28 20:59:14 node-1 kernel: [    0.800725] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 28 20:59:14 node-1 kernel: [    0.800742] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 28 20:59:14 node-1 kernel: [    0.800755] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800757] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800760] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 28 20:59:14 node-1 kernel: [    0.800765] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800767] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800768] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800770] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800772] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800774] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800775] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800777] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800778] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800780] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800781] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800783] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800786] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 28 20:59:14 node-1 kernel: [    0.800800] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800802] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 28 20:59:14 node-1 kernel: [    0.800813] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800816] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 28 20:59:14 node-1 kernel: [    0.800828] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800830] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 28 20:59:14 node-1 kernel: [    0.800833] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 28 20:59:14 node-1 kernel: [    0.800887] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 28 20:59:14 node-1 kernel: [    0.800892] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 28 20:59:14 node-1 kernel: [    0.800896] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 28 20:59:14 node-1 kernel: [    0.800905] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 28 20:59:14 node-1 kernel: [    0.800942] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 28 20:59:14 node-1 kernel: [    0.800944] vesafb: scrolling: redraw
Jul 28 20:59:14 node-1 kernel: [    0.800945] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 28 20:59:14 node-1 kernel: [    0.820141] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 28 20:59:14 node-1 kernel: [    0.828625] Console: switching to colour frame buffer device 80x30
Jul 28 20:59:14 node-1 kernel: [    0.837292] fb0: VESA VGA frame buffer device
Jul 28 20:59:14 node-1 kernel: [    0.837491] intel_idle: MWAIT substates: 0x2120
Jul 28 20:59:14 node-1 kernel: [    0.837492] intel_idle: v0.4 model 0x3F
Jul 28 20:59:14 node-1 kernel: [    0.837493] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 28 20:59:14 node-1 kernel: [    0.837720] ipmi message handler version 39.2
Jul 28 20:59:14 node-1 kernel: [    0.837992] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 28 20:59:14 node-1 kernel: [    0.838425] ACPI: AC Adapter [P111] (on-line)
Jul 28 20:59:14 node-1 kernel: [    0.843665] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 28 20:59:14 node-1 kernel: [    0.854674] ACPI: Power Button [PWRB]
Jul 28 20:59:14 node-1 kernel: [    0.860469] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 28 20:59:14 node-1 kernel: [    0.872123] ACPI: Power Button [PWRF]
Jul 28 20:59:14 node-1 kernel: [    0.889045] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 28 20:59:14 node-1 kernel: [    0.900772] pstore: Registered erst as persistent store backend
Jul 28 20:59:14 node-1 kernel: [    0.906979] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 28 20:59:14 node-1 kernel: [    0.918981] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 28 20:59:14 node-1 kernel: [    0.945741] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 28 20:59:14 node-1 kernel: [    0.979198] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 28 20:59:14 node-1 kernel: [    0.993258] Linux agpgart interface v0.103
Jul 28 20:59:14 node-1 kernel: [    1.000944] brd: module loaded
Jul 28 20:59:14 node-1 kernel: [    1.007976] loop: module loaded
Jul 28 20:59:14 node-1 kernel: [    1.014671] libphy: Fixed MDIO Bus: probed
Jul 28 20:59:14 node-1 kernel: [    1.021131] tun: Universal TUN/TAP device driver, 1.6
Jul 28 20:59:14 node-1 kernel: [    1.027574] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 28 20:59:14 node-1 kernel: [    1.034088] PPP generic driver version 2.4.2
Jul 28 20:59:14 node-1 kernel: [    1.040470] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 28 20:59:14 node-1 kernel: [    1.046886] ehci-pci: EHCI PCI platform driver
Jul 28 20:59:14 node-1 kernel: [    1.053385] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 28 20:59:14 node-1 kernel: [    1.059765] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 28 20:59:14 node-1 kernel: [    1.072268] ehci-pci 0000:00:1a.0: debug port 2
Jul 28 20:59:14 node-1 kernel: [    1.082438] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 28 20:59:14 node-1 kernel: [    1.082456] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 28 20:59:14 node-1 kernel: [    1.099089] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 28 20:59:14 node-1 kernel: [    1.105136] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 28 20:59:14 node-1 kernel: [    1.111291] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 28 20:59:14 node-1 kernel: [    1.123270] usb usb1: Product: EHCI Host Controller
Jul 28 20:59:14 node-1 kernel: [    1.129282] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 28 20:59:14 node-1 kernel: [    1.135296] usb usb1: SerialNumber: 0000:00:1a.0
Jul 28 20:59:14 node-1 kernel: [    1.141226] hub 1-0:1.0: USB hub found
Jul 28 20:59:14 node-1 kernel: [    1.146973] hub 1-0:1.0: 2 ports detected
Jul 28 20:59:14 node-1 kernel: [    1.152757] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 28 20:59:14 node-1 kernel: [    1.158319] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 28 20:59:14 node-1 kernel: [    1.169195] ehci-pci 0000:00:1d.0: debug port 2
Jul 28 20:59:14 node-1 kernel: [    1.178486] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 28 20:59:14 node-1 kernel: [    1.178489] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 28 20:59:14 node-1 kernel: [    1.195007] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 28 20:59:14 node-1 kernel: [    1.200198] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 28 20:59:14 node-1 kernel: [    1.205493] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 28 20:59:14 node-1 kernel: [    1.216049] usb usb2: Product: EHCI Host Controller
Jul 28 20:59:14 node-1 kernel: [    1.221516] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 28 20:59:14 node-1 kernel: [    1.227062] usb usb2: SerialNumber: 0000:00:1d.0
Jul 28 20:59:14 node-1 kernel: [    1.232572] hub 2-0:1.0: USB hub found
Jul 28 20:59:14 node-1 kernel: [    1.237925] hub 2-0:1.0: 2 ports detected
Jul 28 20:59:14 node-1 kernel: [    1.243219] ehci-platform: EHCI generic platform driver
Jul 28 20:59:14 node-1 kernel: [    1.248445] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 28 20:59:14 node-1 kernel: [    1.253756] ohci-pci: OHCI PCI platform driver
Jul 28 20:59:14 node-1 kernel: [    1.259064] ohci-platform: OHCI generic platform driver
Jul 28 20:59:14 node-1 kernel: [    1.264262] uhci_hcd: USB Universal Host Controller Interface driver
Jul 28 20:59:14 node-1 kernel: [    1.269609] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 28 20:59:14 node-1 kernel: [    1.462787] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 28 20:59:14 node-1 kernel: [    1.774571] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 28 20:59:14 node-1 kernel: [    1.790833] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 28 20:59:14 node-1 kernel: [    1.796440] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 28 20:59:14 node-1 kernel: [    1.802226] hub 1-1:1.0: USB hub found
Jul 28 20:59:14 node-1 kernel: [    1.807820] hub 1-1:1.0: 6 ports detected
Jul 28 20:59:14 node-1 kernel: [    1.922418] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 28 20:59:14 node-1 kernel: [    2.309120] i8042: No controller found
Jul 28 20:59:14 node-1 kernel: [    2.314684] mousedev: PS/2 mouse device common for all mice
Jul 28 20:59:14 node-1 kernel: [    2.320436] rtc_cmos 00:02: RTC can wake from S4
Jul 28 20:59:14 node-1 kernel: [    2.322819] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 28 20:59:14 node-1 kernel: [    2.322820] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 28 20:59:14 node-1 kernel: [    2.323334] hub 2-1:1.0: USB hub found
Jul 28 20:59:14 node-1 kernel: [    2.323568] hub 2-1:1.0: 8 ports detected
Jul 28 20:59:14 node-1 kernel: [    2.348948] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 28 20:59:14 node-1 kernel: [    2.354787] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 28 20:59:14 node-1 kernel: [    2.366238] device-mapper: uevent: version 1.0.3
Jul 28 20:59:14 node-1 kernel: [    2.371955] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 28 20:59:14 node-1 kernel: [    2.383367] ledtrig-cpu: registered to indicate activity on CPUs
Jul 28 20:59:14 node-1 kernel: [    2.389349] TCP: cubic registered
Jul 28 20:59:14 node-1 kernel: [    2.395240] NET: Registered protocol family 10
Jul 28 20:59:14 node-1 kernel: [    2.401322] NET: Registered protocol family 17
Jul 28 20:59:14 node-1 kernel: [    2.407113] Key type dns_resolver registered
Jul 28 20:59:14 node-1 kernel: [    2.413205] Loading compiled-in X.509 certificates
Jul 28 20:59:14 node-1 kernel: [    2.419433] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 28 20:59:14 node-1 kernel: [    2.431092] registered taskstats version 1
Jul 28 20:59:14 node-1 kernel: [    2.439181] Key type trusted registered
Jul 28 20:59:14 node-1 kernel: [    2.446881] Key type encrypted registered
Jul 28 20:59:14 node-1 kernel: [    2.452394] AppArmor: AppArmor sha1 policy hashing enabled
Jul 28 20:59:14 node-1 kernel: [    2.457913] IMA: No TPM chip found, activating TPM-bypass!
Jul 28 20:59:14 node-1 kernel: [    2.464043] regulator-dummy: disabling
Jul 28 20:59:14 node-1 kernel: [    2.469545]   Magic number: 8:675:1004
Jul 28 20:59:14 node-1 kernel: [    2.475024] input input1: hash matches
Jul 28 20:59:14 node-1 kernel: [    2.480425] system 00:06: hash matches
Jul 28 20:59:14 node-1 kernel: [    2.485851] memory memory43: hash matches
Jul 28 20:59:14 node-1 kernel: [    2.491106] rtc_cmos 00:02: setting system clock to 2016-07-28 20:58:39 UTC (1469739519)
Jul 28 20:59:14 node-1 kernel: [    2.503053] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 28 20:59:14 node-1 kernel: [    2.508523] EDD information not available.
Jul 28 20:59:14 node-1 kernel: [    2.513904] PM: Hibernation image not present or could not be loaded.
Jul 28 20:59:14 node-1 kernel: [    2.514770] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 28 20:59:14 node-1 kernel: [    2.525801] Write protecting the kernel read-only data: 12288k
Jul 28 20:59:14 node-1 kernel: [    2.531935] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 28 20:59:14 node-1 kernel: [    2.544234] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 28 20:59:14 node-1 kernel: [    2.575537] device-mapper: multipath: version 1.6.0 loaded
Jul 28 20:59:14 node-1 kernel: [    2.583221] systemd-udevd[216]: starting version 204
Jul 28 20:59:14 node-1 kernel: [    2.604357] md: linear personality registered for level -1
Jul 28 20:59:14 node-1 kernel: [    2.606121] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 28 20:59:14 node-1 kernel: [    2.624664] md: multipath personality registered for level -4
Jul 28 20:59:14 node-1 kernel: [    2.632623] md: raid0 personality registered for level 0
Jul 28 20:59:14 node-1 kernel: [    2.640994] md: raid1 personality registered for level 1
Jul 28 20:59:14 node-1 kernel: [    2.647074] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 28 20:59:14 node-1 kernel: [    2.647075] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 28 20:59:14 node-1 kernel: [    2.655826] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Jul 28 20:59:14 node-1 kernel: [    2.655828] 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
Jul 28 20:59:14 node-1 kernel: [    2.655829] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 20:59:14 node-1 kernel: [    2.655894] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.655932] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.655970] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.656009] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.656094] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.666976] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Jul 28 20:59:14 node-1 kernel: [    2.666977] 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
Jul 28 20:59:14 node-1 kernel: [    2.666978] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 20:59:14 node-1 kernel: [    2.667039] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.667074] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.667112] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.667139] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.667220] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.676119] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Jul 28 20:59:14 node-1 kernel: [    2.676121] 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
Jul 28 20:59:14 node-1 kernel: [    2.676122] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 20:59:14 node-1 kernel: [    2.676170] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.676204] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.676242] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.676282] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.676363] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.686660] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Jul 28 20:59:14 node-1 kernel: [    2.686661] 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
Jul 28 20:59:14 node-1 kernel: [    2.686662] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 20:59:14 node-1 kernel: [    2.686722] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.686759] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.686797] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.686833] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.686919] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.742474] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 28 20:59:14 node-1 kernel: [    2.742475] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 28 20:59:14 node-1 kernel: [    2.742475] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 28 20:59:14 node-1 kernel: [    2.742476] usb 2-1.4: Manufacturer: Avocent
Jul 28 20:59:14 node-1 kernel: [    2.742477] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 28 20:59:14 node-1 kernel: [    2.889603] Switched to clocksource tsc
Jul 28 20:59:14 node-1 kernel: [    2.889755] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 28 20:59:14 node-1 kernel: [    2.889835] megasas: FW now in Ready state
Jul 28 20:59:14 node-1 kernel: [    2.889887] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.889929] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.889962] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.889977] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.890008] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.890045] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.890078] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.890116] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.890162] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.890210] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.890240] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.890275] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.890299] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.890335] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.890372] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.890388] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Jul 28 20:59:14 node-1 kernel: [    2.890552] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 28 20:59:14 node-1 kernel: [    2.934831] hidraw: raw HID events driver (C) Jiri Kosina
Jul 28 20:59:14 node-1 kernel: [    2.944399] usbcore: registered new interface driver usbhid
Jul 28 20:59:14 node-1 kernel: [    2.950904] usbhid: USB HID core driver
Jul 28 20:59:14 node-1 kernel: [    2.958327] 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
Jul 28 20:59:14 node-1 kernel: [    2.971683] 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
Jul 28 20:59:14 node-1 kernel: [    2.985169] 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
Jul 28 20:59:14 node-1 kernel: [    2.989628] raid6: sse2x1    3939 MB/s
Jul 28 20:59:14 node-1 kernel: [    3.005320] 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
Jul 28 20:59:14 node-1 kernel: [    3.019099] 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
Jul 28 20:59:14 node-1 kernel: [    3.032833] 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
Jul 28 20:59:14 node-1 kernel: [    3.057419] raid6: sse2x2    3154 MB/s
Jul 28 20:59:14 node-1 kernel: [    3.129358] raid6: sse2x4   16938 MB/s
Jul 28 20:59:14 node-1 kernel: [    3.201295] raid6: avx2x1   22369 MB/s
Jul 28 20:59:14 node-1 kernel: [    3.273234] raid6: avx2x2   26873 MB/s
Jul 28 20:59:14 node-1 kernel: [    3.301212] megasas:IOC Init cmd success
Jul 28 20:59:14 node-1 kernel: [    3.345173] raid6: avx2x4   27375 MB/s
Jul 28 20:59:14 node-1 kernel: [    3.351461] raid6: using algorithm avx2x4 (27375 MB/s)
Jul 28 20:59:14 node-1 kernel: [    3.353527] megasas: INIT adapter done
Jul 28 20:59:14 node-1 kernel: [    3.364147] raid6: using avx2x2 recovery algorithm
Jul 28 20:59:14 node-1 kernel: [    3.371288] xor: automatically using best checksumming function:
Jul 28 20:59:14 node-1 kernel: [    3.417112]    avx       : 35726.000 MB/sec
Jul 28 20:59:14 node-1 kernel: [    3.424063] async_tx: api initialized (async)
Jul 28 20:59:14 node-1 kernel: [    3.425270] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 28 20:59:14 node-1 kernel: [    3.427241] scsi0 : LSI SAS based MegaRAID driver
Jul 28 20:59:14 node-1 kernel: [    3.434775] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 28 20:59:14 node-1 kernel: [    3.458906] md: raid6 personality registered for level 6
Jul 28 20:59:14 node-1 kernel: [    3.465135] md: raid5 personality registered for level 5
Jul 28 20:59:14 node-1 kernel: [    3.467904] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 28 20:59:14 node-1 kernel: [    3.482829] md: raid4 personality registered for level 4
Jul 28 20:59:14 node-1 kernel: [    3.490061] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 28 20:59:14 node-1 kernel: [    3.495829] md: raid10 personality registered for level 10
Jul 28 20:59:14 node-1 kernel: [    3.495858] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 28 20:59:14 node-1 kernel: [    3.496175] sd 0:2:0:0: [sda] Write Protect is off
Jul 28 20:59:14 node-1 kernel: [    3.496176] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 28 20:59:14 node-1 kernel: [    3.496223] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 28 20:59:14 node-1 kernel: [    3.518916]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 28 20:59:14 node-1 kernel: [    3.520780] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 28 20:59:14 node-1 kernel: [    3.583933] multipathd (359): /proc/359/oom_adj is deprecated, please use /proc/359/oom_score_adj instead.
Jul 28 20:59:14 node-1 kernel: [    3.665144] random: lvm urandom read with 27 bits of entropy available
Jul 28 20:59:14 node-1 kernel: [    3.916354] bio: create slab <bio-1> at 1
Jul 28 20:59:14 node-1 kernel: [    4.612334] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 20:59:14 node-1 kernel: [    5.409195] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 28 20:59:14 node-1 kernel: [    5.441611] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 28 20:59:14 node-1 kernel: [    5.526254] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 28 20:59:14 node-1 kernel: [    5.539467] random: nonblocking pool is initialized
Jul 28 20:59:14 node-1 kernel: [    5.628029] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 28 20:59:14 node-1 kernel: [    5.715217] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 20:59:14 node-1 kernel: [    5.926999] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 28 20:59:14 node-1 kernel: [    5.974139] XFS (dm-0): Mounting Filesystem
Jul 28 20:59:14 node-1 kernel: [    6.108810] XFS (dm-0): Ending clean mount
Jul 28 20:59:14 node-1 kernel: [    6.158250] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 20:59:14 node-1 kernel: [    6.183580] XFS (dm-1): Mounting Filesystem
Jul 28 20:59:14 node-1 kernel: [    6.400308] XFS (dm-1): Ending clean mount
Jul 28 20:59:14 node-1 kernel: [    8.358885] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 28 20:59:14 node-1 kernel: [    8.372518] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 28 20:59:14 node-1 kernel: [    8.531430] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 28 20:59:14 node-1 kernel: [    8.531435] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 28 20:59:14 node-1 kernel: [    8.531439] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 28 20:59:14 node-1 kernel: [    8.531442] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 28 20:59:14 node-1 kernel: [    8.579130] systemd-udevd[771]: starting version 204
Jul 28 20:59:14 node-1 kernel: [    8.874786] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 28 20:59:14 node-1 kernel: [    8.874793] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 20:59:14 node-1 kernel: [    8.874797] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 28 20:59:14 node-1 kernel: [    8.874799] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 20:59:14 node-1 kernel: [    8.874853] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 28 20:59:14 node-1 kernel: [    8.881288] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 28 20:59:14 node-1 kernel: [    8.883924] IPMI System Interface driver.
Jul 28 20:59:14 node-1 kernel: [    8.883965] ipmi_si: probing via ACPI
Jul 28 20:59:14 node-1 kernel: [    8.883983] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 28 20:59:14 node-1 kernel: [    8.883984] ipmi_si: Adding ACPI-specified kcs state machine
Jul 28 20:59:14 node-1 kernel: [    8.883996] ipmi_si: probing via SMBIOS
Jul 28 20:59:14 node-1 kernel: [    8.883997] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 28 20:59:14 node-1 kernel: [    8.883998] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 28 20:59:14 node-1 kernel: [    8.884000] ipmi_si: probing via SPMI
Jul 28 20:59:14 node-1 kernel: [    8.884001] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 28 20:59:14 node-1 kernel: [    8.884002] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 28 20:59:14 node-1 kernel: [    8.884004] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 28 20:59:14 node-1 kernel: [    8.889431] power_meter ACPI000D:00: Found ACPI power meter.
Jul 28 20:59:14 node-1 kernel: [    8.889464] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 28 20:59:14 node-1 kernel: [    8.899734] wmi: Mapper loaded
Jul 28 20:59:14 node-1 kernel: [    8.948938] systemd-udevd[792]: renamed network interface eth1 to enp7s0
Jul 28 20:59:14 node-1 kernel: [    8.972851] systemd-udevd[794]: renamed network interface eth2 to enp8s0
Jul 28 20:59:14 node-1 kernel: [    9.004825] systemd-udevd[789]: renamed network interface eth0 to enp6s0
Jul 28 20:59:14 node-1 kernel: [    9.016682] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 28 20:59:14 node-1 kernel: [    9.016697] ipmi_si 00:09: IPMI kcs interface initialized
Jul 28 20:59:14 node-1 kernel: [    9.042886] systemd-udevd[790]: renamed network interface eth3 to enp9s0
Jul 28 20:59:14 node-1 kernel: [    9.402658] type=1400 audit(1469739526.412:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1040 comm="apparmor_parser"
Jul 28 20:59:14 node-1 kernel: [    9.402819] type=1400 audit(1469739526.412:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1040 comm="apparmor_parser"
Jul 28 20:59:14 node-1 kernel: [    9.402947] type=1400 audit(1469739526.412:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1040 comm="apparmor_parser"
Jul 28 20:59:14 node-1 kernel: [    9.413658] type=1400 audit(1469739526.424:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1038 comm="apparmor_parser"
Jul 28 20:59:14 node-1 kernel: [    9.413801] type=1400 audit(1469739526.424:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1038 comm="apparmor_parser"
Jul 28 20:59:14 node-1 kernel: [    9.413923] type=1400 audit(1469739526.424:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1038 comm="apparmor_parser"
Jul 28 20:59:14 node-1 kernel: [    9.414105] type=1400 audit(1469739526.424:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1037 comm="apparmor_parser"
Jul 28 20:59:14 node-1 kernel: [    9.414248] type=1400 audit(1469739526.424:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1037 comm="apparmor_parser"
Jul 28 20:59:14 node-1 kernel: [    9.414386] type=1400 audit(1469739526.424:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1037 comm="apparmor_parser"
Jul 28 20:59:14 node-1 kernel: [    9.419423] type=1400 audit(1469739526.428:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1041 comm="apparmor_parser"
Jul 28 20:59:14 node-1 kernel: [   10.122419] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 28 20:59:14 node-1 kernel: [   10.123434] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 28 20:59:14 node-1 kernel: [   10.318430] enic 0000:06:00.0 enp6s0: Link UP
Jul 28 20:59:14 node-1 kernel: [   10.318953] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 28 20:59:14 node-1 kernel: [   10.318962] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 28 20:59:14 node-1 kernel: [   20.073630] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 28 20:59:14 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 28 20:59:15 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 28 20:59:16 node-1 kernel: [   38.654878] init: failsafe main process (8386) killed by TERM signal
Jul 28 20:59:16 node-1 dbus[8426]: [system] AppArmor D-Bus mediation is enabled
Jul 28 20:59:16 node-1 kernel: [   38.836752] audit_printk_skb: 30 callbacks suppressed
Jul 28 20:59:16 node-1 kernel: [   38.836753] type=1400 audit(1469739556.301:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8512 comm="apparmor_parser"
Jul 28 20:59:16 node-1 kernel: [   38.836883] type=1400 audit(1469739556.301:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8511 comm="apparmor_parser"
Jul 28 20:59:16 node-1 kernel: [   38.836887] type=1400 audit(1469739556.301:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8511 comm="apparmor_parser"
Jul 28 20:59:16 node-1 kernel: [   38.836889] type=1400 audit(1469739556.301:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8511 comm="apparmor_parser"
Jul 28 20:59:16 node-1 kernel: [   38.837109] type=1400 audit(1469739556.301:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8511 comm="apparmor_parser"
Jul 28 20:59:16 node-1 kernel: [   38.837110] type=1400 audit(1469739556.301:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8511 comm="apparmor_parser"
Jul 28 20:59:16 node-1 kernel: [   38.837226] type=1400 audit(1469739556.301:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8511 comm="apparmor_parser"
Jul 28 20:59:16 node-1 kernel: [   38.918644] type=1400 audit(1469739556.381:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8514 comm="apparmor_parser"
Jul 28 20:59:16 node-1 anacron[8578]: Anacron 2.3 started on 2016-07-28
Jul 28 20:59:16 node-1 cron[8544]: (CRON) INFO (pidfile fd = 3)
Jul 28 20:59:16 node-1 cron[8582]: (CRON) STARTUP (fork ok)
Jul 28 20:59:16 node-1 anacron[8578]: Will run job `cron.daily' in 5 min.
Jul 28 20:59:16 node-1 anacron[8578]: Will run job `cron.weekly' in 10 min.
Jul 28 20:59:16 node-1 anacron[8578]: Will run job `cron.monthly' in 15 min.
Jul 28 20:59:16 node-1 anacron[8578]: Jobs will be executed sequentially
Jul 28 20:59:16 node-1 cron[8582]: (CRON) INFO (Running @reboot jobs)
Jul 28 20:59:16 node-1 multipathd: path checkers start up
Jul 28 20:59:17 node-1 postfix/master[8724]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 28 20:59:20 node-1 puppet-agent[8908]: Reopening log files
Jul 28 20:59:20 node-1 puppet-agent[8908]: Could not request certificate: Connection refused - connect(2)
Jul 28 20:59:34 node-1 puppet-user[9116]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 28 20:59:34 node-1 puppet-user[9116]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 28 20:59:35 node-1 puppet-user[9116]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 28 20:59:35 node-1 puppet-user[9116]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 28 20:59:35 node-1 puppet-user[9116]: Finished catalog run in 1.03 seconds
Jul 28 20:59:37 node-1 multipathd: uevent trigger error
Jul 28 20:59:37 node-1 puppet-user[9546]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 28 20:59:37 node-1 puppet-user[9546]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Jul 28 20:59:37 node-1 puppet-user[9546]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 28 20:59:37 node-1 puppet-user[9546]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 28 20:59:37 node-1 puppet-user[9546]: (/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"]'
Jul 28 20:59:37 node-1 puppet-user[9546]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 28 20:59:37 node-1 puppet-user[9546]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 28 20:59:37 node-1 puppet-user[9546]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 28 20:59:37 node-1 puppet-user[9546]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 28 20:59:37 node-1 puppet-user[9546]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 28 20:59:37 node-1 puppet-user[9546]: Finished catalog run in 0.06 seconds
Jul 28 20:59:38 node-1 puppet-user[10191]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 28 20:59:38 node-1 puppet-user[10191]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 28 20:59:39 node-1 puppet-user[10191]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 28 20:59:39 node-1 puppet-user[10191]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 28 20:59:39 node-1 puppet-user[10191]: Finished catalog run in 0.04 seconds
Jul 28 20:59:40 node-1 puppet-user[10658]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 28 20:59:40 node-1 puppet-user[10658]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 28 20:59:40 node-1 puppet-user[10658]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 28 20:59:40 node-1 puppet-user[10658]: Finished catalog run in 0.04 seconds
Jul 28 20:59:42 node-1 puppet-user[11127]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 28 20:59:42 node-1 puppet-user[11127]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Jul 28 20:59:43 node-1 puppet-user[11127]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 28 20:59:43 node-1 kernel: [   65.744990] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 28 20:59:43 node-1 kernel: [   65.745043] 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.
Jul 28 20:59:43 node-1 puppet-user[11127]: (/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'
Jul 28 20:59:43 node-1 puppet-user[11127]: Finished catalog run in 0.05 seconds
Jul 28 20:59:44 node-1 puppet-user[11587]: (Scope(Class[main])) MODULAR: sync_time
Jul 28 20:59:44 node-1 puppet-user[11587]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 28 20:59:45 node-1 ntpdate[12011]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 28 20:59:49 node-1 kernel: [   72.002500] init: plymouth-upstart-bridge main process ended, respawning
Jul 28 20:59:49 node-1 puppet-agent[8908]: Could not run: SIGTERM
Jul 28 20:59:49 node-1 kernel: [   72.214560] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 28 20:59:49 node-1 ec2: 
Jul 28 20:59:49 node-1 ec2: #############################################################
Jul 28 20:59:49 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 28 20:59:49 node-1 ec2: 1024 d2:10:82:2e:8d:42:3b:09:2a:4f:39:45:11:05:b5:45  root@node-1.domain.tld (DSA)
Jul 28 20:59:49 node-1 ec2: 256 c2:e5:cf:d2:53:d5:98:c8:75:89:eb:5e:77:09:65:7d  root@node-1.domain.tld (ECDSA)
Jul 28 20:59:49 node-1 ec2: 256 55:bb:ba:d9:63:e0:0f:d6:39:92:e0:55:e7:53:a6:c7  root@node-1.domain.tld (ED25519)
Jul 28 20:59:49 node-1 ec2: 2048 3f:2e:a6:b6:48:80:2c:ce:1f:07:3b:ba:7f:76:e8:6c  root@node-1.domain.tld (RSA)
Jul 28 20:59:49 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 28 20:59:49 node-1 ec2: #############################################################
Jul 28 20:59:51 node-1 ntpdate[12011]: adjust time server 10.20.0.2 offset 0.000068 sec
Jul 28 20:59:51 node-1 puppet-user[11587]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 28 20:59:51 node-1 puppet-user[11587]: Finished catalog run in 6.22 seconds
Jul 28 20:59:56 node-1 puppet-user[12394]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 28 20:59:57 node-1 puppet-user[12394]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Jul 28 20:59:57 node-1 puppet-user[12394]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 28 20:59:57 node-1 puppet-user[12394]: Finished catalog run in 0.07 seconds
Jul 28 20:59:58 node-1 puppet-user[12855]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 28 20:59:59 node-1 puppet-user[12855]: Compiled catalog for node-1.domain.tld in environment production in 1.23 seconds
Jul 28 20:59:59 node-1 puppet-user[12855]: (/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
Jul 28 20:59:59 node-1 puppet-user[12855]: (/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
Jul 28 20:59:59 node-1 puppet-user[12855]: (/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
Jul 28 20:59:59 node-1 puppet-user[12855]: (/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
Jul 28 21:00:00 node-1 puppet-user[12855]: (/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
Jul 28 21:00:00 node-1 puppet-user[12855]: (/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
Jul 28 21:00:00 node-1 puppet-user[12855]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 28 21:00:00 node-1 puppet-user[12855]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 28 21:00:00 node-1 puppet-user[12855]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 28 21:00:00 node-1 puppet-user[12855]: (/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
Jul 28 21:00:00 node-1 puppet-user[12855]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 28 21:00:00 node-1 puppet-user[12855]: (/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
Jul 28 21:00:00 node-1 puppet-user[12855]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 28 21:00:00 node-1 puppet-user[12855]: (/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
Jul 28 21:00:00 node-1 puppet-user[12855]: (/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
Jul 28 21:00:00 node-1 puppet-user[12855]: (/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
Jul 28 21:00:00 node-1 puppet-user[12855]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 28 21:00:00 node-1 puppet-user[12855]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 28 21:00:01 node-1 CRON[13386]: (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")
Jul 28 21:00:14 node-1 puppet-user[12855]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 28 21:00:14 node-1 puppet-user[12855]: Finished catalog run in 14.33 seconds
Jul 28 21:00:15 node-1 puppet-user[13862]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 28 21:00:15 node-1 puppet-user[13862]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Jul 28 21:00:20 node-1 puppet-user[13862]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 28 21:00:28 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 21:00:28 node-1 nailgun-agent: I, [2016-07-28T21:00:28.557471 #13389]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 28 21:00:41 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 21:00:41 node-1 nailgun-agent: I, [2016-07-28T21:00:41.816801 #13389]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 28 21:00:52 node-1 puppet-user[13862]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 28 21:00:52 node-1 puppet-user[13862]: Finished catalog run in 36.16 seconds
Jul 28 21:00:53 node-1 puppet-user[17012]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 28 21:00:54 node-1 puppet-user[17012]: Compiled catalog for node-1.domain.tld in environment production in 0.55 seconds
Jul 28 21:00:54 node-1 puppet-user[17012]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 28 21:00:54 node-1 puppet-user[17012]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 28 21:00:54 node-1 puppet-user[17012]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 28 21:00:54 node-1 puppet-user[17012]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 28 21:00:54 node-1 puppet-user[17012]: Finished catalog run in 0.09 seconds
Jul 28 21:00:56 node-1 puppet-user[17474]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 28 21:00:57 node-1 puppet-user[17474]: Compiled catalog for node-1.domain.tld in environment production in 0.82 seconds
Jul 28 21:00:57 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 28 21:00:57 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 28 21:00:57 node-1 crontab[17914]: (root) LIST (root)
Jul 28 21:00:57 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 28 21:00:57 node-1 crontab[17915]: (root) REPLACE (root)
Jul 28 21:01:00 node-1 puppet-user[17474]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 28 21:01:01 node-1 CRON[18095]: (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")
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 28 21:01:01 node-1 puppet-user[17474]: (/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
Jul 28 21:01:01 node-1 puppet-user[17474]: (/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
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 28 21:01:01 node-1 puppet-user[17474]: (/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
Jul 28 21:01:01 node-1 puppet-user[17474]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/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
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/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
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/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
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/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
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/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
Jul 28 21:01:02 node-1 puppet-user[17474]: (/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
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 28 21:01:02 node-1 puppet-user[17474]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 28 21:01:02 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8359" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 21:01:02 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 28 21:01:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:01:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:01:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:01:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:01:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:01:22 node-1 multipathd: uevent trigger error
<27>Jul 28 21:01:22 node-1 multipathd: uevent trigger error
<27>Jul 28 21:01:22 node-1 multipathd: uevent trigger error
<27>Jul 28 21:01:22 node-1 multipathd: uevent trigger error
<27>Jul 28 21:01:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:01:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:01:26 node-1 multipathd: uevent trigger error
<27>Jul 28 21:01:26 node-1 multipathd: uevent trigger error
<27>Jul 28 21:01:26 node-1 multipathd: uevent trigger error
<27>Jul 28 21:02:25 node-1 ntpdate[29648]: no servers can be used, exiting
<27>Jul 28 21:02:57 node-1 multipathd: uevent trigger error
<27>Jul 28 21:02:57 node-1 multipathd: uevent trigger error
<27>Jul 28 21:02:57 node-1 multipathd: uevent trigger error
<27>Jul 28 21:02:57 node-1 multipathd: uevent trigger error
<27>Jul 28 21:02:57 node-1 multipathd: uevent trigger error
<27>Jul 28 21:03:00 node-1 multipathd: uevent trigger error
<27>Jul 28 21:03:00 node-1 multipathd: uevent trigger error
<27>Jul 28 21:03:00 node-1 multipathd: uevent trigger error
<27>Jul 28 21:03:00 node-1 multipathd: uevent trigger error
<27>Jul 28 21:03:00 node-1 multipathd: uevent trigger error
<27>Jul 28 21:03:13 node-1 multipathd: uevent trigger error
<27>Jul 28 21:03:13 node-1 multipathd: uevent trigger error
<27>Jul 28 21:03:13 node-1 multipathd: uevent trigger error
<27>Jul 28 21:03:13 node-1 multipathd: uevent trigger error
<27>Jul 28 21:03:13 node-1 multipathd: uevent trigger error
<27>Jul 28 21:03:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:03:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:03:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:03:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:03:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:03:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:04:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:04:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:04:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:04:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:04:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:04:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:04:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:04:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:04:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:04:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:04:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:04:27 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 21:04:27 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 28 21:04:33 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 21:04:33 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 28 21:04:39 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 28 21:04:44 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 21:04:44 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 28 21:04:51 node-1 multipathd: uevent trigger error
<27>Jul 28 21:04:51 node-1 multipathd: uevent trigger error
<27>Jul 28 21:04:51 node-1 multipathd: uevent trigger error
<27>Jul 28 21:04:51 node-1 multipathd: uevent trigger error
<27>Jul 28 21:04:51 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:04 node-1 multipathd: uevent trigger error
<129>Jul 28 21:05:07 node-1 haproxy[17438]: 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>Jul 28 21:05:07 node-1 haproxy[17438]: 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>Jul 28 21:05:08 node-1 haproxy[17447]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:08 node-1 haproxy[17447]: proxy mysqld has no server available!
<27>Jul 28 21:05:10 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:10 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:10 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:10 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:10 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:13 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:13 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:14 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:14 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:14 node-1 multipathd: uevent trigger error
<129>Jul 28 21:05:16 node-1 haproxy[20041]: 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>Jul 28 21:05:16 node-1 haproxy[20041]: 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>Jul 28 21:05:17 node-1 haproxy[20045]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:17 node-1 haproxy[20045]: proxy mysqld has no server available!
<129>Jul 28 21:05:17 node-1 haproxy[20045]: 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>Jul 28 21:05:17 node-1 haproxy[20045]: 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>Jul 28 21:05:18 node-1 haproxy[20045]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:18 node-1 haproxy[20045]: proxy object-storage has no server available!
<27>Jul 28 21:05:19 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:19 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:19 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:19 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:19 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:19 node-1 multipathd: uevent trigger error
<129>Jul 28 21:05:21 node-1 haproxy[21453]: 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>Jul 28 21:05:22 node-1 haproxy[21458]: 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>Jul 28 21:05:22 node-1 haproxy[21458]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:22 node-1 haproxy[21458]: proxy neutron has no server available!
<129>Jul 28 21:05:22 node-1 haproxy[21458]: 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>Jul 28 21:05:22 node-1 haproxy[21458]: 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>Jul 28 21:05:23 node-1 haproxy[21458]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:23 node-1 haproxy[21458]: proxy mysqld has no server available!
<129>Jul 28 21:05:23 node-1 haproxy[21458]: 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>Jul 28 21:05:23 node-1 haproxy[21458]: 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>Jul 28 21:05:23 node-1 haproxy[21458]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:23 node-1 haproxy[21458]: proxy object-storage has no server available!
<27>Jul 28 21:05:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:25 node-1 multipathd: uevent trigger error
<129>Jul 28 21:05:27 node-1 haproxy[22887]: 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>Jul 28 21:05:27 node-1 haproxy[22887]: 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>Jul 28 21:05:28 node-1 haproxy[22899]: Server keystone-1/node-3 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>Jul 28 21:05:28 node-1 haproxy[22899]: proxy keystone-1 has no server available!
<129>Jul 28 21:05:28 node-1 haproxy[22899]: 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>Jul 28 21:05:28 node-1 haproxy[22899]: 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>Jul 28 21:05:28 node-1 haproxy[22899]: Server keystone-2/node-3 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>Jul 28 21:05:28 node-1 haproxy[22899]: proxy keystone-2 has no server available!
<129>Jul 28 21:05:28 node-1 haproxy[22899]: 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>Jul 28 21:05:28 node-1 haproxy[22899]: 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>Jul 28 21:05:28 node-1 haproxy[22899]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:28 node-1 haproxy[22899]: proxy neutron has no server available!
<129>Jul 28 21:05:28 node-1 haproxy[22899]: 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>Jul 28 21:05:29 node-1 haproxy[22899]: 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>Jul 28 21:05:29 node-1 haproxy[22899]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:29 node-1 haproxy[22899]: proxy mysqld has no server available!
<129>Jul 28 21:05:29 node-1 haproxy[22899]: 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>Jul 28 21:05:29 node-1 haproxy[22899]: 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>Jul 28 21:05:29 node-1 haproxy[22899]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:29 node-1 haproxy[22899]: proxy object-storage has no server available!
<27>Jul 28 21:05:30 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:30 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:30 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:30 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:30 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:30 node-1 multipathd: uevent trigger error
<129>Jul 28 21:05:33 node-1 haproxy[24396]: 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>Jul 28 21:05:33 node-1 haproxy[24396]: 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>Jul 28 21:05:33 node-1 haproxy[24396]: Server keystone-1/node-3 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>Jul 28 21:05:33 node-1 haproxy[24396]: proxy keystone-1 has no server available!
<129>Jul 28 21:05:33 node-1 haproxy[24396]: 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>Jul 28 21:05:33 node-1 haproxy[24396]: 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>Jul 28 21:05:33 node-1 haproxy[24396]: Server keystone-2/node-3 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>Jul 28 21:05:33 node-1 haproxy[24396]: proxy keystone-2 has no server available!
<129>Jul 28 21:05:33 node-1 haproxy[24396]: 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>Jul 28 21:05:33 node-1 haproxy[24396]: 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>Jul 28 21:05:33 node-1 haproxy[24396]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:33 node-1 haproxy[24396]: proxy neutron has no server available!
<129>Jul 28 21:05:34 node-1 haproxy[24400]: 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>Jul 28 21:05:34 node-1 haproxy[24400]: 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>Jul 28 21:05:34 node-1 haproxy[24400]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:34 node-1 haproxy[24400]: proxy mysqld has no server available!
<129>Jul 28 21:05:34 node-1 haproxy[24400]: 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>Jul 28 21:05:34 node-1 haproxy[24400]: 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>Jul 28 21:05:34 node-1 haproxy[24400]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:34 node-1 haproxy[24400]: proxy object-storage has no server available!
<129>Jul 28 21:05:34 node-1 haproxy[24400]: 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>Jul 28 21:05:34 node-1 haproxy[24400]: 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>Jul 28 21:05:34 node-1 haproxy[24400]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:34 node-1 haproxy[24400]: proxy aodh has no server available!
<27>Jul 28 21:05:36 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:36 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:36 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:36 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:36 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:36 node-1 multipathd: uevent trigger error
<129>Jul 28 21:05:38 node-1 haproxy[25727]: 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>Jul 28 21:05:38 node-1 haproxy[25727]: 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>Jul 28 21:05:38 node-1 haproxy[25727]: Server keystone-1/node-3 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>Jul 28 21:05:38 node-1 haproxy[25727]: proxy keystone-1 has no server available!
<129>Jul 28 21:05:38 node-1 haproxy[25727]: 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>Jul 28 21:05:38 node-1 haproxy[25727]: 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>Jul 28 21:05:38 node-1 haproxy[25727]: Server keystone-2/node-3 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>Jul 28 21:05:38 node-1 haproxy[25727]: proxy keystone-2 has no server available!
<129>Jul 28 21:05:38 node-1 haproxy[25727]: 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>Jul 28 21:05:39 node-1 haproxy[25731]: 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>Jul 28 21:05:39 node-1 haproxy[25731]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:39 node-1 haproxy[25731]: proxy neutron has no server available!
<129>Jul 28 21:05:39 node-1 haproxy[25731]: 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>Jul 28 21:05:39 node-1 haproxy[25731]: 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>Jul 28 21:05:39 node-1 haproxy[25731]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:39 node-1 haproxy[25731]: proxy mysqld has no server available!
<129>Jul 28 21:05:39 node-1 haproxy[25731]: 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>Jul 28 21:05:39 node-1 haproxy[25731]: 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>Jul 28 21:05:39 node-1 haproxy[25731]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:39 node-1 haproxy[25731]: proxy object-storage has no server available!
<129>Jul 28 21:05:39 node-1 haproxy[25731]: 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>Jul 28 21:05:39 node-1 haproxy[25731]: 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>Jul 28 21:05:40 node-1 haproxy[25731]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:40 node-1 haproxy[25731]: proxy aodh has no server available!
<129>Jul 28 21:05:40 node-1 haproxy[25731]: 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>Jul 28 21:05:40 node-1 haproxy[25731]: 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>Jul 28 21:05:40 node-1 haproxy[25731]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:40 node-1 haproxy[25731]: proxy ceilometer has no server available!
<27>Jul 28 21:05:41 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:41 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:41 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:41 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:41 node-1 multipathd: uevent trigger error
<129>Jul 28 21:05:43 node-1 haproxy[27256]: 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>Jul 28 21:05:43 node-1 haproxy[27256]: 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>Jul 28 21:05:43 node-1 haproxy[27256]: Server keystone-1/node-3 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>Jul 28 21:05:43 node-1 haproxy[27256]: proxy keystone-1 has no server available!
<129>Jul 28 21:05:44 node-1 haproxy[27260]: 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>Jul 28 21:05:44 node-1 haproxy[27260]: 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>Jul 28 21:05:44 node-1 haproxy[27260]: Server keystone-2/node-3 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>Jul 28 21:05:44 node-1 haproxy[27260]: proxy keystone-2 has no server available!
<129>Jul 28 21:05:44 node-1 haproxy[27260]: 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>Jul 28 21:05:44 node-1 haproxy[27260]: 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>Jul 28 21:05:44 node-1 haproxy[27260]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:44 node-1 haproxy[27260]: proxy neutron has no server available!
<129>Jul 28 21:05:44 node-1 haproxy[27260]: 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>Jul 28 21:05:44 node-1 haproxy[27260]: 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>Jul 28 21:05:44 node-1 haproxy[27260]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:44 node-1 haproxy[27260]: proxy mysqld has no server available!
<129>Jul 28 21:05:44 node-1 haproxy[27260]: 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>Jul 28 21:05:45 node-1 haproxy[27260]: 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>Jul 28 21:05:45 node-1 haproxy[27260]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:45 node-1 haproxy[27260]: proxy object-storage has no server available!
<129>Jul 28 21:05:45 node-1 haproxy[27260]: 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>Jul 28 21:05:45 node-1 haproxy[27260]: 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>Jul 28 21:05:45 node-1 haproxy[27260]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:45 node-1 haproxy[27260]: proxy aodh has no server available!
<129>Jul 28 21:05:45 node-1 haproxy[27260]: 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>Jul 28 21:05:45 node-1 haproxy[27260]: 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>Jul 28 21:05:45 node-1 haproxy[27260]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:45 node-1 haproxy[27260]: proxy ceilometer has no server available!
<27>Jul 28 21:05:46 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:46 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:46 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:46 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:46 node-1 multipathd: uevent trigger error
<129>Jul 28 21:05:49 node-1 haproxy[28615]: 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>Jul 28 21:05:49 node-1 haproxy[28615]: 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>Jul 28 21:05:49 node-1 haproxy[28615]: 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>Jul 28 21:05:49 node-1 haproxy[28615]: Server keystone-1/node-3 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>Jul 28 21:05:49 node-1 haproxy[28615]: proxy keystone-1 has no server available!
<129>Jul 28 21:05:49 node-1 haproxy[28615]: 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>Jul 28 21:05:49 node-1 haproxy[28615]: 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>Jul 28 21:05:49 node-1 haproxy[28615]: Server keystone-2/node-3 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>Jul 28 21:05:49 node-1 haproxy[28615]: proxy keystone-2 has no server available!
<129>Jul 28 21:05:49 node-1 haproxy[28615]: 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>Jul 28 21:05:49 node-1 haproxy[28615]: 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>Jul 28 21:05:50 node-1 haproxy[28619]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:50 node-1 haproxy[28619]: proxy neutron has no server available!
<129>Jul 28 21:05:50 node-1 haproxy[28619]: 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>Jul 28 21:05:50 node-1 haproxy[28619]: 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>Jul 28 21:05:50 node-1 haproxy[28619]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:50 node-1 haproxy[28619]: proxy mysqld has no server available!
<129>Jul 28 21:05:50 node-1 haproxy[28619]: 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>Jul 28 21:05:50 node-1 haproxy[28619]: 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>Jul 28 21:05:50 node-1 haproxy[28619]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:50 node-1 haproxy[28619]: proxy object-storage has no server available!
<129>Jul 28 21:05:50 node-1 haproxy[28619]: 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>Jul 28 21:05:50 node-1 haproxy[28619]: 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>Jul 28 21:05:50 node-1 haproxy[28619]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:50 node-1 haproxy[28619]: proxy aodh has no server available!
<129>Jul 28 21:05:50 node-1 haproxy[28619]: 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>Jul 28 21:05:50 node-1 haproxy[28619]: 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>Jul 28 21:05:51 node-1 haproxy[28619]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:51 node-1 haproxy[28619]: proxy ceilometer has no server available!
<27>Jul 28 21:05:52 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:52 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:52 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:52 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:52 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:52 node-1 multipathd: uevent trigger error
<129>Jul 28 21:05:55 node-1 haproxy[30027]: 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>Jul 28 21:05:55 node-1 haproxy[30027]: 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>Jul 28 21:05:55 node-1 haproxy[30027]: 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>Jul 28 21:05:55 node-1 haproxy[30027]: Server keystone-1/node-3 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>Jul 28 21:05:55 node-1 haproxy[30027]: proxy keystone-1 has no server available!
<129>Jul 28 21:05:55 node-1 haproxy[30027]: 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>Jul 28 21:05:55 node-1 haproxy[30027]: 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>Jul 28 21:05:55 node-1 haproxy[30027]: Server keystone-2/node-3 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>Jul 28 21:05:55 node-1 haproxy[30027]: proxy keystone-2 has no server available!
<129>Jul 28 21:05:55 node-1 haproxy[30027]: 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>Jul 28 21:05:55 node-1 haproxy[30027]: 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>Jul 28 21:05:55 node-1 haproxy[30027]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:55 node-1 haproxy[30027]: proxy glance-api has no server available!
<129>Jul 28 21:05:55 node-1 haproxy[30027]: 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>Jul 28 21:05:55 node-1 haproxy[30027]: 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>Jul 28 21:05:55 node-1 haproxy[30027]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:55 node-1 haproxy[30027]: proxy glance-glare has no server available!
<129>Jul 28 21:05:55 node-1 haproxy[30027]: 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>Jul 28 21:05:55 node-1 haproxy[30027]: 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>Jul 28 21:05:56 node-1 haproxy[30031]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:56 node-1 haproxy[30031]: proxy neutron has no server available!
<129>Jul 28 21:05:56 node-1 haproxy[30031]: 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>Jul 28 21:05:56 node-1 haproxy[30031]: 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>Jul 28 21:05:56 node-1 haproxy[30031]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:56 node-1 haproxy[30031]: proxy glance-registry has no server available!
<129>Jul 28 21:05:56 node-1 haproxy[30031]: 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>Jul 28 21:05:56 node-1 haproxy[30031]: 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>Jul 28 21:05:56 node-1 haproxy[30031]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:56 node-1 haproxy[30031]: proxy mysqld has no server available!
<129>Jul 28 21:05:56 node-1 haproxy[30031]: 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>Jul 28 21:05:56 node-1 haproxy[30031]: 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>Jul 28 21:05:56 node-1 haproxy[30031]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:56 node-1 haproxy[30031]: proxy object-storage has no server available!
<129>Jul 28 21:05:56 node-1 haproxy[30031]: 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>Jul 28 21:05:56 node-1 haproxy[30031]: 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>Jul 28 21:05:56 node-1 haproxy[30031]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:56 node-1 haproxy[30031]: proxy aodh has no server available!
<129>Jul 28 21:05:56 node-1 haproxy[30031]: 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>Jul 28 21:05:56 node-1 haproxy[30031]: 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>Jul 28 21:05:56 node-1 haproxy[30031]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:05:56 node-1 haproxy[30031]: proxy ceilometer has no server available!
<27>Jul 28 21:05:58 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:58 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:58 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:58 node-1 multipathd: uevent trigger error
<27>Jul 28 21:05:58 node-1 multipathd: uevent trigger error
<129>Jul 28 21:06:00 node-1 haproxy[31443]: 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>Jul 28 21:06:00 node-1 haproxy[31443]: 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>Jul 28 21:06:01 node-1 haproxy[31447]: 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>Jul 28 21:06:01 node-1 haproxy[31447]: Server keystone-1/node-3 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>Jul 28 21:06:01 node-1 haproxy[31447]: proxy keystone-1 has no server available!
<129>Jul 28 21:06:01 node-1 haproxy[31447]: 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>Jul 28 21:06:01 node-1 haproxy[31447]: 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>Jul 28 21:06:01 node-1 haproxy[31447]: Server keystone-2/node-3 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>Jul 28 21:06:01 node-1 haproxy[31447]: proxy keystone-2 has no server available!
<129>Jul 28 21:06:01 node-1 haproxy[31447]: 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>Jul 28 21:06:01 node-1 haproxy[31447]: 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>Jul 28 21:06:01 node-1 haproxy[31447]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:01 node-1 haproxy[31447]: proxy nova-api has no server available!
<129>Jul 28 21:06:01 node-1 haproxy[31447]: 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>Jul 28 21:06:01 node-1 haproxy[31447]: 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>Jul 28 21:06:01 node-1 haproxy[31447]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:01 node-1 haproxy[31447]: proxy nova-metadata-api has no server available!
<129>Jul 28 21:06:01 node-1 haproxy[31447]: 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>Jul 28 21:06:01 node-1 haproxy[31447]: 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>Jul 28 21:06:01 node-1 haproxy[31447]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:01 node-1 haproxy[31447]: proxy glance-api has no server available!
<129>Jul 28 21:06:01 node-1 haproxy[31447]: 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>Jul 28 21:06:01 node-1 haproxy[31447]: 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>Jul 28 21:06:01 node-1 haproxy[31447]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:01 node-1 haproxy[31447]: proxy glance-glare has no server available!
<129>Jul 28 21:06:01 node-1 haproxy[31447]: 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>Jul 28 21:06:01 node-1 haproxy[31447]: 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>Jul 28 21:06:01 node-1 haproxy[31447]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:01 node-1 haproxy[31447]: proxy neutron has no server available!
<129>Jul 28 21:06:01 node-1 haproxy[31447]: 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>Jul 28 21:06:02 node-1 haproxy[31447]: 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>Jul 28 21:06:02 node-1 haproxy[31447]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:02 node-1 haproxy[31447]: proxy glance-registry has no server available!
<129>Jul 28 21:06:02 node-1 haproxy[31447]: 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>Jul 28 21:06:02 node-1 haproxy[31447]: 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>Jul 28 21:06:02 node-1 haproxy[31447]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:02 node-1 haproxy[31447]: proxy mysqld has no server available!
<129>Jul 28 21:06:02 node-1 haproxy[31447]: 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>Jul 28 21:06:02 node-1 haproxy[31447]: 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>Jul 28 21:06:02 node-1 haproxy[31447]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:02 node-1 haproxy[31447]: proxy object-storage has no server available!
<129>Jul 28 21:06:02 node-1 haproxy[31447]: 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>Jul 28 21:06:02 node-1 haproxy[31447]: 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>Jul 28 21:06:02 node-1 haproxy[31447]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:02 node-1 haproxy[31447]: proxy aodh has no server available!
<129>Jul 28 21:06:02 node-1 haproxy[31447]: 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>Jul 28 21:06:02 node-1 haproxy[31447]: 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>Jul 28 21:06:02 node-1 haproxy[31447]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:02 node-1 haproxy[31447]: proxy ceilometer has no server available!
<129>Jul 28 21:06:02 node-1 haproxy[31447]: 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>Jul 28 21:06:02 node-1 haproxy[31447]: 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>Jul 28 21:06:02 node-1 haproxy[31447]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:02 node-1 haproxy[31447]: proxy nova-novncproxy has no server available!
<27>Jul 28 21:06:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:04 node-1 multipathd: uevent trigger error
<129>Jul 28 21:06:06 node-1 haproxy[322]: 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>Jul 28 21:06:06 node-1 haproxy[322]: 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>Jul 28 21:06:06 node-1 haproxy[322]: 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>Jul 28 21:06:06 node-1 haproxy[322]: Server keystone-1/node-3 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>Jul 28 21:06:06 node-1 haproxy[322]: proxy keystone-1 has no server available!
<129>Jul 28 21:06:06 node-1 haproxy[322]: 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>Jul 28 21:06:06 node-1 haproxy[322]: 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>Jul 28 21:06:06 node-1 haproxy[322]: Server keystone-2/node-3 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>Jul 28 21:06:06 node-1 haproxy[322]: proxy keystone-2 has no server available!
<129>Jul 28 21:06:06 node-1 haproxy[322]: 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>Jul 28 21:06:06 node-1 haproxy[322]: 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>Jul 28 21:06:06 node-1 haproxy[322]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:06 node-1 haproxy[322]: proxy nova-api has no server available!
<129>Jul 28 21:06:06 node-1 haproxy[322]: 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>Jul 28 21:06:07 node-1 haproxy[332]: 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>Jul 28 21:06:07 node-1 haproxy[332]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:07 node-1 haproxy[332]: proxy nova-metadata-api has no server available!
<129>Jul 28 21:06:07 node-1 haproxy[332]: 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>Jul 28 21:06:07 node-1 haproxy[332]: 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>Jul 28 21:06:07 node-1 haproxy[332]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:07 node-1 haproxy[332]: proxy cinder-api has no server available!
<129>Jul 28 21:06:07 node-1 haproxy[332]: 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>Jul 28 21:06:07 node-1 haproxy[332]: 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>Jul 28 21:06:07 node-1 haproxy[332]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:07 node-1 haproxy[332]: proxy glance-api has no server available!
<129>Jul 28 21:06:07 node-1 haproxy[332]: 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>Jul 28 21:06:07 node-1 haproxy[332]: 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>Jul 28 21:06:07 node-1 haproxy[332]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:07 node-1 haproxy[332]: proxy glance-glare has no server available!
<129>Jul 28 21:06:07 node-1 haproxy[332]: 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>Jul 28 21:06:07 node-1 haproxy[332]: 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>Jul 28 21:06:07 node-1 haproxy[332]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:07 node-1 haproxy[332]: proxy neutron has no server available!
<129>Jul 28 21:06:07 node-1 haproxy[332]: 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>Jul 28 21:06:07 node-1 haproxy[332]: 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>Jul 28 21:06:07 node-1 haproxy[332]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:07 node-1 haproxy[332]: proxy glance-registry has no server available!
<129>Jul 28 21:06:07 node-1 haproxy[332]: 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>Jul 28 21:06:07 node-1 haproxy[332]: 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>Jul 28 21:06:07 node-1 haproxy[332]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:07 node-1 haproxy[332]: proxy mysqld has no server available!
<129>Jul 28 21:06:07 node-1 haproxy[332]: 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>Jul 28 21:06:07 node-1 haproxy[332]: 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>Jul 28 21:06:07 node-1 haproxy[332]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:07 node-1 haproxy[332]: proxy object-storage has no server available!
<129>Jul 28 21:06:08 node-1 haproxy[332]: 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>Jul 28 21:06:08 node-1 haproxy[332]: 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>Jul 28 21:06:08 node-1 haproxy[332]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:08 node-1 haproxy[332]: proxy aodh has no server available!
<129>Jul 28 21:06:08 node-1 haproxy[332]: 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>Jul 28 21:06:08 node-1 haproxy[332]: 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>Jul 28 21:06:08 node-1 haproxy[332]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:08 node-1 haproxy[332]: proxy ceilometer has no server available!
<129>Jul 28 21:06:08 node-1 haproxy[332]: 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>Jul 28 21:06:08 node-1 haproxy[332]: 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>Jul 28 21:06:08 node-1 haproxy[332]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:08 node-1 haproxy[332]: proxy nova-novncproxy has no server available!
<27>Jul 28 21:06:09 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:09 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:09 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:09 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:09 node-1 multipathd: uevent trigger error
<129>Jul 28 21:06:12 node-1 haproxy[1777]: 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>Jul 28 21:06:12 node-1 haproxy[1777]: 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>Jul 28 21:06:12 node-1 haproxy[1777]: 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>Jul 28 21:06:12 node-1 haproxy[1777]: Server keystone-1/node-3 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>Jul 28 21:06:12 node-1 haproxy[1777]: proxy keystone-1 has no server available!
<129>Jul 28 21:06:12 node-1 haproxy[1777]: 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>Jul 28 21:06:12 node-1 haproxy[1777]: 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>Jul 28 21:06:12 node-1 haproxy[1777]: Server keystone-2/node-3 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>Jul 28 21:06:12 node-1 haproxy[1777]: proxy keystone-2 has no server available!
<129>Jul 28 21:06:12 node-1 haproxy[1777]: 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>Jul 28 21:06:12 node-1 haproxy[1777]: 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>Jul 28 21:06:12 node-1 haproxy[1777]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:12 node-1 haproxy[1777]: proxy nova-api has no server available!
<129>Jul 28 21:06:12 node-1 haproxy[1777]: 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>Jul 28 21:06:12 node-1 haproxy[1777]: 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>Jul 28 21:06:12 node-1 haproxy[1777]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:12 node-1 haproxy[1777]: proxy nova-metadata-api has no server available!
<129>Jul 28 21:06:12 node-1 haproxy[1777]: 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>Jul 28 21:06:12 node-1 haproxy[1777]: 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>Jul 28 21:06:12 node-1 haproxy[1777]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:12 node-1 haproxy[1777]: proxy cinder-api has no server available!
<129>Jul 28 21:06:12 node-1 haproxy[1777]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:13 node-1 haproxy[1781]: proxy glance-api has no server available!
<129>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:13 node-1 haproxy[1781]: proxy glance-glare has no server available!
<129>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:13 node-1 haproxy[1781]: proxy neutron has no server available!
<129>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:13 node-1 haproxy[1781]: proxy glance-registry has no server available!
<129>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:13 node-1 haproxy[1781]: proxy mysqld has no server available!
<129>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:13 node-1 haproxy[1781]: proxy object-storage has no server available!
<129>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:13 node-1 haproxy[1781]: proxy aodh has no server available!
<129>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:13 node-1 haproxy[1781]: proxy ceilometer has no server available!
<129>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:13 node-1 haproxy[1781]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:13 node-1 haproxy[1781]: proxy heat-api has no server available!
<129>Jul 28 21:06:13 node-1 haproxy[1781]: 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>Jul 28 21:06:14 node-1 haproxy[1781]: 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>Jul 28 21:06:14 node-1 haproxy[1781]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:14 node-1 haproxy[1781]: proxy heat-api-cfn has no server available!
<129>Jul 28 21:06:14 node-1 haproxy[1781]: 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>Jul 28 21:06:14 node-1 haproxy[1781]: 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>Jul 28 21:06:14 node-1 haproxy[1781]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:14 node-1 haproxy[1781]: proxy heat-api-cloudwatch has no server available!
<129>Jul 28 21:06:14 node-1 haproxy[1781]: 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>Jul 28 21:06:14 node-1 haproxy[1781]: 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>Jul 28 21:06:14 node-1 haproxy[1781]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 21:06:14 node-1 haproxy[1781]: proxy nova-novncproxy has no server available!
<27>Jul 28 21:06:15 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:15 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:15 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:15 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:15 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:19 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:19 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:19 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:19 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:19 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:19 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:19 node-1 multipathd: uevent trigger error
<27>Jul 28 21:06:31 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 28 21:06:56 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>Jul 28 21:06:58 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 28 21:07:20 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 21:07:26 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 21:07:45 node-1 multipathd: uevent trigger error
<27>Jul 28 21:07:45 node-1 multipathd: uevent trigger error
<27>Jul 28 21:07:45 node-1 multipathd: uevent trigger error
<27>Jul 28 21:07:45 node-1 multipathd: uevent trigger error
<27>Jul 28 21:07:45 node-1 multipathd: uevent trigger error
<27>Jul 28 21:07:45 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:05 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:05 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:05 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:05 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:05 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:05 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:12 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:12 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:12 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:12 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:12 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:26 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 28 21:10:33 node-1 apache2_error [Thu Jul 28 21:10:24.868247 2016] [mpm_event:notice] [pid 10920:tid 140330497685376] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 28 21:10:33 node-1 apache2_error [Thu Jul 28 21:10:24.868416 2016] [core:notice] [pid 10920:tid 140330497685376] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 28 21:10:33 node-1 apache2_error [Thu Jul 28 21:10:27.956955 2016] [mpm_event:notice] [pid 10920:tid 140330497685376] AH00491: caught SIGTERM, shutting down
<43>Jul 28 21:10:33 node-1 apache2_error [Thu Jul 28 21:10:29.079126 2016] [mpm_worker:notice] [pid 11547:tid 139791893759872] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 28 21:10:33 node-1 apache2_error [Thu Jul 28 21:10:29.079187 2016] [core:notice] [pid 11547:tid 139791893759872] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 21:10:33 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:33 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:33 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:33 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:33 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:38 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:38 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:38 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:38 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:38 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:41 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:41 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:41 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:41 node-1 multipathd: uevent trigger error
<27>Jul 28 21:10:41 node-1 multipathd: uevent trigger error
<43>Jul 28 21:11:53 node-1 apache2_error [Thu Jul 28 21:11:51.246575 2016] [mpm_worker:notice] [pid 11547:tid 139791893759872] AH00295: caught SIGTERM, shutting down
<43>Jul 28 21:11:53 node-1 apache2_error [Thu Jul 28 21:11:52.008255 2016] [mpm_worker:notice] [pid 25905:tid 140695543658368] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 21:11:53 node-1 apache2_error [Thu Jul 28 21:11:52.008296 2016] [core:notice] [pid 25905:tid 140695543658368] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 28 21:12:43 node-1 apache2_error [Thu Jul 28 21:12:35.713720 2016] [mpm_worker:notice] [pid 25905:tid 140695543658368] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 21:12:43 node-1 apache2_error [Thu Jul 28 21:12:35.908288 2016] [mpm_worker:warn] [pid 25905:tid 140695543658368] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 21:12:43 node-1 apache2_error [Thu Jul 28 21:12:35.910897 2016] [mpm_worker:notice] [pid 25905:tid 140695543658368] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 21:12:43 node-1 apache2_error [Thu Jul 28 21:12:35.910914 2016] [core:notice] [pid 25905:tid 140695543658368] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 21:13:20 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:20 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:20 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:20 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:20 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:20 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:20 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:20 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:24 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:24 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:24 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:24 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:27 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 21:13:40 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:40 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:40 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:40 node-1 multipathd: uevent trigger error
<27>Jul 28 21:13:40 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:02 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:02 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:02 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:02 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:02 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:02 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:07 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:07 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:07 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:07 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:07 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:14:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:15:17 node-1 multipathd: uevent trigger error
<27>Jul 28 21:15:17 node-1 multipathd: uevent trigger error
<27>Jul 28 21:15:17 node-1 multipathd: uevent trigger error
<27>Jul 28 21:15:17 node-1 multipathd: uevent trigger error
<27>Jul 28 21:15:17 node-1 multipathd: uevent trigger error
<27>Jul 28 21:15:17 node-1 multipathd: uevent trigger error
<27>Jul 28 21:16:29 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 21:16:32 node-1 multipathd: uevent trigger error
<27>Jul 28 21:16:32 node-1 multipathd: uevent trigger error
<27>Jul 28 21:16:32 node-1 multipathd: uevent trigger error
<27>Jul 28 21:16:32 node-1 multipathd: uevent trigger error
<27>Jul 28 21:16:32 node-1 multipathd: uevent trigger error
<27>Jul 28 21:17:31 node-1 multipathd: uevent trigger error
<27>Jul 28 21:17:31 node-1 multipathd: uevent trigger error
<27>Jul 28 21:17:31 node-1 multipathd: uevent trigger error
<27>Jul 28 21:17:31 node-1 multipathd: uevent trigger error
<27>Jul 28 21:17:31 node-1 multipathd: uevent trigger error
<27>Jul 28 21:17:31 node-1 multipathd: uevent trigger error
<27>Jul 28 21:17:31 node-1 multipathd: uevent trigger error
<27>Jul 28 21:17:55 node-1 multipathd: uevent trigger error
<27>Jul 28 21:17:55 node-1 multipathd: uevent trigger error
<27>Jul 28 21:17:55 node-1 multipathd: uevent trigger error
<27>Jul 28 21:17:55 node-1 multipathd: uevent trigger error
<27>Jul 28 21:17:55 node-1 multipathd: uevent trigger error
<27>Jul 28 21:18:00 node-1 multipathd: uevent trigger error
<27>Jul 28 21:18:00 node-1 multipathd: uevent trigger error
<27>Jul 28 21:18:01 node-1 multipathd: uevent trigger error
<27>Jul 28 21:18:01 node-1 multipathd: uevent trigger error
<27>Jul 28 21:18:01 node-1 multipathd: uevent trigger error
<27>Jul 28 21:18:01 node-1 multipathd: uevent trigger error
<27>Jul 28 21:19:32 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 21:20:28 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:28 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:28 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:28 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:28 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:28 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:42 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:42 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:42 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:42 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:42 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:42 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:42 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:48 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:48 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:48 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:48 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:48 node-1 multipathd: uevent trigger error
<27>Jul 28 21:20:48 node-1 multipathd: uevent trigger error
<27>Jul 28 21:21:30 node-1 multipathd: uevent trigger error
<27>Jul 28 21:21:30 node-1 multipathd: uevent trigger error
<27>Jul 28 21:21:30 node-1 multipathd: uevent trigger error
<27>Jul 28 21:21:30 node-1 multipathd: uevent trigger error
<27>Jul 28 21:21:30 node-1 multipathd: uevent trigger error
<27>Jul 28 21:21:30 node-1 multipathd: uevent trigger error
<27>Jul 28 21:21:30 node-1 multipathd: uevent trigger error
<27>Jul 28 21:21:35 node-1 multipathd: uevent trigger error
<27>Jul 28 21:21:35 node-1 multipathd: uevent trigger error
<27>Jul 28 21:21:35 node-1 multipathd: uevent trigger error
<27>Jul 28 21:21:35 node-1 multipathd: uevent trigger error
<27>Jul 28 21:21:35 node-1 multipathd: uevent trigger error
<27>Jul 28 21:21:35 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:00 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:00 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:00 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:00 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:00 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:33 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 21:22:45 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:45 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:45 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:45 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:45 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:52 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Jul 28 21:22:52 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Jul 28 21:22:52 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Jul 28 21:22:53 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Jul 28 21:22:54 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Jul 28 21:22:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:22:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:08 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:08 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:08 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:08 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:08 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:23 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:23 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:23 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:23 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:23 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:23 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:41 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:41 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:41 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:41 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:41 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:41 node-1 multipathd: uevent trigger error
<27>Jul 28 21:23:41 node-1 multipathd: uevent trigger error
<27>Jul 28 21:25:35 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 21:26:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:26:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:26:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:26:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:26:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:26:19 node-1 multipathd: uevent trigger error
<27>Jul 28 21:26:20 node-1 multipathd: uevent trigger error
<27>Jul 28 21:26:20 node-1 multipathd: uevent trigger error
<27>Jul 28 21:26:29 node-1 multipathd: uevent trigger error
<27>Jul 28 21:26:29 node-1 multipathd: uevent trigger error
<27>Jul 28 21:26:29 node-1 multipathd: uevent trigger error
<27>Jul 28 21:26:29 node-1 multipathd: uevent trigger error
<27>Jul 28 21:26:29 node-1 multipathd: uevent trigger error
<27>Jul 28 21:26:29 node-1 multipathd: uevent trigger error
<27>Jul 28 21:26:30 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Jul 28 21:27:37 node-1 multipathd: uevent trigger error
<27>Jul 28 21:27:37 node-1 multipathd: uevent trigger error
<27>Jul 28 21:27:37 node-1 multipathd: uevent trigger error
<27>Jul 28 21:27:37 node-1 multipathd: uevent trigger error
<27>Jul 28 21:27:37 node-1 multipathd: uevent trigger error
<27>Jul 28 21:27:43 node-1 multipathd: uevent trigger error
<27>Jul 28 21:27:43 node-1 multipathd: uevent trigger error
<27>Jul 28 21:27:43 node-1 multipathd: uevent trigger error
<27>Jul 28 21:27:43 node-1 multipathd: uevent trigger error
<27>Jul 28 21:27:43 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:34 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:34 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:34 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:34 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:34 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:34 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:37 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 21:28:38 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:38 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:38 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:38 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:38 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:42 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:42 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:42 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:42 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:42 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:28:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:29:01 node-1 multipathd: uevent trigger error
<27>Jul 28 21:29:01 node-1 multipathd: uevent trigger error
<27>Jul 28 21:29:01 node-1 multipathd: uevent trigger error
<27>Jul 28 21:29:01 node-1 multipathd: uevent trigger error
<27>Jul 28 21:29:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:29:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:29:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:29:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:29:25 node-1 multipathd: uevent trigger error
<27>Jul 28 21:30:34 node-1 multipathd: uevent trigger error
<27>Jul 28 21:30:34 node-1 multipathd: uevent trigger error
<27>Jul 28 21:30:34 node-1 multipathd: uevent trigger error
<27>Jul 28 21:30:34 node-1 multipathd: uevent trigger error
<27>Jul 28 21:30:34 node-1 multipathd: uevent trigger error
<27>Jul 28 21:30:53 node-1 multipathd: uevent trigger error
<27>Jul 28 21:30:53 node-1 multipathd: uevent trigger error
<27>Jul 28 21:30:53 node-1 multipathd: uevent trigger error
<27>Jul 28 21:30:53 node-1 multipathd: uevent trigger error
<27>Jul 28 21:30:53 node-1 multipathd: uevent trigger error
<11>Jul 28 21:31:07 node-1 liberasurecode[87513]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:07 node-1 liberasurecode[87513]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:07 node-1 liberasurecode[87513]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:07 node-1 liberasurecode[87513]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:07 node-1 liberasurecode[87542]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:07 node-1 liberasurecode[87542]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:07 node-1 liberasurecode[87542]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:07 node-1 liberasurecode[87542]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:09 node-1 liberasurecode[87958]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:09 node-1 liberasurecode[87958]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:09 node-1 liberasurecode[87958]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:09 node-1 liberasurecode[87958]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:14 node-1 liberasurecode[88640]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:14 node-1 liberasurecode[88640]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:14 node-1 liberasurecode[88640]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:14 node-1 liberasurecode[88640]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:14 node-1 liberasurecode[88682]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:14 node-1 liberasurecode[88682]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:14 node-1 liberasurecode[88682]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:14 node-1 liberasurecode[88682]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88726]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88726]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88726]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88726]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88785]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88785]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88785]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88785]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88801]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88801]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88801]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88801]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88815]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88815]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88815]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88815]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88827]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88827]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88827]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:15 node-1 liberasurecode[88827]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:32 node-1 liberasurecode[91331]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:32 node-1 liberasurecode[91331]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:32 node-1 liberasurecode[91331]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:31:32 node-1 liberasurecode[91331]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 28 21:31:38 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 21:31:40 node-1 multipathd: uevent trigger error
<27>Jul 28 21:31:40 node-1 multipathd: uevent trigger error
<27>Jul 28 21:31:40 node-1 multipathd: uevent trigger error
<27>Jul 28 21:31:40 node-1 multipathd: uevent trigger error
<27>Jul 28 21:31:40 node-1 multipathd: uevent trigger error
<43>Jul 28 21:32:35 node-1 apache2_error [Thu Jul 28 21:32:27.456314 2016] [mpm_worker:notice] [pid 25905:tid 140695543658368] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 21:32:35 node-1 apache2_error [Thu Jul 28 21:32:27.839990 2016] [mpm_worker:warn] [pid 25905:tid 140695543658368] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 21:32:35 node-1 apache2_error [Thu Jul 28 21:32:27.845094 2016] [mpm_worker:notice] [pid 25905:tid 140695543658368] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 21:32:35 node-1 apache2_error [Thu Jul 28 21:32:27.845119 2016] [core:notice] [pid 25905:tid 140695543658368] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 28 21:33:05 node-1 apache2_error [Thu Jul 28 21:33:04.486637 2016] [mpm_worker:notice] [pid 25905:tid 140695543658368] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 21:33:05 node-1 apache2_error [Thu Jul 28 21:33:04.681674 2016] [mpm_worker:warn] [pid 25905:tid 140695543658368] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 21:33:05 node-1 apache2_error [Thu Jul 28 21:33:04.689955 2016] [mpm_worker:notice] [pid 25905:tid 140695543658368] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 21:33:05 node-1 apache2_error [Thu Jul 28 21:33:04.689982 2016] [core:notice] [pid 25905:tid 140695543658368] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 21:33:08 node-1 multipathd: uevent trigger error
<27>Jul 28 21:33:08 node-1 multipathd: uevent trigger error
<27>Jul 28 21:33:08 node-1 multipathd: uevent trigger error
<27>Jul 28 21:33:08 node-1 multipathd: uevent trigger error
<27>Jul 28 21:33:08 node-1 multipathd: uevent trigger error
<27>Jul 28 21:33:08 node-1 multipathd: uevent trigger error
<27>Jul 28 21:33:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:33:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:33:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:33:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:33:16 node-1 multipathd: uevent trigger error
<27>Jul 28 21:33:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:33:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:33:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:33:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:33:54 node-1 multipathd: uevent trigger error
<43>Jul 28 21:33:55 node-1 apache2_error [Thu Jul 28 21:33:50.643482 2016] [mpm_worker:notice] [pid 25905:tid 140695543658368] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 21:33:55 node-1 apache2_error [Thu Jul 28 21:33:50.837567 2016] [mpm_worker:warn] [pid 25905:tid 140695543658368] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 21:33:55 node-1 apache2_error [Thu Jul 28 21:33:50.844466 2016] [mpm_worker:notice] [pid 25905:tid 140695543658368] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 21:33:55 node-1 apache2_error [Thu Jul 28 21:33:50.844495 2016] [core:notice] [pid 25905:tid 140695543658368] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 21:34:01 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:01 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:01 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:01 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:01 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:07 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:07 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:07 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:07 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:07 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:07 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:21 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:21 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:21 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:21 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:21 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:43 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:46 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 21:34:50 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:50 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:50 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:50 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:50 node-1 multipathd: uevent trigger error
<27>Jul 28 21:34:57 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<11>Jul 28 21:35:01 node-1 liberasurecode[134128]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:35:01 node-1 liberasurecode[134128]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:35:01 node-1 liberasurecode[134128]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 21:35:01 node-1 liberasurecode[134128]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 28 21:35:06 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:06 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:06 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:06 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:06 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:11 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:11 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:11 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:11 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:11 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:11 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:21 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:21 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:21 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:21 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:21 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:26 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:26 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:26 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:26 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:26 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:39 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:39 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:39 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:39 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:39 node-1 multipathd: uevent trigger error
<27>Jul 28 21:35:42 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 21:36:06 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:06 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:06 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:06 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:06 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:11 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:11 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:11 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:11 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:11 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:24 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:24 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:24 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:24 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:24 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:32 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:32 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:32 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:32 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:32 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:32 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:37 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:37 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:37 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:37 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:37 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:49 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:49 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:49 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:49 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:49 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:54 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:59 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:59 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:59 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:59 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:59 node-1 multipathd: uevent trigger error
<27>Jul 28 21:36:59 node-1 multipathd: uevent trigger error
<27>Jul 28 21:37:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:37:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:37:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:37:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:37:04 node-1 multipathd: uevent trigger error
<27>Jul 28 21:37:08 node-1 multipathd: uevent trigger error
<27>Jul 28 21:37:08 node-1 multipathd: uevent trigger error
<27>Jul 28 21:37:08 node-1 multipathd: uevent trigger error
<27>Jul 28 21:37:08 node-1 multipathd: uevent trigger error
<27>Jul 28 21:37:09 node-1 multipathd: uevent trigger error
