Jul 26 21:10:05 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8415" x-info="http://www.rsyslog.com"] start
Jul 26 21:10:05 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 26 21:10:05 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 26 21:10:05 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 26 21:10:05 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 26 21:10:05 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 26 21:10:05 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 26 21:10:05 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 26 21:10:05 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=d6a4002d-fcf3-4b0b-8dec-ac0a764030af nomdmonddf nomdmonisw
Jul 26 21:10:05 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 26 21:10:05 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 26 21:10:05 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 26 21:10:05 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 26 21:10:05 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 26 21:10:05 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 26 21:10:05 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 26 21:10:05 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 26 21:10:05 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 26 21:10:05 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 26 21:10:05 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 26 21:10:05 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 26 21:10:05 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 26 21:10:05 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 26 21:10:05 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 26 21:10:05 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 26 21:10:05 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 26 21:10:05 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 26 21:10:05 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 26 21:10:05 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 26 21:10:05 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 26 21:10:05 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 26 21:10:05 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 26 21:10:05 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 26 21:10:05 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 26 21:10:05 node-1 kernel: [    0.000000] No AGP bridge found
Jul 26 21:10:05 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 26 21:10:05 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 26 21:10:05 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 26 21:10:05 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 26 21:10:05 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 26 21:10:05 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 26 21:10:05 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 26 21:10:05 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 26 21:10:05 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 26 21:10:05 node-1 kernel: [    0.000000]   2 disabled
Jul 26 21:10:05 node-1 kernel: [    0.000000]   3 disabled
Jul 26 21:10:05 node-1 kernel: [    0.000000]   4 disabled
Jul 26 21:10:05 node-1 kernel: [    0.000000]   5 disabled
Jul 26 21:10:05 node-1 kernel: [    0.000000]   6 disabled
Jul 26 21:10:05 node-1 kernel: [    0.000000]   7 disabled
Jul 26 21:10:05 node-1 kernel: [    0.000000]   8 disabled
Jul 26 21:10:05 node-1 kernel: [    0.000000]   9 disabled
Jul 26 21:10:05 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 26 21:10:05 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 26 21:10:05 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 26 21:10:05 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 26 21:10:05 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 26 21:10:05 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 26 21:10:05 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 26 21:10:05 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 26 21:10:05 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 26 21:10:05 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 26 21:10:05 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 26 21:10:05 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 26 21:10:05 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 26 21:10:05 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 26 21:10:05 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 26 21:10:05 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 26 21:10:05 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 26 21:10:05 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 26 21:10:05 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 26 21:10:05 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 26 21:10:05 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 26 21:10:05 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 26 21:10:05 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 26 21:10:05 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 26 21:10:05 node-1 kernel: [    0.000000] Zone ranges:
Jul 26 21:10:05 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 26 21:10:05 node-1 kernel: [    0.000000] Early memory node ranges
Jul 26 21:10:05 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 26 21:10:05 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 26 21:10:05 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 26 21:10:05 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 26 21:10:05 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 26 21:10:05 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 26 21:10:05 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 26 21:10:05 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 26 21:10:05 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 26 21:10:05 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 26 21:10:05 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 26 21:10:05 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 26 21:10:05 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 26 21:10:05 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 26 21:10:05 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 26 21:10:05 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 26 21:10:05 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 26 21:10:05 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 26 21:10:05 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 26 21:10:05 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 26 21:10:05 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 26 21:10:05 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 26 21:10:05 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 26 21:10:05 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 26 21:10:05 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 26 21:10:05 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 26 21:10:05 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 26 21:10:05 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=d6a4002d-fcf3-4b0b-8dec-ac0a764030af nomdmonddf nomdmonisw
Jul 26 21:10:05 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 26 21:10:05 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 26 21:10:05 node-1 kernel: [    0.000000] Checking aperture...
Jul 26 21:10:05 node-1 kernel: [    0.000000] No AGP bridge found
Jul 26 21:10:05 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 26 21:10:05 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 26 21:10:05 node-1 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 26 21:10:05 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 26 21:10:05 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 26 21:10:05 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 26 21:10:05 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 26 21:10:05 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 26 21:10:05 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 26 21:10:05 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 26 21:10:05 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 26 21:10:05 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 26 21:10:05 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 26 21:10:05 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 26 21:10:05 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 26 21:10:05 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 26 21:10:05 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 26 21:10:05 node-1 kernel: [    0.004000] tsc: Detected 3492.228 MHz processor
Jul 26 21:10:05 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.45 BogoMIPS (lpj=13968912)
Jul 26 21:10:05 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 26 21:10:05 node-1 kernel: [    0.000042] Security Framework initialized
Jul 26 21:10:05 node-1 kernel: [    0.000060] AppArmor: AppArmor initialized
Jul 26 21:10:05 node-1 kernel: [    0.000062] Yama: becoming mindful.
Jul 26 21:10:05 node-1 kernel: [    0.001446] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 26 21:10:05 node-1 kernel: [    0.006346] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 26 21:10:05 node-1 kernel: [    0.008268] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 26 21:10:05 node-1 kernel: [    0.008296] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 26 21:10:05 node-1 kernel: [    0.008581] Initializing cgroup subsys memory
Jul 26 21:10:05 node-1 kernel: [    0.008589] Initializing cgroup subsys devices
Jul 26 21:10:05 node-1 kernel: [    0.008590] Initializing cgroup subsys freezer
Jul 26 21:10:05 node-1 kernel: [    0.008592] Initializing cgroup subsys blkio
Jul 26 21:10:05 node-1 kernel: [    0.008594] Initializing cgroup subsys perf_event
Jul 26 21:10:05 node-1 kernel: [    0.008596] Initializing cgroup subsys hugetlb
Jul 26 21:10:05 node-1 kernel: [    0.008615] CPU: Physical Processor ID: 0
Jul 26 21:10:05 node-1 kernel: [    0.008617] CPU: Processor Core ID: 0
Jul 26 21:10:05 node-1 kernel: [    0.008620] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 26 21:10:05 node-1 kernel: [    0.008620] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 26 21:10:05 node-1 kernel: [    0.009314] mce: CPU supports 22 MCE banks
Jul 26 21:10:05 node-1 kernel: [    0.009341] CPU0: Thermal monitoring enabled (TM1)
Jul 26 21:10:05 node-1 kernel: [    0.009362] process: using mwait in idle threads
Jul 26 21:10:05 node-1 kernel: [    0.009365] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 26 21:10:05 node-1 kernel: [    0.009365] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 26 21:10:05 node-1 kernel: [    0.009365] tlb_flushall_shift: 6
Jul 26 21:10:05 node-1 kernel: [    0.009453] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 26 21:10:05 node-1 kernel: [    0.010176] ACPI: Core revision 20131115
Jul 26 21:10:05 node-1 kernel: [    0.022844] ACPI: All ACPI Tables successfully acquired
Jul 26 21:10:05 node-1 kernel: [    0.023005] ftrace: allocating 28617 entries in 112 pages
Jul 26 21:10:05 node-1 kernel: [    0.031817] dmar: Host address width 46
Jul 26 21:10:05 node-1 kernel: [    0.031819] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 26 21:10:05 node-1 kernel: [    0.031825] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 26 21:10:05 node-1 kernel: [    0.031827] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 26 21:10:05 node-1 kernel: [    0.031831] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 26 21:10:05 node-1 kernel: [    0.031833] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 26 21:10:05 node-1 kernel: [    0.031834] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 26 21:10:05 node-1 kernel: [    0.031835] dmar: ATSR flags: 0x0
Jul 26 21:10:05 node-1 kernel: [    0.031836] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 26 21:10:05 node-1 kernel: [    0.031837] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 26 21:10:05 node-1 kernel: [    0.031953] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 26 21:10:05 node-1 kernel: [    0.031954] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 26 21:10:05 node-1 kernel: [    0.031955] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 26 21:10:05 node-1 kernel: [    0.031956] HPET id 0 under DRHD base 0xc7ffc000
Jul 26 21:10:05 node-1 kernel: [    0.031957] Your BIOS is broken and requested that x2apic be disabled.
Jul 26 21:10:05 node-1 kernel: [    0.031957] This will slightly decrease performance.
Jul 26 21:10:05 node-1 kernel: [    0.031957] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 26 21:10:05 node-1 kernel: [    0.032388] Enabled IRQ remapping in xapic mode
Jul 26 21:10:05 node-1 kernel: [    0.032389] x2apic not enabled, IRQ remapping is in xapic mode
Jul 26 21:10:05 node-1 kernel: [    0.032393] Switched APIC routing to physical flat.
Jul 26 21:10:05 node-1 kernel: [    0.033022] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 26 21:10:05 node-1 kernel: [    0.072675] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 26 21:10:05 node-1 kernel: [    0.072681] TSC deadline timer enabled
Jul 26 21:10:05 node-1 kernel: [    0.072689] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 26 21:10:05 node-1 kernel: [    0.072695] ... version:                3
Jul 26 21:10:05 node-1 kernel: [    0.072695] ... bit width:              48
Jul 26 21:10:05 node-1 kernel: [    0.072696] ... generic registers:      4
Jul 26 21:10:05 node-1 kernel: [    0.072697] ... value mask:             0000ffffffffffff
Jul 26 21:10:05 node-1 kernel: [    0.072698] ... max period:             0000ffffffffffff
Jul 26 21:10:05 node-1 kernel: [    0.072699] ... fixed-purpose events:   3
Jul 26 21:10:05 node-1 kernel: [    0.072700] ... event mask:             000000070000000f
Jul 26 21:10:05 node-1 kernel: [    0.074105] x86: Booting SMP configuration:
Jul 26 21:10:05 node-1 kernel: [    0.088210] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 26 21:10:05 node-1 kernel: [    0.074107] .... node  #0, CPUs:        #1  #2  #3
Jul 26 21:10:05 node-1 kernel: [    0.116120] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 26 21:10:05 node-1 kernel: [    0.270287] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 26 21:10:05 node-1 kernel: [    0.325909] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 26 21:10:05 node-1 kernel: [    0.382762] x86: Booted up 2 nodes, 16 CPUs
Jul 26 21:10:05 node-1 kernel: [    0.382766] smpboot: Total of 16 processors activated (111763.86 BogoMIPS)
Jul 26 21:10:05 node-1 kernel: [    0.406582] devtmpfs: initialized
Jul 26 21:10:05 node-1 kernel: [    0.409668] EVM: security.selinux
Jul 26 21:10:05 node-1 kernel: [    0.409669] EVM: security.SMACK64
Jul 26 21:10:05 node-1 kernel: [    0.409670] EVM: security.ima
Jul 26 21:10:05 node-1 kernel: [    0.409671] EVM: security.capability
Jul 26 21:10:05 node-1 kernel: [    0.409722] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 26 21:10:05 node-1 kernel: [    0.410407] pinctrl core: initialized pinctrl subsystem
Jul 26 21:10:05 node-1 kernel: [    0.410466] regulator-dummy: no parameters
Jul 26 21:10:05 node-1 kernel: [    0.410496] RTC time: 21:09:28, date: 07/26/16
Jul 26 21:10:05 node-1 kernel: [    0.410530] NET: Registered protocol family 16
Jul 26 21:10:05 node-1 kernel: [    0.410614] cpuidle: using governor ladder
Jul 26 21:10:05 node-1 kernel: [    0.410616] cpuidle: using governor menu
Jul 26 21:10:05 node-1 kernel: [    0.410649] ACPI: bus type PCI registered
Jul 26 21:10:05 node-1 kernel: [    0.410650] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 26 21:10:05 node-1 kernel: [    0.410697] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 26 21:10:05 node-1 kernel: [    0.410700] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 26 21:10:05 node-1 kernel: [    0.424434] PCI: Using configuration type 1 for base access
Jul 26 21:10:05 node-1 kernel: [    0.425428] bio: create slab <bio-0> at 0
Jul 26 21:10:05 node-1 kernel: [    0.425716] ACPI: Added _OSI(Module Device)
Jul 26 21:10:05 node-1 kernel: [    0.425717] ACPI: Added _OSI(Processor Device)
Jul 26 21:10:05 node-1 kernel: [    0.425718] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 26 21:10:05 node-1 kernel: [    0.425719] ACPI: Added _OSI(Processor Aggregator Device)
Jul 26 21:10:05 node-1 kernel: [    0.438341] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 26 21:10:05 node-1 kernel: [    0.448839] ACPI: Interpreter enabled
Jul 26 21:10:05 node-1 kernel: [    0.448845] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 26 21:10:05 node-1 kernel: [    0.448849] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 26 21:10:05 node-1 kernel: [    0.448851] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 26 21:10:05 node-1 kernel: [    0.448858] ACPI: (supports S0 S4 S5)
Jul 26 21:10:05 node-1 kernel: [    0.448859] ACPI: Using IOAPIC for interrupt routing
Jul 26 21:10:05 node-1 kernel: [    0.448900] HEST: Table parsing has been initialized.
Jul 26 21:10:05 node-1 kernel: [    0.448903] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 26 21:10:05 node-1 kernel: [    0.449453] ACPI: No dock devices found.
Jul 26 21:10:05 node-1 kernel: [    0.461072] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 26 21:10:05 node-1 kernel: [    0.461077] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 21:10:05 node-1 kernel: [    0.461080] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 26 21:10:05 node-1 kernel: [    0.461109] PCI host bridge to bus 0000:ff
Jul 26 21:10:05 node-1 kernel: [    0.461111] pci_bus 0000:ff: root bus resource [bus ff]
Jul 26 21:10:05 node-1 kernel: [    0.461119] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461158] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 26 21:10:05 node-1 kernel: [    0.461188] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461224] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461254] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 26 21:10:05 node-1 kernel: [    0.461283] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 26 21:10:05 node-1 kernel: [    0.461315] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461344] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461374] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461402] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461429] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461455] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461483] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461509] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461535] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461562] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461591] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461618] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461644] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 26 21:10:05 node-1 kernel: [    0.461672] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461698] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 26 21:10:05 node-1 kernel: [    0.461724] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461750] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461780] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 26 21:10:05 node-1 kernel: [    0.461814] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461845] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461875] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461905] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461936] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.461968] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462000] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462030] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462060] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462093] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462125] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462157] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462190] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462219] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462246] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462277] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462312] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462352] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462387] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462420] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462451] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462482] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462512] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462540] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462571] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462602] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462634] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462663] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462693] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462722] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462752] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462783] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462815] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462873] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 26 21:10:05 node-1 kernel: [    0.462875] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 21:10:05 node-1 kernel: [    0.462878] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 26 21:10:05 node-1 kernel: [    0.462896] PCI host bridge to bus 0000:7f
Jul 26 21:10:05 node-1 kernel: [    0.462898] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 26 21:10:05 node-1 kernel: [    0.462903] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462931] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 26 21:10:05 node-1 kernel: [    0.462959] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.462989] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463011] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 26 21:10:05 node-1 kernel: [    0.463036] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 26 21:10:05 node-1 kernel: [    0.463062] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463089] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463111] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463137] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463163] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463188] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463213] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463235] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463259] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463286] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463308] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463331] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463353] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 26 21:10:05 node-1 kernel: [    0.463377] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463399] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 26 21:10:05 node-1 kernel: [    0.463421] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463444] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463470] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 26 21:10:05 node-1 kernel: [    0.463504] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463531] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463558] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463586] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463611] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463638] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463663] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463691] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463716] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463745] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463773] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463801] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463830] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463855] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463879] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463909] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463934] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463963] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.463993] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.464022] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.464048] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.464074] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.464099] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.464128] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.464157] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.464184] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.464214] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.464241] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.464264] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.464290] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.464316] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.464345] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.464372] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.465626] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 26 21:10:05 node-1 kernel: [    0.465630] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 21:10:05 node-1 kernel: [    0.466749] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 26 21:10:05 node-1 kernel: [    0.467267] PCI host bridge to bus 0000:00
Jul 26 21:10:05 node-1 kernel: [    0.467269] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 26 21:10:05 node-1 kernel: [    0.467271] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 26 21:10:05 node-1 kernel: [    0.467272] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 26 21:10:05 node-1 kernel: [    0.467273] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 26 21:10:05 node-1 kernel: [    0.467275] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 26 21:10:05 node-1 kernel: [    0.467276] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 26 21:10:05 node-1 kernel: [    0.467277] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 26 21:10:05 node-1 kernel: [    0.467283] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 26 21:10:05 node-1 kernel: [    0.467366] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 26 21:10:05 node-1 kernel: [    0.467397] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:05 node-1 kernel: [    0.467438] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 26 21:10:05 node-1 kernel: [    0.467458] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 26 21:10:05 node-1 kernel: [    0.467487] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:05 node-1 kernel: [    0.467527] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 26 21:10:05 node-1 kernel: [    0.467547] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 26 21:10:05 node-1 kernel: [    0.467576] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:05 node-1 kernel: [    0.467619] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 26 21:10:05 node-1 kernel: [    0.467635] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.467705] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.467783] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.467860] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 26 21:10:05 node-1 kernel: [    0.467865] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 26 21:10:05 node-1 kernel: [    0.467951] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 26 21:10:05 node-1 kernel: [    0.468099] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 26 21:10:05 node-1 kernel: [    0.468117] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 26 21:10:05 node-1 kernel: [    0.468195] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:05 node-1 kernel: [    0.468248] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 26 21:10:05 node-1 kernel: [    0.468270] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 26 21:10:05 node-1 kernel: [    0.468325] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:05 node-1 kernel: [    0.468368] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 26 21:10:05 node-1 kernel: [    0.468397] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 26 21:10:05 node-1 kernel: [    0.468452] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 26 21:10:05 node-1 kernel: [    0.468495] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 26 21:10:05 node-1 kernel: [    0.468520] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 26 21:10:05 node-1 kernel: [    0.468538] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 26 21:10:05 node-1 kernel: [    0.468615] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:05 node-1 kernel: [    0.468664] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 26 21:10:05 node-1 kernel: [    0.468694] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 26 21:10:05 node-1 kernel: [    0.468943] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 26 21:10:05 node-1 kernel: [    0.468949] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 26 21:10:05 node-1 kernel: [    0.468955] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 26 21:10:05 node-1 kernel: [    0.468961] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 26 21:10:05 node-1 kernel: [    0.468968] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 26 21:10:05 node-1 kernel: [    0.468998] pci 0000:01:00.0: supports D1 D2
Jul 26 21:10:05 node-1 kernel: [    0.475151] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 26 21:10:05 node-1 kernel: [    0.475158] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 26 21:10:05 node-1 kernel: [    0.475162] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 26 21:10:05 node-1 kernel: [    0.475425] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 26 21:10:05 node-1 kernel: [    0.475458] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 26 21:10:05 node-1 kernel: [    0.483150] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 26 21:10:05 node-1 kernel: [    0.483153] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:05 node-1 kernel: [    0.483154] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 21:10:05 node-1 kernel: [    0.483209] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 26 21:10:05 node-1 kernel: [    0.483278] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 26 21:10:05 node-1 kernel: [    0.483354] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:05 node-1 kernel: [    0.483400] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 26 21:10:05 node-1 kernel: [    0.483403] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:05 node-1 kernel: [    0.483405] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 21:10:05 node-1 kernel: [    0.483458] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 26 21:10:05 node-1 kernel: [    0.483584] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:05 node-1 kernel: [    0.483637] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 26 21:10:05 node-1 kernel: [    0.483640] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:05 node-1 kernel: [    0.483642] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 21:10:05 node-1 kernel: [    0.483701] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 26 21:10:05 node-1 kernel: [    0.483821] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:05 node-1 kernel: [    0.483861] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 26 21:10:05 node-1 kernel: [    0.483983] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:05 node-1 kernel: [    0.484019] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 26 21:10:05 node-1 kernel: [    0.484138] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:05 node-1 kernel: [    0.484174] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 26 21:10:05 node-1 kernel: [    0.484293] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:05 node-1 kernel: [    0.484334] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 26 21:10:05 node-1 kernel: [    0.484336] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:05 node-1 kernel: [    0.484338] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 21:10:05 node-1 kernel: [    0.484398] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 26 21:10:05 node-1 kernel: [    0.484464] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 26 21:10:05 node-1 kernel: [    0.484516] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 26 21:10:05 node-1 kernel: [    0.484557] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 26 21:10:05 node-1 kernel: [    0.484639] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 26 21:10:05 node-1 kernel: [    0.484763] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 26 21:10:05 node-1 kernel: [    0.484765] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:05 node-1 kernel: [    0.484767] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 26 21:10:05 node-1 kernel: [    0.484823] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 26 21:10:05 node-1 kernel: [    0.484880] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 26 21:10:05 node-1 kernel: [    0.484929] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 26 21:10:05 node-1 kernel: [    0.485144] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 26 21:10:05 node-1 kernel: [    0.485148] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 26 21:10:05 node-1 kernel: [    0.485210] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 26 21:10:05 node-1 kernel: [    0.485263] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 26 21:10:05 node-1 kernel: [    0.485311] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 26 21:10:05 node-1 kernel: [    0.485520] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 26 21:10:05 node-1 kernel: [    0.485524] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 26 21:10:05 node-1 kernel: [    0.485582] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 26 21:10:05 node-1 kernel: [    0.485642] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 26 21:10:05 node-1 kernel: [    0.485719] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 26 21:10:05 node-1 kernel: [    0.485939] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 26 21:10:05 node-1 kernel: [    0.485943] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 26 21:10:05 node-1 kernel: [    0.486120] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 26 21:10:05 node-1 kernel: [    0.486157] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 26 21:10:05 node-1 kernel: [    0.486231] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 26 21:10:05 node-1 kernel: [    0.486250] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 26 21:10:05 node-1 kernel: [    0.486263] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 26 21:10:05 node-1 kernel: [    0.486276] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 26 21:10:05 node-1 kernel: [    0.486326] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 26 21:10:05 node-1 kernel: [    0.491163] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 26 21:10:05 node-1 kernel: [    0.491172] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 26 21:10:05 node-1 kernel: [    0.491224] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 26 21:10:05 node-1 kernel: [    0.491712] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 26 21:10:05 node-1 kernel: [    0.491715] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 21:10:05 node-1 kernel: [    0.491839] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 26 21:10:05 node-1 kernel: [    0.491943] PCI host bridge to bus 0000:80
Jul 26 21:10:05 node-1 kernel: [    0.491945] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 26 21:10:05 node-1 kernel: [    0.491947] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 26 21:10:05 node-1 kernel: [    0.491948] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 26 21:10:05 node-1 kernel: [    0.491956] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.492018] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.492085] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 26 21:10:05 node-1 kernel: [    0.492146] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 26 21:10:05 node-1 kernel: [    0.492151] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 26 21:10:05 node-1 kernel: [    0.492223] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 26 21:10:05 node-1 kernel: [    0.492521] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 26 21:10:05 node-1 kernel: [    0.492553] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 26 21:10:05 node-1 kernel: [    0.492582] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 26 21:10:05 node-1 kernel: [    0.492611] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 26 21:10:05 node-1 kernel: [    0.492641] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 21:10:05 node-1 kernel: [    0.492671] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 21:10:05 node-1 kernel: [    0.492700] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 21:10:05 node-1 kernel: [    0.492730] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 21:10:05 node-1 kernel: [    0.492815] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 26 21:10:05 node-1 kernel: [    0.492819] ACPI: \_SB_.UNC1: notify handler is installed
Jul 26 21:10:05 node-1 kernel: [    0.492820] ACPI: \_SB_.UNC0: notify handler is installed
Jul 26 21:10:05 node-1 kernel: [    0.492835] ACPI: \_SB_.PCI0: notify handler is installed
Jul 26 21:10:05 node-1 kernel: [    0.492888] ACPI: \_SB_.PCI1: notify handler is installed
Jul 26 21:10:05 node-1 kernel: [    0.492968] Found 4 acpi root devices
Jul 26 21:10:05 node-1 kernel: [    0.493073] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 26 21:10:05 node-1 kernel: [    0.493075] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 26 21:10:05 node-1 kernel: [    0.493076] vgaarb: loaded
Jul 26 21:10:05 node-1 kernel: [    0.493077] vgaarb: bridge control possible 0000:0c:00.0
Jul 26 21:10:05 node-1 kernel: [    0.493190] SCSI subsystem initialized
Jul 26 21:10:05 node-1 kernel: [    0.493254] libata version 3.00 loaded.
Jul 26 21:10:05 node-1 kernel: [    0.493268] ACPI: bus type USB registered
Jul 26 21:10:05 node-1 kernel: [    0.493278] usbcore: registered new interface driver usbfs
Jul 26 21:10:05 node-1 kernel: [    0.493283] usbcore: registered new interface driver hub
Jul 26 21:10:05 node-1 kernel: [    0.493307] usbcore: registered new device driver usb
Jul 26 21:10:05 node-1 kernel: [    0.493474] PCI: Using ACPI for IRQ routing
Jul 26 21:10:05 node-1 kernel: [    0.497069] PCI: pci_cache_line_size set to 64 bytes
Jul 26 21:10:05 node-1 kernel: [    0.497270] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 26 21:10:05 node-1 kernel: [    0.497271] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 26 21:10:05 node-1 kernel: [    0.497272] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 26 21:10:05 node-1 kernel: [    0.497336] NetLabel: Initializing
Jul 26 21:10:05 node-1 kernel: [    0.497337] NetLabel:  domain hash size = 128
Jul 26 21:10:05 node-1 kernel: [    0.497338] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 26 21:10:05 node-1 kernel: [    0.497348] NetLabel:  unlabeled traffic allowed by default
Jul 26 21:10:05 node-1 kernel: [    0.497403] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 26 21:10:05 node-1 kernel: [    0.497407] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 26 21:10:05 node-1 kernel: [    0.499476] Switched to clocksource hpet
Jul 26 21:10:05 node-1 kernel: [    0.504017] AppArmor: AppArmor Filesystem Enabled
Jul 26 21:10:05 node-1 kernel: [    0.504055] pnp: PnP ACPI init
Jul 26 21:10:05 node-1 kernel: [    0.504067] ACPI: bus type PNP registered
Jul 26 21:10:05 node-1 kernel: [    0.504243] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 26 21:10:05 node-1 kernel: [    0.504254] pnp 00:01: [dma 4]
Jul 26 21:10:05 node-1 kernel: [    0.504273] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 26 21:10:05 node-1 kernel: [    0.504307] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 26 21:10:05 node-1 kernel: [    0.504332] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 26 21:10:05 node-1 kernel: [    0.504353] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 26 21:10:05 node-1 kernel: [    0.504401] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 26 21:10:05 node-1 kernel: [    0.504513] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 26 21:10:05 node-1 kernel: [    0.504515] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 26 21:10:05 node-1 kernel: [    0.504517] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 26 21:10:05 node-1 kernel: [    0.504518] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 26 21:10:05 node-1 kernel: [    0.504520] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 26 21:10:05 node-1 kernel: [    0.504521] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 26 21:10:05 node-1 kernel: [    0.504525] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 26 21:10:05 node-1 kernel: [    0.504526] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 26 21:10:05 node-1 kernel: [    0.504528] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 26 21:10:05 node-1 kernel: [    0.504530] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 26 21:10:05 node-1 kernel: [    0.504531] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 26 21:10:05 node-1 kernel: [    0.504533] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 26 21:10:05 node-1 kernel: [    0.504534] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 26 21:10:05 node-1 kernel: [    0.504537] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 26 21:10:05 node-1 kernel: [    0.504638] pnp 00:07: [dma 0 disabled]
Jul 26 21:10:05 node-1 kernel: [    0.504671] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 26 21:10:05 node-1 kernel: [    0.504752] pnp 00:08: [dma 0 disabled]
Jul 26 21:10:05 node-1 kernel: [    0.504791] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 26 21:10:05 node-1 kernel: [    0.504849] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 26 21:10:05 node-1 kernel: [    0.505294] pnp: PnP ACPI: found 10 devices
Jul 26 21:10:05 node-1 kernel: [    0.505296] ACPI: bus type PNP unregistered
Jul 26 21:10:05 node-1 kernel: [    0.511336] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 26 21:10:05 node-1 kernel: [    0.511339] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 26 21:10:05 node-1 kernel: [    0.511342] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 26 21:10:05 node-1 kernel: [    0.511348] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 26 21:10:05 node-1 kernel: [    0.511349] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:05 node-1 kernel: [    0.511368] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 26 21:10:05 node-1 kernel: [    0.511397] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 26 21:10:05 node-1 kernel: [    0.511412] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 26 21:10:05 node-1 kernel: [    0.511440] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 26 21:10:05 node-1 kernel: [    0.511459] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 26 21:10:05 node-1 kernel: [    0.511488] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 26 21:10:05 node-1 kernel: [    0.511502] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 26 21:10:05 node-1 kernel: [    0.511531] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 26 21:10:05 node-1 kernel: [    0.511533] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:05 node-1 kernel: [    0.511548] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 21:10:05 node-1 kernel: [    0.511577] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 26 21:10:05 node-1 kernel: [    0.511579] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:05 node-1 kernel: [    0.511593] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 21:10:05 node-1 kernel: [    0.511622] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 26 21:10:05 node-1 kernel: [    0.511624] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:05 node-1 kernel: [    0.511627] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 21:10:05 node-1 kernel: [    0.511632] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 26 21:10:05 node-1 kernel: [    0.511634] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:05 node-1 kernel: [    0.511636] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 21:10:05 node-1 kernel: [    0.511641] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 26 21:10:05 node-1 kernel: [    0.511647] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 26 21:10:05 node-1 kernel: [    0.511656] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 26 21:10:05 node-1 kernel: [    0.511659] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 26 21:10:05 node-1 kernel: [    0.511666] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 26 21:10:05 node-1 kernel: [    0.511667] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 26 21:10:05 node-1 kernel: [    0.511668] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 26 21:10:05 node-1 kernel: [    0.511669] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 26 21:10:05 node-1 kernel: [    0.511670] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 26 21:10:05 node-1 kernel: [    0.511671] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 26 21:10:05 node-1 kernel: [    0.511672] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 26 21:10:05 node-1 kernel: [    0.511673] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 26 21:10:05 node-1 kernel: [    0.511674] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 26 21:10:05 node-1 kernel: [    0.511675] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 26 21:10:05 node-1 kernel: [    0.511676] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 26 21:10:05 node-1 kernel: [    0.511677] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 26 21:10:05 node-1 kernel: [    0.511678] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 26 21:10:05 node-1 kernel: [    0.511679] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 26 21:10:05 node-1 kernel: [    0.511680] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 26 21:10:05 node-1 kernel: [    0.511681] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 26 21:10:05 node-1 kernel: [    0.511682] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 26 21:10:05 node-1 kernel: [    0.511683] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 26 21:10:05 node-1 kernel: [    0.511684] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 26 21:10:05 node-1 kernel: [    0.511685] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 26 21:10:05 node-1 kernel: [    0.511686] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 26 21:10:05 node-1 kernel: [    0.511688] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 26 21:10:05 node-1 kernel: [    0.511690] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 26 21:10:05 node-1 kernel: [    0.511691] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 26 21:10:05 node-1 kernel: [    0.511731] NET: Registered protocol family 2
Jul 26 21:10:05 node-1 kernel: [    0.512031] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 26 21:10:05 node-1 kernel: [    0.512401] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 26 21:10:05 node-1 kernel: [    0.512568] TCP: Hash tables configured (established 262144 bind 65536)
Jul 26 21:10:05 node-1 kernel: [    0.512609] TCP: reno registered
Jul 26 21:10:05 node-1 kernel: [    0.512649] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 26 21:10:05 node-1 kernel: [    0.512755] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 26 21:10:05 node-1 kernel: [    0.512916] NET: Registered protocol family 1
Jul 26 21:10:05 node-1 kernel: [    0.551565] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 26 21:10:05 node-1 kernel: [    0.551580] PCI: CLS 64 bytes, default 64
Jul 26 21:10:05 node-1 kernel: [    0.551663] Trying to unpack rootfs image as initramfs...
Jul 26 21:10:05 node-1 kernel: [    0.773438] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 26 21:10:05 node-1 kernel: [    0.773494] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 26 21:10:05 node-1 kernel: [    0.773504] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 26 21:10:05 node-1 kernel: [    0.774012] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:05 node-1 kernel: [    0.774019] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:05 node-1 kernel: [    0.774026] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:05 node-1 kernel: [    0.774033] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:05 node-1 kernel: [    0.774042] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:05 node-1 kernel: [    0.774050] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:05 node-1 kernel: [    0.774061] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:05 node-1 kernel: [    0.774069] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:05 node-1 kernel: [    0.774078] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:05 node-1 kernel: [    0.774085] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:05 node-1 kernel: [    0.774092] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:05 node-1 kernel: [    0.774098] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:05 node-1 kernel: [    0.774105] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:05 node-1 kernel: [    0.774113] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:05 node-1 kernel: [    0.774119] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:05 node-1 kernel: [    0.774126] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:05 node-1 kernel: [    0.774181] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 26 21:10:05 node-1 kernel: [    0.774185] Scanning for low memory corruption every 60 seconds
Jul 26 21:10:05 node-1 kernel: [    0.774523] Initialise system trusted keyring
Jul 26 21:10:05 node-1 kernel: [    0.774570] audit: initializing netlink socket (disabled)
Jul 26 21:10:05 node-1 kernel: [    0.774582] type=2000 audit(1469567367.728:1): initialized
Jul 26 21:10:05 node-1 kernel: [    0.792358] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 26 21:10:05 node-1 kernel: [    0.793794] zbud: loaded
Jul 26 21:10:05 node-1 kernel: [    0.793905] VFS: Disk quotas dquot_6.5.2
Jul 26 21:10:05 node-1 kernel: [    0.793936] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 26 21:10:05 node-1 kernel: [    0.794285] fuse init (API version 7.22)
Jul 26 21:10:05 node-1 kernel: [    0.794340] msgmni has been set to 32768
Jul 26 21:10:05 node-1 kernel: [    0.794387] Key type big_key registered
Jul 26 21:10:05 node-1 kernel: [    0.794833] Key type asymmetric registered
Jul 26 21:10:05 node-1 kernel: [    0.794834] Asymmetric key parser 'x509' registered
Jul 26 21:10:05 node-1 kernel: [    0.794854] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 26 21:10:05 node-1 kernel: [    0.794906] io scheduler noop registered
Jul 26 21:10:05 node-1 kernel: [    0.794908] io scheduler deadline registered (default)
Jul 26 21:10:05 node-1 kernel: [    0.794926] io scheduler cfq registered
Jul 26 21:10:05 node-1 kernel: [    0.795241] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    0.795339] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    0.795428] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    0.795515] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    0.795610] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    0.795674] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    0.795941] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 26 21:10:05 node-1 kernel: [    0.795960] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 26 21:10:05 node-1 kernel: [    0.795980] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 26 21:10:05 node-1 kernel: [    0.795991] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.795993] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.795995] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 26 21:10:05 node-1 kernel: [    0.795999] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.796000] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.796002] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.796003] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.796004] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.796006] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.796007] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.796009] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.796010] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.796012] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.796013] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.796014] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.796017] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 26 21:10:05 node-1 kernel: [    0.796021] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.796023] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 26 21:10:05 node-1 kernel: [    0.796033] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.796036] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 26 21:10:05 node-1 kernel: [    0.796048] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.796050] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:05 node-1 kernel: [    0.796052] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 26 21:10:05 node-1 kernel: [    0.796064] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 26 21:10:05 node-1 kernel: [    0.796100] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 26 21:10:05 node-1 kernel: [    0.796104] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 26 21:10:05 node-1 kernel: [    0.796112] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 26 21:10:05 node-1 kernel: [    0.796147] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 26 21:10:05 node-1 kernel: [    0.796149] vesafb: scrolling: redraw
Jul 26 21:10:05 node-1 kernel: [    0.796150] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 26 21:10:05 node-1 kernel: [    0.815756] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 26 21:10:05 node-1 kernel: [    0.824261] Console: switching to colour frame buffer device 80x30
Jul 26 21:10:05 node-1 kernel: [    0.832942] fb0: VESA VGA frame buffer device
Jul 26 21:10:05 node-1 kernel: [    0.833139] intel_idle: MWAIT substates: 0x2120
Jul 26 21:10:05 node-1 kernel: [    0.833140] intel_idle: v0.4 model 0x3F
Jul 26 21:10:05 node-1 kernel: [    0.833140] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 26 21:10:05 node-1 kernel: [    0.833359] ipmi message handler version 39.2
Jul 26 21:10:05 node-1 kernel: [    0.833616] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 26 21:10:05 node-1 kernel: [    0.834047] ACPI: AC Adapter [P111] (on-line)
Jul 26 21:10:05 node-1 kernel: [    0.839280] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 26 21:10:05 node-1 kernel: [    0.850311] ACPI: Power Button [PWRB]
Jul 26 21:10:05 node-1 kernel: [    0.856106] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 26 21:10:05 node-1 kernel: [    0.867885] ACPI: Power Button [PWRF]
Jul 26 21:10:05 node-1 kernel: [    0.888965] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 26 21:10:05 node-1 kernel: [    0.900649] pstore: Registered erst as persistent store backend
Jul 26 21:10:05 node-1 kernel: [    0.906846] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 26 21:10:05 node-1 kernel: [    0.918782] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 26 21:10:05 node-1 kernel: [    0.945538] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 26 21:10:05 node-1 kernel: [    0.978830] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 26 21:10:05 node-1 kernel: [    0.992894] Linux agpgart interface v0.103
Jul 26 21:10:05 node-1 kernel: [    1.000561] brd: module loaded
Jul 26 21:10:05 node-1 kernel: [    1.007725] loop: module loaded
Jul 26 21:10:05 node-1 kernel: [    1.014434] libphy: Fixed MDIO Bus: probed
Jul 26 21:10:05 node-1 kernel: [    1.020910] tun: Universal TUN/TAP device driver, 1.6
Jul 26 21:10:05 node-1 kernel: [    1.027396] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 26 21:10:05 node-1 kernel: [    1.033988] PPP generic driver version 2.4.2
Jul 26 21:10:05 node-1 kernel: [    1.040456] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 26 21:10:05 node-1 kernel: [    1.046896] ehci-pci: EHCI PCI platform driver
Jul 26 21:10:05 node-1 kernel: [    1.053413] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 26 21:10:05 node-1 kernel: [    1.059818] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 26 21:10:05 node-1 kernel: [    1.072331] ehci-pci 0000:00:1a.0: debug port 2
Jul 26 21:10:05 node-1 kernel: [    1.082523] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 26 21:10:05 node-1 kernel: [    1.082540] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 26 21:10:05 node-1 kernel: [    1.098960] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 26 21:10:05 node-1 kernel: [    1.105016] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 26 21:10:05 node-1 kernel: [    1.111175] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 26 21:10:05 node-1 kernel: [    1.123056] usb usb1: Product: EHCI Host Controller
Jul 26 21:10:05 node-1 kernel: [    1.129075] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 26 21:10:05 node-1 kernel: [    1.135110] usb usb1: SerialNumber: 0000:00:1a.0
Jul 26 21:10:05 node-1 kernel: [    1.141064] hub 1-0:1.0: USB hub found
Jul 26 21:10:05 node-1 kernel: [    1.146837] hub 1-0:1.0: 2 ports detected
Jul 26 21:10:05 node-1 kernel: [    1.152625] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 26 21:10:05 node-1 kernel: [    1.158217] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 26 21:10:05 node-1 kernel: [    1.169212] ehci-pci 0000:00:1d.0: debug port 2
Jul 26 21:10:05 node-1 kernel: [    1.178506] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 26 21:10:05 node-1 kernel: [    1.178509] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 26 21:10:05 node-1 kernel: [    1.194878] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 26 21:10:05 node-1 kernel: [    1.200086] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 26 21:10:05 node-1 kernel: [    1.205391] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 26 21:10:05 node-1 kernel: [    1.215966] usb usb2: Product: EHCI Host Controller
Jul 26 21:10:05 node-1 kernel: [    1.221432] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 26 21:10:05 node-1 kernel: [    1.226987] usb usb2: SerialNumber: 0000:00:1d.0
Jul 26 21:10:05 node-1 kernel: [    1.232527] hub 2-0:1.0: USB hub found
Jul 26 21:10:05 node-1 kernel: [    1.237879] hub 2-0:1.0: 2 ports detected
Jul 26 21:10:05 node-1 kernel: [    1.243165] ehci-platform: EHCI generic platform driver
Jul 26 21:10:05 node-1 kernel: [    1.248407] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 26 21:10:05 node-1 kernel: [    1.253717] ohci-pci: OHCI PCI platform driver
Jul 26 21:10:05 node-1 kernel: [    1.259038] ohci-platform: OHCI generic platform driver
Jul 26 21:10:05 node-1 kernel: [    1.264264] uhci_hcd: USB Universal Host Controller Interface driver
Jul 26 21:10:05 node-1 kernel: [    1.269642] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 26 21:10:05 node-1 kernel: [    1.462660] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 26 21:10:05 node-1 kernel: [    1.634801] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 26 21:10:05 node-1 kernel: [    1.640318] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 26 21:10:05 node-1 kernel: [    1.646069] hub 1-1:1.0: USB hub found
Jul 26 21:10:05 node-1 kernel: [    1.651537] hub 1-1:1.0: 6 ports detected
Jul 26 21:10:05 node-1 kernel: [    1.766392] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 26 21:10:05 node-1 kernel: [    1.794366] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 26 21:10:05 node-1 kernel: [    2.034462] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 26 21:10:05 node-1 kernel: [    2.040017] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 26 21:10:05 node-1 kernel: [    2.045856] hub 2-1:1.0: USB hub found
Jul 26 21:10:05 node-1 kernel: [    2.051573] hub 2-1:1.0: 8 ports detected
Jul 26 21:10:05 node-1 kernel: [    2.311128] i8042: No controller found
Jul 26 21:10:05 node-1 kernel: [    2.316552] mousedev: PS/2 mouse device common for all mice
Jul 26 21:10:05 node-1 kernel: [    2.322082] rtc_cmos 00:02: RTC can wake from S4
Jul 26 21:10:05 node-1 kernel: [    2.327673] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 26 21:10:05 node-1 kernel: [    2.329984] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 26 21:10:05 node-1 kernel: [    2.338791] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 26 21:10:05 node-1 kernel: [    2.349865] device-mapper: uevent: version 1.0.3
Jul 26 21:10:05 node-1 kernel: [    2.355487] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 26 21:10:05 node-1 kernel: [    2.366777] ledtrig-cpu: registered to indicate activity on CPUs
Jul 26 21:10:05 node-1 kernel: [    2.372731] TCP: cubic registered
Jul 26 21:10:05 node-1 kernel: [    2.378647] NET: Registered protocol family 10
Jul 26 21:10:05 node-1 kernel: [    2.384657] NET: Registered protocol family 17
Jul 26 21:10:05 node-1 kernel: [    2.390348] Key type dns_resolver registered
Jul 26 21:10:05 node-1 kernel: [    2.396360] Loading compiled-in X.509 certificates
Jul 26 21:10:05 node-1 kernel: [    2.402541] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 26 21:10:05 node-1 kernel: [    2.413960] registered taskstats version 1
Jul 26 21:10:05 node-1 kernel: [    2.421956] Key type trusted registered
Jul 26 21:10:05 node-1 kernel: [    2.429572] Key type encrypted registered
Jul 26 21:10:05 node-1 kernel: [    2.435036] AppArmor: AppArmor sha1 policy hashing enabled
Jul 26 21:10:05 node-1 kernel: [    2.440524] IMA: No TPM chip found, activating TPM-bypass!
Jul 26 21:10:05 node-1 kernel: [    2.446652] regulator-dummy: disabling
Jul 26 21:10:05 node-1 kernel: [    2.452215]   Magic number: 8:804:197
Jul 26 21:10:05 node-1 kernel: [    2.457708] acpi device:52: hash matches
Jul 26 21:10:05 node-1 kernel: [    2.462293] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 26 21:10:05 node-1 kernel: [    2.462294] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 26 21:10:05 node-1 kernel: [    2.462295] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 26 21:10:05 node-1 kernel: [    2.462296] usb 2-1.4: Manufacturer: Avocent
Jul 26 21:10:05 node-1 kernel: [    2.462296] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 26 21:10:05 node-1 kernel: [    2.496170] acpi PNP0100:00: hash matches
Jul 26 21:10:05 node-1 kernel: [    2.501828] rtc_cmos 00:02: setting system clock to 2016-07-26 21:09:30 UTC (1469567370)
Jul 26 21:10:05 node-1 kernel: [    2.514326] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 26 21:10:05 node-1 kernel: [    2.519963] EDD information not available.
Jul 26 21:10:05 node-1 kernel: [    2.525604] PM: Hibernation image not present or could not be loaded.
Jul 26 21:10:05 node-1 kernel: [    2.526471] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 26 21:10:05 node-1 kernel: [    2.537732] Write protecting the kernel read-only data: 12288k
Jul 26 21:10:05 node-1 kernel: [    2.543907] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 26 21:10:05 node-1 kernel: [    2.556318] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 26 21:10:05 node-1 kernel: [    2.589015] device-mapper: multipath: version 1.6.0 loaded
Jul 26 21:10:05 node-1 kernel: [    2.596944] systemd-udevd[218]: starting version 204
Jul 26 21:10:05 node-1 kernel: [    2.616938] md: linear personality registered for level -1
Jul 26 21:10:05 node-1 kernel: [    2.631459] md: multipath personality registered for level -4
Jul 26 21:10:05 node-1 kernel: [    2.639436] md: raid0 personality registered for level 0
Jul 26 21:10:05 node-1 kernel: [    2.647609] md: raid1 personality registered for level 1
Jul 26 21:10:05 node-1 kernel: [    2.657635] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 26 21:10:05 node-1 kernel: [    2.663976] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 26 21:10:05 node-1 kernel: [    2.663982] hidraw: raw HID events driver (C) Jiri Kosina
Jul 26 21:10:05 node-1 kernel: [    2.676193] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 26 21:10:05 node-1 kernel: [    2.676199] 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 26 21:10:05 node-1 kernel: [    2.676211] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 21:10:05 node-1 kernel: [    2.676729] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.676812] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.676949] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.677018] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.677290] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.696307] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 26 21:10:05 node-1 kernel: [    2.696309] 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 26 21:10:05 node-1 kernel: [    2.696310] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 21:10:05 node-1 kernel: [    2.696663] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.696844] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.696964] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.697116] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.697466] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.715872] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 26 21:10:05 node-1 kernel: [    2.715874] 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 26 21:10:05 node-1 kernel: [    2.715942] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 21:10:05 node-1 kernel: [    2.716361] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.716484] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.716577] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.716668] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.716911] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.721724] raid6: sse2x1   11381 MB/s
Jul 26 21:10:05 node-1 kernel: [    2.735210] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 26 21:10:05 node-1 kernel: [    2.735212] 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 26 21:10:05 node-1 kernel: [    2.735213] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 21:10:05 node-1 kernel: [    2.735611] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.735723] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.735798] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.735915] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.736327] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 21:10:05 node-1 kernel: [    2.789641] raid6: sse2x2   14404 MB/s
Jul 26 21:10:05 node-1 kernel: [    2.857554] raid6: sse2x4   16781 MB/s
Jul 26 21:10:05 node-1 kernel: [    2.884390] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 26 21:10:05 node-1 kernel: [    2.925416] raid6: avx2x1   18188 MB/s
Jul 26 21:10:05 node-1 kernel: [    2.997361] raid6: avx2x2   18860 MB/s
Jul 26 21:10:05 node-1 kernel: [    3.069299] raid6: avx2x4   21362 MB/s
Jul 26 21:10:05 node-1 kernel: [    3.075495] raid6: using algorithm avx2x4 (21362 MB/s)
Jul 26 21:10:05 node-1 kernel: [    3.081634] raid6: using avx2x2 recovery algorithm
Jul 26 21:10:05 node-1 kernel: [    3.087639] Switched to clocksource tsc
Jul 26 21:10:05 node-1 kernel: [    3.093540] megasas: FW now in Ready state
Jul 26 21:10:05 node-1 kernel: [    3.099289] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    3.099297] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    3.099303] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    3.099305] xor: automatically using best checksumming function:
Jul 26 21:10:05 node-1 kernel: [    3.099307] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    3.099334] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    3.099372] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    3.099410] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    3.099450] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    3.099488] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    3.099527] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    3.099555] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    3.099594] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    3.099626] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    3.099664] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    3.099699] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    3.099737] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Jul 26 21:10:05 node-1 kernel: [    3.099884] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 26 21:10:05 node-1 kernel: [    3.110128] usbcore: registered new interface driver usbhid
Jul 26 21:10:05 node-1 kernel: [    3.110151] usbhid: USB HID core driver
Jul 26 21:10:05 node-1 kernel: [    3.129085] 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 26 21:10:05 node-1 kernel: [    3.140690] 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 26 21:10:05 node-1 kernel: [    3.152400] 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 26 21:10:05 node-1 kernel: [    3.164530] 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 26 21:10:05 node-1 kernel: [    3.165238]    avx       : 36586.000 MB/sec
Jul 26 21:10:05 node-1 kernel: [    3.183346] 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 26 21:10:05 node-1 kernel: [    3.195817] async_tx: api initialized (async)
Jul 26 21:10:05 node-1 kernel: [    3.196033] 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 26 21:10:05 node-1 kernel: [    3.218516] md: raid6 personality registered for level 6
Jul 26 21:10:05 node-1 kernel: [    3.224997] md: raid5 personality registered for level 5
Jul 26 21:10:05 node-1 kernel: [    3.231461] md: raid4 personality registered for level 4
Jul 26 21:10:05 node-1 kernel: [    3.240743] md: raid10 personality registered for level 10
Jul 26 21:10:05 node-1 kernel: [    3.294859] multipathd (357): /proc/357/oom_adj is deprecated, please use /proc/357/oom_score_adj instead.
Jul 26 21:10:05 node-1 kernel: [    3.456997] megasas:IOC Init cmd success
Jul 26 21:10:05 node-1 kernel: [    3.508968] megasas: INIT adapter done
Jul 26 21:10:05 node-1 kernel: [    3.584898] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 26 21:10:05 node-1 kernel: [    3.591799] scsi0 : LSI SAS based MegaRAID driver
Jul 26 21:10:05 node-1 kernel: [    3.601288] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 26 21:10:05 node-1 kernel: [    3.620043] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 26 21:10:05 node-1 kernel: [    3.635586] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 26 21:10:05 node-1 kernel: [    3.642089] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 26 21:10:05 node-1 kernel: [    3.654800] sd 0:2:0:0: [sda] Write Protect is off
Jul 26 21:10:05 node-1 kernel: [    3.661001] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 26 21:10:05 node-1 kernel: [    3.661021] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 26 21:10:05 node-1 kernel: [    3.696317]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 26 21:10:05 node-1 kernel: [    3.702896] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 26 21:10:05 node-1 kernel: [    3.837762] random: lvm urandom read with 29 bits of entropy available
Jul 26 21:10:05 node-1 kernel: [    3.973835] bio: create slab <bio-1> at 1
Jul 26 21:10:05 node-1 kernel: [    4.810366] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 21:10:05 node-1 kernel: [    5.321862] init: plymouth-upstart-bridge main process (575) terminated with status 1
Jul 26 21:10:05 node-1 kernel: [    5.334346] init: plymouth-upstart-bridge main process ended, respawning
Jul 26 21:10:05 node-1 kernel: [    5.501584] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 26 21:10:05 node-1 kernel: [    5.529150] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 26 21:10:05 node-1 kernel: [    5.542436] random: nonblocking pool is initialized
Jul 26 21:10:05 node-1 kernel: [    5.641418] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 26 21:10:05 node-1 kernel: [    5.725218] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 26 21:10:05 node-1 kernel: [    5.777098] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 21:10:05 node-1 kernel: [    6.018527] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 26 21:10:05 node-1 kernel: [    6.057226] XFS (dm-1): Mounting Filesystem
Jul 26 21:10:05 node-1 kernel: [    6.347220] XFS (dm-1): Ending clean mount
Jul 26 21:10:05 node-1 kernel: [    6.399888] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 21:10:05 node-1 kernel: [    6.426590] XFS (dm-2): Mounting Filesystem
Jul 26 21:10:05 node-1 kernel: [    6.552444] XFS (dm-2): Ending clean mount
Jul 26 21:10:05 node-1 kernel: [    6.666364] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 21:10:05 node-1 kernel: [    8.685300] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 26 21:10:05 node-1 kernel: [    8.710519] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 26 21:10:05 node-1 kernel: [    8.830349] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 26 21:10:05 node-1 kernel: [    8.830355] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 26 21:10:05 node-1 kernel: [    8.830360] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 26 21:10:05 node-1 kernel: [    8.830378] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 26 21:10:05 node-1 kernel: [    8.868153] systemd-udevd[805]: starting version 204
Jul 26 21:10:05 node-1 kernel: [    9.094471] power_meter ACPI000D:00: Found ACPI power meter.
Jul 26 21:10:05 node-1 kernel: [    9.094491] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 26 21:10:05 node-1 kernel: [    9.101497] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 26 21:10:05 node-1 kernel: [    9.101502] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 26 21:10:05 node-1 kernel: [    9.101504] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 26 21:10:05 node-1 kernel: [    9.101506] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 26 21:10:05 node-1 kernel: [    9.101522] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 26 21:10:05 node-1 kernel: [    9.112153] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 26 21:10:05 node-1 kernel: [    9.115526] wmi: Mapper loaded
Jul 26 21:10:05 node-1 kernel: [    9.166218] IPMI System Interface driver.
Jul 26 21:10:05 node-1 kernel: [    9.166256] ipmi_si: probing via ACPI
Jul 26 21:10:05 node-1 kernel: [    9.166272] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 26 21:10:05 node-1 kernel: [    9.166273] ipmi_si: Adding ACPI-specified kcs state machine
Jul 26 21:10:05 node-1 kernel: [    9.166281] ipmi_si: probing via SMBIOS
Jul 26 21:10:05 node-1 kernel: [    9.166281] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 26 21:10:05 node-1 kernel: [    9.166282] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 26 21:10:05 node-1 kernel: [    9.166284] ipmi_si: probing via SPMI
Jul 26 21:10:05 node-1 kernel: [    9.166285] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 26 21:10:05 node-1 kernel: [    9.166285] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 26 21:10:05 node-1 kernel: [    9.166286] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 26 21:10:05 node-1 kernel: [    9.240518] systemd-udevd[848]: renamed network interface eth1 to enp7s0
Jul 26 21:10:05 node-1 kernel: [    9.264447] systemd-udevd[827]: renamed network interface eth0 to enp6s0
Jul 26 21:10:05 node-1 kernel: [    9.312820] systemd-udevd[825]: renamed network interface eth2 to enp8s0
Jul 26 21:10:05 node-1 kernel: [    9.348343] systemd-udevd[843]: renamed network interface eth3 to enp9s0
Jul 26 21:10:05 node-1 kernel: [    9.379992] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 26 21:10:05 node-1 kernel: [    9.379999] ipmi_si 00:09: IPMI kcs interface initialized
Jul 26 21:10:05 node-1 kernel: [    9.658772] type=1400 audit(1469567377.656:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1087 comm="apparmor_parser"
Jul 26 21:10:05 node-1 kernel: [    9.658931] type=1400 audit(1469567377.656:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1087 comm="apparmor_parser"
Jul 26 21:10:05 node-1 kernel: [    9.659064] type=1400 audit(1469567377.656:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1087 comm="apparmor_parser"
Jul 26 21:10:05 node-1 kernel: [    9.671470] type=1400 audit(1469567377.668:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1108 comm="apparmor_parser"
Jul 26 21:10:05 node-1 kernel: [    9.671619] type=1400 audit(1469567377.668:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1108 comm="apparmor_parser"
Jul 26 21:10:05 node-1 kernel: [    9.671752] type=1400 audit(1469567377.672:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1108 comm="apparmor_parser"
Jul 26 21:10:05 node-1 kernel: [    9.678809] type=1400 audit(1469567377.676:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1085 comm="apparmor_parser"
Jul 26 21:10:05 node-1 kernel: [    9.678963] type=1400 audit(1469567377.676:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1085 comm="apparmor_parser"
Jul 26 21:10:05 node-1 kernel: [    9.679083] type=1400 audit(1469567377.676:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1085 comm="apparmor_parser"
Jul 26 21:10:05 node-1 kernel: [    9.697671] type=1400 audit(1469567377.696:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1079 comm="apparmor_parser"
Jul 26 21:10:05 node-1 kernel: [   10.209059] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 26 21:10:05 node-1 kernel: [   10.210004] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 26 21:10:05 node-1 kernel: [   10.429320] enic 0000:06:00.0 enp6s0: Link UP
Jul 26 21:10:05 node-1 kernel: [   10.432235] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 26 21:10:05 node-1 kernel: [   10.432240] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 26 21:10:05 node-1 kernel: [   20.654566] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 26 21:10:05 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 26 21:10:06 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 26 21:10:06 node-1 kernel: [   38.880586] init: failsafe main process (8442) killed by TERM signal
Jul 26 21:10:06 node-1 dbus[8474]: [system] AppArmor D-Bus mediation is enabled
Jul 26 21:10:07 node-1 kernel: [   39.100251] audit_printk_skb: 30 callbacks suppressed
Jul 26 21:10:07 node-1 kernel: [   39.100254] type=1400 audit(1469567407.127:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8567 comm="apparmor_parser"
Jul 26 21:10:07 node-1 kernel: [   39.100258] type=1400 audit(1469567407.127:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8567 comm="apparmor_parser"
Jul 26 21:10:07 node-1 kernel: [   39.100261] type=1400 audit(1469567407.127:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8567 comm="apparmor_parser"
Jul 26 21:10:07 node-1 kernel: [   39.100479] type=1400 audit(1469567407.127:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8567 comm="apparmor_parser"
Jul 26 21:10:07 node-1 kernel: [   39.100481] type=1400 audit(1469567407.127:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8567 comm="apparmor_parser"
Jul 26 21:10:07 node-1 kernel: [   39.100592] type=1400 audit(1469567407.127:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8567 comm="apparmor_parser"
Jul 26 21:10:07 node-1 kernel: [   39.105633] type=1400 audit(1469567407.131:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8568 comm="apparmor_parser"
Jul 26 21:10:07 node-1 kernel: [   39.205267] type=1400 audit(1469567407.231:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8570 comm="apparmor_parser"
Jul 26 21:10:07 node-1 cron[8600]: (CRON) INFO (pidfile fd = 3)
Jul 26 21:10:07 node-1 anacron[8616]: Anacron 2.3 started on 2016-07-26
Jul 26 21:10:07 node-1 cron[8636]: (CRON) STARTUP (fork ok)
Jul 26 21:10:07 node-1 anacron[8616]: Will run job `cron.daily' in 5 min.
Jul 26 21:10:07 node-1 anacron[8616]: Will run job `cron.weekly' in 10 min.
Jul 26 21:10:07 node-1 anacron[8616]: Will run job `cron.monthly' in 15 min.
Jul 26 21:10:07 node-1 anacron[8616]: Jobs will be executed sequentially
Jul 26 21:10:07 node-1 cron[8636]: (CRON) INFO (Running @reboot jobs)
Jul 26 21:10:07 node-1 multipathd: path checkers start up
Jul 26 21:10:07 node-1 postfix/master[8779]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 26 21:10:11 node-1 puppet-agent[8963]: Reopening log files
Jul 26 21:10:12 node-1 puppet-agent[8963]: Could not request certificate: Connection refused - connect(2)
Jul 26 21:10:22 node-1 puppet-user[9042]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 26 21:10:22 node-1 puppet-user[9042]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 26 21:10:23 node-1 puppet-user[9042]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 26 21:10:23 node-1 puppet-user[9042]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 26 21:10:23 node-1 puppet-user[9042]: Finished catalog run in 0.96 seconds
Jul 26 21:10:24 node-1 multipathd: uevent trigger error
Jul 26 21:10:24 node-1 puppet-user[9487]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 26 21:10:24 node-1 puppet-user[9487]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Jul 26 21:10:25 node-1 puppet-user[9487]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 26 21:10:25 node-1 puppet-user[9487]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 26 21:10:25 node-1 puppet-user[9487]: (/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 26 21:10:25 node-1 puppet-user[9487]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 26 21:10:25 node-1 puppet-user[9487]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 26 21:10:25 node-1 puppet-user[9487]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 26 21:10:25 node-1 puppet-user[9487]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 26 21:10:25 node-1 puppet-user[9487]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 26 21:10:25 node-1 puppet-user[9487]: Finished catalog run in 0.07 seconds
Jul 26 21:10:26 node-1 puppet-user[9950]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 26 21:10:26 node-1 puppet-user[9950]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 26 21:10:26 node-1 puppet-user[9950]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 26 21:10:26 node-1 puppet-user[9950]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 26 21:10:26 node-1 puppet-user[9950]: Finished catalog run in 0.03 seconds
Jul 26 21:10:28 node-1 puppet-user[10419]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 26 21:10:28 node-1 puppet-user[10419]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 26 21:10:28 node-1 puppet-user[10419]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 26 21:10:28 node-1 puppet-user[10419]: Finished catalog run in 0.05 seconds
Jul 26 21:10:30 node-1 puppet-user[10890]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 26 21:10:30 node-1 puppet-user[10890]: Compiled catalog for node-1.domain.tld in environment production in 0.23 seconds
Jul 26 21:10:30 node-1 puppet-user[10890]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 26 21:10:30 node-1 kernel: [   62.674515] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 26 21:10:30 node-1 kernel: [   62.674565] 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 26 21:10:30 node-1 puppet-user[10890]: (/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 26 21:10:30 node-1 puppet-user[10890]: Finished catalog run in 0.16 seconds
Jul 26 21:10:32 node-1 puppet-user[11357]: (Scope(Class[main])) MODULAR: sync_time
Jul 26 21:10:32 node-1 puppet-user[11357]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 26 21:10:32 node-1 ntpdate[11908]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 26 21:10:39 node-1 ntpdate[11908]: adjust time server 10.20.0.2 offset 0.007078 sec
Jul 26 21:10:39 node-1 puppet-user[11357]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 26 21:10:39 node-1 puppet-user[11357]: Finished catalog run in 6.20 seconds
Jul 26 21:10:43 node-1 puppet-user[12120]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 26 21:10:43 node-1 puppet-user[12120]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 26 21:10:43 node-1 puppet-user[12120]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 26 21:10:43 node-1 puppet-user[12120]: Finished catalog run in 0.07 seconds
Jul 26 21:10:45 node-1 puppet-user[12574]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 26 21:10:46 node-1 puppet-user[12574]: Compiled catalog for node-1.domain.tld in environment production in 1.14 seconds
Jul 26 21:10:46 node-1 puppet-user[12574]: (/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 26 21:10:46 node-1 puppet-user[12574]: (/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 26 21:10:46 node-1 puppet-user[12574]: (/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 26 21:10:46 node-1 puppet-user[12574]: (/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 26 21:10:46 node-1 puppet-user[12574]: (/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 26 21:10:46 node-1 puppet-user[12574]: (/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 26 21:10:46 node-1 puppet-user[12574]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 26 21:10:46 node-1 puppet-user[12574]: (/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 26 21:10:46 node-1 puppet-user[12574]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 26 21:10:46 node-1 puppet-user[12574]: (/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 26 21:10:46 node-1 puppet-user[12574]: (/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 26 21:10:46 node-1 puppet-user[12574]: (/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 26 21:10:46 node-1 puppet-user[12574]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 26 21:10:46 node-1 puppet-user[12574]: (/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 26 21:10:46 node-1 puppet-user[12574]: (/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 26 21:10:46 node-1 puppet-user[12574]: (/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 26 21:10:46 node-1 puppet-user[12574]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 26 21:10:46 node-1 puppet-user[12574]: (/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 26 21:10:57 node-1 kernel: [   89.288419] init: plymouth-upstart-bridge main process ended, respawning
Jul 26 21:10:57 node-1 puppet-agent[8963]: Could not run: SIGTERM
Jul 26 21:10:57 node-1 kernel: [   89.544022] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 26 21:10:57 node-1 ec2: 
Jul 26 21:10:57 node-1 ec2: #############################################################
Jul 26 21:10:57 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 26 21:10:57 node-1 ec2: 1024 b1:cf:85:91:e1:44:fe:68:33:8e:0b:e8:9e:36:45:65  root@node-1.domain.tld (DSA)
Jul 26 21:10:57 node-1 ec2: 256 90:13:f2:0f:98:f3:d0:43:bf:39:f0:16:d1:0e:4f:f3  root@node-1.domain.tld (ECDSA)
Jul 26 21:10:57 node-1 ec2: 256 36:1e:7a:05:8d:60:37:72:f8:e0:e6:13:8c:1a:2f:71  root@node-1.domain.tld (ED25519)
Jul 26 21:10:57 node-1 ec2: 2048 e7:64:82:e3:d1:78:a4:d3:03:68:ad:58:a2:c2:0b:8d  root@node-1.domain.tld (RSA)
Jul 26 21:10:57 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 26 21:10:57 node-1 ec2: #############################################################
Jul 26 21:10:57 node-1 puppet-user[12574]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 26 21:10:57 node-1 puppet-user[12574]: Finished catalog run in 11.65 seconds
Jul 26 21:10:59 node-1 puppet-user[13835]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 26 21:10:59 node-1 puppet-user[13835]: Compiled catalog for node-1.domain.tld in environment production in 0.12 seconds
Jul 26 21:11:01 node-1 CRON[14340]: (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 26 21:11:04 node-1 puppet-user[13835]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 26 21:11:13 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 21:11:13 node-1 nailgun-agent: I, [2016-07-26T21:11:13.695385 #14343]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 26 21:11:26 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 21:11:26 node-1 nailgun-agent: I, [2016-07-26T21:11:26.866250 #14343]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 26 21:11:37 node-1 puppet-user[13835]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 26 21:11:37 node-1 puppet-user[13835]: Finished catalog run in 37.50 seconds
Jul 26 21:11:39 node-1 puppet-user[16664]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 26 21:11:39 node-1 puppet-user[16664]: Compiled catalog for node-1.domain.tld in environment production in 0.55 seconds
Jul 26 21:11:39 node-1 puppet-user[16664]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 26 21:11:39 node-1 puppet-user[16664]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 26 21:11:39 node-1 puppet-user[16664]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 26 21:11:39 node-1 puppet-user[16664]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 26 21:11:39 node-1 puppet-user[16664]: Finished catalog run in 0.14 seconds
Jul 26 21:11:41 node-1 puppet-user[17124]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 26 21:11:42 node-1 puppet-user[17124]: Compiled catalog for node-1.domain.tld in environment production in 0.80 seconds
Jul 26 21:11:42 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 26 21:11:43 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 26 21:11:43 node-1 crontab[17566]: (root) LIST (root)
Jul 26 21:11:43 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 26 21:11:43 node-1 crontab[17567]: (root) REPLACE (root)
Jul 26 21:11:45 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 26 21:11:46 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 26 21:11:46 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 26 21:11:46 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 26 21:11:46 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 26 21:11:46 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 26 21:11:46 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 26 21:11:46 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 26 21:11:46 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 26 21:11:46 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 26 21:11:46 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 26 21:11:46 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 26 21:11:46 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 26 21:11:46 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 26 21:11:46 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 26 21:11:46 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 26 21:11:47 node-1 puppet-user[17124]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 26 21:11:47 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8415" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:47 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 26 21:11:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:11:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:11:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:11:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:11:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:12:10 node-1 multipathd: uevent trigger error
<27>Jul 26 21:12:10 node-1 multipathd: uevent trigger error
<27>Jul 26 21:12:10 node-1 multipathd: uevent trigger error
<27>Jul 26 21:12:10 node-1 multipathd: uevent trigger error
<27>Jul 26 21:12:10 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:10 node-1 ntpdate[28357]: no servers can be used, exiting
<27>Jul 26 21:13:10 node-1 ntpdate[28486]: no servers can be used, exiting
<27>Jul 26 21:13:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:45 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:45 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:45 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:45 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:45 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:57 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:57 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:57 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:57 node-1 multipathd: uevent trigger error
<27>Jul 26 21:13:57 node-1 multipathd: uevent trigger error
<27>Jul 26 21:14:00 node-1 multipathd: uevent trigger error
<27>Jul 26 21:14:00 node-1 multipathd: uevent trigger error
<27>Jul 26 21:14:00 node-1 multipathd: uevent trigger error
<27>Jul 26 21:14:00 node-1 multipathd: uevent trigger error
<27>Jul 26 21:14:00 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:02 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:02 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:02 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:02 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:02 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:11 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:11 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:11 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:11 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:11 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:11 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:13 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 21:15:13 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 26 21:15:19 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 21:15:19 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 26 21:15:25 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 26 21:15:30 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 21:15:30 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 26 21:15:37 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:37 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:37 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:37 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:37 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:51 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:51 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:51 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:51 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:51 node-1 multipathd: uevent trigger error
<129>Jul 26 21:15:53 node-1 haproxy[16431]: 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 26 21:15:54 node-1 haproxy[16438]: 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 26 21:15:54 node-1 haproxy[16438]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:15:54 node-1 haproxy[16438]: proxy mysqld has no server available!
<27>Jul 26 21:15:56 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:56 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:56 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:56 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:56 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:56 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:56 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:59 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:59 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:59 node-1 multipathd: uevent trigger error
<27>Jul 26 21:15:59 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:00 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:00 node-1 multipathd: uevent trigger error
<129>Jul 26 21:16:02 node-1 haproxy[19033]: 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 26 21:16:02 node-1 haproxy[19033]: 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 26 21:16:03 node-1 haproxy[19042]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:03 node-1 haproxy[19042]: proxy mysqld has no server available!
<129>Jul 26 21:16:03 node-1 haproxy[19042]: 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 26 21:16:03 node-1 haproxy[19042]: 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 26 21:16:04 node-1 haproxy[19042]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:04 node-1 haproxy[19042]: proxy object-storage has no server available!
<27>Jul 26 21:16:05 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:05 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:05 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:05 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:05 node-1 multipathd: uevent trigger error
<129>Jul 26 21:16:07 node-1 haproxy[20371]: 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 26 21:16:07 node-1 haproxy[20371]: 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 26 21:16:08 node-1 haproxy[20375]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:08 node-1 haproxy[20375]: proxy neutron has no server available!
<129>Jul 26 21:16:08 node-1 haproxy[20375]: 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 26 21:16:08 node-1 haproxy[20375]: 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 26 21:16:08 node-1 haproxy[20375]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:08 node-1 haproxy[20375]: proxy mysqld has no server available!
<129>Jul 26 21:16:09 node-1 haproxy[20375]: 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 26 21:16:09 node-1 haproxy[20375]: 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 26 21:16:09 node-1 haproxy[20375]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:09 node-1 haproxy[20375]: proxy object-storage has no server available!
<27>Jul 26 21:16:11 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:11 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:11 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:11 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:11 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:11 node-1 multipathd: uevent trigger error
<129>Jul 26 21:16:13 node-1 haproxy[21906]: 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 26 21:16:13 node-1 haproxy[21906]: 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 26 21:16:13 node-1 haproxy[21906]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:13 node-1 haproxy[21906]: proxy keystone-1 has no server available!
<129>Jul 26 21:16:13 node-1 haproxy[21906]: 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 26 21:16:13 node-1 haproxy[21906]: 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 26 21:16:14 node-1 haproxy[21912]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:14 node-1 haproxy[21912]: proxy keystone-2 has no server available!
<129>Jul 26 21:16:14 node-1 haproxy[21912]: 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 26 21:16:14 node-1 haproxy[21912]: 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 26 21:16:14 node-1 haproxy[21912]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:14 node-1 haproxy[21912]: proxy neutron has no server available!
<129>Jul 26 21:16:14 node-1 haproxy[21912]: 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 26 21:16:14 node-1 haproxy[21912]: 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 26 21:16:14 node-1 haproxy[21912]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:14 node-1 haproxy[21912]: proxy mysqld has no server available!
<129>Jul 26 21:16:14 node-1 haproxy[21912]: 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 26 21:16:15 node-1 haproxy[21912]: 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 26 21:16:15 node-1 haproxy[21912]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:15 node-1 haproxy[21912]: proxy object-storage has no server available!
<27>Jul 26 21:16:16 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:16 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:16 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:16 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:16 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:16 node-1 multipathd: uevent trigger error
<129>Jul 26 21:16:18 node-1 haproxy[23299]: 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 26 21:16:18 node-1 haproxy[23299]: 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 26 21:16:18 node-1 haproxy[23299]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:18 node-1 haproxy[23299]: proxy keystone-1 has no server available!
<129>Jul 26 21:16:18 node-1 haproxy[23299]: 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 26 21:16:18 node-1 haproxy[23299]: 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 26 21:16:19 node-1 haproxy[23303]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:19 node-1 haproxy[23303]: proxy keystone-2 has no server available!
<129>Jul 26 21:16:19 node-1 haproxy[23303]: 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 26 21:16:19 node-1 haproxy[23303]: 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 26 21:16:19 node-1 haproxy[23303]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:19 node-1 haproxy[23303]: proxy neutron has no server available!
<129>Jul 26 21:16:19 node-1 haproxy[23303]: 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 26 21:16:19 node-1 haproxy[23303]: 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 26 21:16:19 node-1 haproxy[23303]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:19 node-1 haproxy[23303]: proxy mysqld has no server available!
<129>Jul 26 21:16:19 node-1 haproxy[23303]: 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 26 21:16:19 node-1 haproxy[23303]: 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 26 21:16:20 node-1 haproxy[23303]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:20 node-1 haproxy[23303]: proxy object-storage has no server available!
<129>Jul 26 21:16:20 node-1 haproxy[23303]: 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 26 21:16:20 node-1 haproxy[23303]: 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 26 21:16:20 node-1 haproxy[23303]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:20 node-1 haproxy[23303]: proxy aodh has no server available!
<27>Jul 26 21:16:21 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:21 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:21 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:21 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:21 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:21 node-1 multipathd: uevent trigger error
<129>Jul 26 21:16:24 node-1 haproxy[24804]: 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 26 21:16:24 node-1 haproxy[24804]: 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 26 21:16:24 node-1 haproxy[24804]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:24 node-1 haproxy[24804]: proxy keystone-1 has no server available!
<129>Jul 26 21:16:24 node-1 haproxy[24804]: 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 26 21:16:24 node-1 haproxy[24804]: 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 26 21:16:24 node-1 haproxy[24804]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:24 node-1 haproxy[24804]: proxy keystone-2 has no server available!
<129>Jul 26 21:16:24 node-1 haproxy[24804]: 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 26 21:16:24 node-1 haproxy[24804]: 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 26 21:16:24 node-1 haproxy[24804]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:24 node-1 haproxy[24804]: proxy neutron has no server available!
<129>Jul 26 21:16:24 node-1 haproxy[24804]: 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 26 21:16:24 node-1 haproxy[24804]: 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 26 21:16:25 node-1 haproxy[24808]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:25 node-1 haproxy[24808]: proxy mysqld has no server available!
<129>Jul 26 21:16:25 node-1 haproxy[24808]: 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 26 21:16:25 node-1 haproxy[24808]: 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 26 21:16:25 node-1 haproxy[24808]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:25 node-1 haproxy[24808]: proxy object-storage has no server available!
<129>Jul 26 21:16:25 node-1 haproxy[24808]: 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 26 21:16:25 node-1 haproxy[24808]: 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 26 21:16:25 node-1 haproxy[24808]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:25 node-1 haproxy[24808]: proxy aodh has no server available!
<129>Jul 26 21:16:25 node-1 haproxy[24808]: 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 26 21:16:25 node-1 haproxy[24808]: 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 26 21:16:25 node-1 haproxy[24808]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:25 node-1 haproxy[24808]: proxy ceilometer has no server available!
<27>Jul 26 21:16:27 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:27 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:27 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:27 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:27 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:27 node-1 multipathd: uevent trigger error
<129>Jul 26 21:16:29 node-1 haproxy[26156]: 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 26 21:16:29 node-1 haproxy[26156]: 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 26 21:16:29 node-1 haproxy[26156]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:29 node-1 haproxy[26156]: proxy keystone-1 has no server available!
<129>Jul 26 21:16:29 node-1 haproxy[26156]: 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 26 21:16:29 node-1 haproxy[26156]: 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 26 21:16:29 node-1 haproxy[26156]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:29 node-1 haproxy[26156]: proxy keystone-2 has no server available!
<129>Jul 26 21:16:30 node-1 haproxy[26160]: 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 26 21:16:30 node-1 haproxy[26160]: 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 26 21:16:30 node-1 haproxy[26160]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:30 node-1 haproxy[26160]: proxy neutron has no server available!
<129>Jul 26 21:16:30 node-1 haproxy[26160]: 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 26 21:16:30 node-1 haproxy[26160]: 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 26 21:16:30 node-1 haproxy[26160]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:30 node-1 haproxy[26160]: proxy mysqld has no server available!
<129>Jul 26 21:16:30 node-1 haproxy[26160]: 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 26 21:16:30 node-1 haproxy[26160]: 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 26 21:16:30 node-1 haproxy[26160]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:30 node-1 haproxy[26160]: proxy object-storage has no server available!
<129>Jul 26 21:16:30 node-1 haproxy[26160]: 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 26 21:16:30 node-1 haproxy[26160]: 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 26 21:16:31 node-1 haproxy[26160]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:31 node-1 haproxy[26160]: proxy aodh has no server available!
<129>Jul 26 21:16:31 node-1 haproxy[26160]: 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 26 21:16:31 node-1 haproxy[26160]: 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 26 21:16:31 node-1 haproxy[26160]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:31 node-1 haproxy[26160]: proxy ceilometer has no server available!
<27>Jul 26 21:16:32 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:32 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:32 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:32 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:32 node-1 multipathd: uevent trigger error
<129>Jul 26 21:16:34 node-1 haproxy[27508]: 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 26 21:16:35 node-1 haproxy[27517]: 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 26 21:16:35 node-1 haproxy[27517]: 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 26 21:16:35 node-1 haproxy[27517]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:35 node-1 haproxy[27517]: proxy keystone-1 has no server available!
<129>Jul 26 21:16:35 node-1 haproxy[27517]: 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 26 21:16:35 node-1 haproxy[27517]: 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 26 21:16:35 node-1 haproxy[27517]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:35 node-1 haproxy[27517]: proxy keystone-2 has no server available!
<129>Jul 26 21:16:35 node-1 haproxy[27517]: 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 26 21:16:35 node-1 haproxy[27517]: 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 26 21:16:35 node-1 haproxy[27517]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:35 node-1 haproxy[27517]: proxy neutron has no server available!
<129>Jul 26 21:16:35 node-1 haproxy[27517]: 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 26 21:16:35 node-1 haproxy[27517]: 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 26 21:16:36 node-1 haproxy[27517]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:36 node-1 haproxy[27517]: proxy mysqld has no server available!
<129>Jul 26 21:16:36 node-1 haproxy[27517]: 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 26 21:16:36 node-1 haproxy[27517]: 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 26 21:16:36 node-1 haproxy[27517]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:36 node-1 haproxy[27517]: proxy object-storage has no server available!
<129>Jul 26 21:16:36 node-1 haproxy[27517]: 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 26 21:16:36 node-1 haproxy[27517]: 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 26 21:16:36 node-1 haproxy[27517]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:36 node-1 haproxy[27517]: proxy aodh has no server available!
<129>Jul 26 21:16:36 node-1 haproxy[27517]: 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 26 21:16:36 node-1 haproxy[27517]: 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 26 21:16:36 node-1 haproxy[27517]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:36 node-1 haproxy[27517]: proxy ceilometer has no server available!
<27>Jul 26 21:16:37 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:38 node-1 multipathd: uevent trigger error
<129>Jul 26 21:16:40 node-1 haproxy[28908]: 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 26 21:16:40 node-1 haproxy[28908]: 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 26 21:16:40 node-1 haproxy[28908]: 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 26 21:16:40 node-1 haproxy[28908]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:40 node-1 haproxy[28908]: proxy keystone-1 has no server available!
<129>Jul 26 21:16:40 node-1 haproxy[28908]: 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 26 21:16:41 node-1 haproxy[28912]: 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 26 21:16:41 node-1 haproxy[28912]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:41 node-1 haproxy[28912]: proxy keystone-2 has no server available!
<129>Jul 26 21:16:41 node-1 haproxy[28912]: 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 26 21:16:41 node-1 haproxy[28912]: 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 26 21:16:41 node-1 haproxy[28912]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:41 node-1 haproxy[28912]: proxy glance-api has no server available!
<129>Jul 26 21:16:41 node-1 haproxy[28912]: 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 26 21:16:41 node-1 haproxy[28912]: 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 26 21:16:41 node-1 haproxy[28912]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:41 node-1 haproxy[28912]: proxy glance-glare has no server available!
<129>Jul 26 21:16:41 node-1 haproxy[28912]: 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 26 21:16:41 node-1 haproxy[28912]: 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 26 21:16:41 node-1 haproxy[28912]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:41 node-1 haproxy[28912]: proxy neutron has no server available!
<129>Jul 26 21:16:41 node-1 haproxy[28912]: 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 26 21:16:41 node-1 haproxy[28912]: 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 26 21:16:41 node-1 haproxy[28912]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:41 node-1 haproxy[28912]: proxy glance-registry has no server available!
<129>Jul 26 21:16:41 node-1 haproxy[28912]: 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 26 21:16:41 node-1 haproxy[28912]: 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 26 21:16:41 node-1 haproxy[28912]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:41 node-1 haproxy[28912]: proxy mysqld has no server available!
<129>Jul 26 21:16:42 node-1 haproxy[28912]: 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 26 21:16:42 node-1 haproxy[28912]: 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 26 21:16:42 node-1 haproxy[28912]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:42 node-1 haproxy[28912]: proxy object-storage has no server available!
<129>Jul 26 21:16:42 node-1 haproxy[28912]: 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 26 21:16:42 node-1 haproxy[28912]: 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 26 21:16:42 node-1 haproxy[28912]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:42 node-1 haproxy[28912]: proxy aodh has no server available!
<129>Jul 26 21:16:42 node-1 haproxy[28912]: 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 26 21:16:42 node-1 haproxy[28912]: 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 26 21:16:42 node-1 haproxy[28912]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:42 node-1 haproxy[28912]: proxy ceilometer has no server available!
<27>Jul 26 21:16:43 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:43 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:43 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:43 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:43 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:44 node-1 multipathd: uevent trigger error
<129>Jul 26 21:16:46 node-1 haproxy[30317]: 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 26 21:16:46 node-1 haproxy[30317]: 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 26 21:16:46 node-1 haproxy[30317]: 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 26 21:16:46 node-1 haproxy[30317]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:46 node-1 haproxy[30317]: proxy keystone-1 has no server available!
<129>Jul 26 21:16:46 node-1 haproxy[30317]: 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 26 21:16:46 node-1 haproxy[30317]: 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 26 21:16:46 node-1 haproxy[30317]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:46 node-1 haproxy[30317]: proxy keystone-2 has no server available!
<129>Jul 26 21:16:46 node-1 haproxy[30317]: 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 26 21:16:47 node-1 haproxy[30324]: 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 26 21:16:47 node-1 haproxy[30324]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:47 node-1 haproxy[30324]: proxy nova-api has no server available!
<129>Jul 26 21:16:47 node-1 haproxy[30324]: 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 26 21:16:47 node-1 haproxy[30324]: 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 26 21:16:47 node-1 haproxy[30324]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:47 node-1 haproxy[30324]: proxy nova-metadata-api has no server available!
<129>Jul 26 21:16:47 node-1 haproxy[30324]: 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 26 21:16:47 node-1 haproxy[30324]: 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 26 21:16:47 node-1 haproxy[30324]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:47 node-1 haproxy[30324]: proxy glance-api has no server available!
<129>Jul 26 21:16:47 node-1 haproxy[30324]: 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 26 21:16:47 node-1 haproxy[30324]: 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 26 21:16:47 node-1 haproxy[30324]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:47 node-1 haproxy[30324]: proxy glance-glare has no server available!
<129>Jul 26 21:16:47 node-1 haproxy[30324]: 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 26 21:16:47 node-1 haproxy[30324]: 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 26 21:16:47 node-1 haproxy[30324]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:47 node-1 haproxy[30324]: proxy neutron has no server available!
<129>Jul 26 21:16:47 node-1 haproxy[30324]: 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 26 21:16:47 node-1 haproxy[30324]: 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 26 21:16:47 node-1 haproxy[30324]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:47 node-1 haproxy[30324]: proxy glance-registry has no server available!
<129>Jul 26 21:16:47 node-1 haproxy[30324]: 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 26 21:16:47 node-1 haproxy[30324]: 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 26 21:16:47 node-1 haproxy[30324]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:47 node-1 haproxy[30324]: proxy mysqld has no server available!
<129>Jul 26 21:16:47 node-1 haproxy[30324]: 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 26 21:16:48 node-1 haproxy[30324]: 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 26 21:16:48 node-1 haproxy[30324]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:48 node-1 haproxy[30324]: proxy object-storage has no server available!
<129>Jul 26 21:16:48 node-1 haproxy[30324]: 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 26 21:16:48 node-1 haproxy[30324]: 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 26 21:16:48 node-1 haproxy[30324]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:48 node-1 haproxy[30324]: proxy aodh has no server available!
<129>Jul 26 21:16:48 node-1 haproxy[30324]: 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 26 21:16:48 node-1 haproxy[30324]: 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 26 21:16:48 node-1 haproxy[30324]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:48 node-1 haproxy[30324]: proxy ceilometer has no server available!
<129>Jul 26 21:16:48 node-1 haproxy[30324]: 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 26 21:16:48 node-1 haproxy[30324]: 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 26 21:16:48 node-1 haproxy[30324]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:48 node-1 haproxy[30324]: proxy nova-novncproxy has no server available!
<27>Jul 26 21:16:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:49 node-1 multipathd: uevent trigger error
<129>Jul 26 21:16:52 node-1 haproxy[31678]: 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 26 21:16:52 node-1 haproxy[31678]: 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 26 21:16:52 node-1 haproxy[31678]: 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 26 21:16:52 node-1 haproxy[31678]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:52 node-1 haproxy[31678]: proxy keystone-1 has no server available!
<129>Jul 26 21:16:52 node-1 haproxy[31678]: 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 26 21:16:52 node-1 haproxy[31678]: 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 26 21:16:52 node-1 haproxy[31678]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:52 node-1 haproxy[31678]: proxy keystone-2 has no server available!
<129>Jul 26 21:16:52 node-1 haproxy[31678]: 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 26 21:16:52 node-1 haproxy[31678]: 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 26 21:16:52 node-1 haproxy[31678]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:52 node-1 haproxy[31678]: proxy nova-api has no server available!
<129>Jul 26 21:16:52 node-1 haproxy[31678]: 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 26 21:16:52 node-1 haproxy[31678]: 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 26 21:16:52 node-1 haproxy[31678]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:52 node-1 haproxy[31678]: proxy nova-metadata-api has no server available!
<129>Jul 26 21:16:52 node-1 haproxy[31678]: 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 26 21:16:52 node-1 haproxy[31678]: 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 26 21:16:52 node-1 haproxy[31678]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:52 node-1 haproxy[31678]: proxy cinder-api has no server available!
<129>Jul 26 21:16:52 node-1 haproxy[31678]: 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 26 21:16:52 node-1 haproxy[31678]: 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 26 21:16:52 node-1 haproxy[31678]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:52 node-1 haproxy[31678]: proxy glance-api has no server available!
<129>Jul 26 21:16:52 node-1 haproxy[31678]: 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 26 21:16:53 node-1 haproxy[31682]: 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 26 21:16:53 node-1 haproxy[31682]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:53 node-1 haproxy[31682]: proxy glance-glare has no server available!
<129>Jul 26 21:16:53 node-1 haproxy[31682]: 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 26 21:16:53 node-1 haproxy[31682]: 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 26 21:16:53 node-1 haproxy[31682]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:53 node-1 haproxy[31682]: proxy neutron has no server available!
<129>Jul 26 21:16:53 node-1 haproxy[31682]: 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 26 21:16:53 node-1 haproxy[31682]: 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 26 21:16:53 node-1 haproxy[31682]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:53 node-1 haproxy[31682]: proxy glance-registry has no server available!
<129>Jul 26 21:16:53 node-1 haproxy[31682]: 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 26 21:16:53 node-1 haproxy[31682]: 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 26 21:16:53 node-1 haproxy[31682]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:53 node-1 haproxy[31682]: proxy mysqld has no server available!
<129>Jul 26 21:16:53 node-1 haproxy[31682]: 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 26 21:16:53 node-1 haproxy[31682]: 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 26 21:16:53 node-1 haproxy[31682]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:53 node-1 haproxy[31682]: proxy object-storage has no server available!
<129>Jul 26 21:16:53 node-1 haproxy[31682]: 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 26 21:16:53 node-1 haproxy[31682]: 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 26 21:16:53 node-1 haproxy[31682]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:53 node-1 haproxy[31682]: proxy aodh has no server available!
<129>Jul 26 21:16:53 node-1 haproxy[31682]: 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 26 21:16:53 node-1 haproxy[31682]: 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 26 21:16:53 node-1 haproxy[31682]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:53 node-1 haproxy[31682]: proxy ceilometer has no server available!
<129>Jul 26 21:16:53 node-1 haproxy[31682]: 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 26 21:16:53 node-1 haproxy[31682]: 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 26 21:16:53 node-1 haproxy[31682]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:53 node-1 haproxy[31682]: proxy nova-novncproxy has no server available!
<27>Jul 26 21:16:55 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:55 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:55 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:55 node-1 multipathd: uevent trigger error
<27>Jul 26 21:16:55 node-1 multipathd: uevent trigger error
<129>Jul 26 21:16:57 node-1 haproxy[554]: 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 26 21:16:57 node-1 haproxy[554]: 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 26 21:16:57 node-1 haproxy[554]: 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 26 21:16:58 node-1 haproxy[558]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:58 node-1 haproxy[558]: proxy keystone-1 has no server available!
<129>Jul 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:58 node-1 haproxy[558]: proxy keystone-2 has no server available!
<129>Jul 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:58 node-1 haproxy[558]: proxy nova-api has no server available!
<129>Jul 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:58 node-1 haproxy[558]: proxy nova-metadata-api has no server available!
<129>Jul 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:58 node-1 haproxy[558]: proxy cinder-api has no server available!
<129>Jul 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:58 node-1 haproxy[558]: proxy glance-api has no server available!
<129>Jul 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:58 node-1 haproxy[558]: proxy glance-glare has no server available!
<129>Jul 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:58 node-1 haproxy[558]: proxy neutron has no server available!
<129>Jul 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:58 node-1 haproxy[558]: proxy glance-registry has no server available!
<129>Jul 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:58 node-1 haproxy[558]: 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 26 21:16:59 node-1 haproxy[558]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:59 node-1 haproxy[558]: proxy mysqld has no server available!
<129>Jul 26 21:16:59 node-1 haproxy[558]: 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 26 21:16:59 node-1 haproxy[558]: 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 26 21:16:59 node-1 haproxy[558]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:59 node-1 haproxy[558]: proxy object-storage has no server available!
<129>Jul 26 21:16:59 node-1 haproxy[558]: 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 26 21:16:59 node-1 haproxy[558]: 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 26 21:16:59 node-1 haproxy[558]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:59 node-1 haproxy[558]: proxy aodh has no server available!
<129>Jul 26 21:16:59 node-1 haproxy[558]: 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 26 21:16:59 node-1 haproxy[558]: 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 26 21:16:59 node-1 haproxy[558]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:59 node-1 haproxy[558]: proxy ceilometer has no server available!
<129>Jul 26 21:16:59 node-1 haproxy[558]: 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 26 21:16:59 node-1 haproxy[558]: 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 26 21:16:59 node-1 haproxy[558]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:59 node-1 haproxy[558]: proxy heat-api has no server available!
<129>Jul 26 21:16:59 node-1 haproxy[558]: 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 26 21:16:59 node-1 haproxy[558]: 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 26 21:16:59 node-1 haproxy[558]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:59 node-1 haproxy[558]: proxy heat-api-cfn has no server available!
<129>Jul 26 21:16:59 node-1 haproxy[558]: 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 26 21:16:59 node-1 haproxy[558]: 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 26 21:16:59 node-1 haproxy[558]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:59 node-1 haproxy[558]: proxy heat-api-cloudwatch has no server available!
<129>Jul 26 21:16:59 node-1 haproxy[558]: 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 26 21:16:59 node-1 haproxy[558]: 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 26 21:16:59 node-1 haproxy[558]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:59 node-1 haproxy[558]: proxy nova-novncproxy has no server available!
<27>Jul 26 21:17:01 node-1 multipathd: uevent trigger error
<27>Jul 26 21:17:01 node-1 multipathd: uevent trigger error
<27>Jul 26 21:17:01 node-1 multipathd: uevent trigger error
<27>Jul 26 21:17:01 node-1 multipathd: uevent trigger error
<27>Jul 26 21:17:01 node-1 multipathd: uevent trigger error
<27>Jul 26 21:17:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:17:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:17:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:17:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:17:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:17:15 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 26 21:17:41 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 26 21:17:43 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 26 21:18:13 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 21:18:18 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 21:18:41 node-1 multipathd: uevent trigger error
<27>Jul 26 21:18:41 node-1 multipathd: uevent trigger error
<27>Jul 26 21:18:41 node-1 multipathd: uevent trigger error
<27>Jul 26 21:18:41 node-1 multipathd: uevent trigger error
<27>Jul 26 21:18:41 node-1 multipathd: uevent trigger error
<27>Jul 26 21:20:58 node-1 multipathd: uevent trigger error
<27>Jul 26 21:20:58 node-1 multipathd: uevent trigger error
<27>Jul 26 21:20:58 node-1 multipathd: uevent trigger error
<27>Jul 26 21:20:58 node-1 multipathd: uevent trigger error
<27>Jul 26 21:20:58 node-1 multipathd: uevent trigger error
<27>Jul 26 21:20:58 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:17 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 26 21:21:18 node-1 apache2_error [Tue Jul 26 21:21:18.465522 2016] [mpm_event:notice] [pid 11066:tid 139929143601024] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 26 21:21:18 node-1 apache2_error [Tue Jul 26 21:21:18.465593 2016] [core:notice] [pid 11066:tid 139929143601024] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 21:21:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:26 node-1 multipathd: uevent trigger error
<43>Jul 26 21:21:28 node-1 apache2_error [Tue Jul 26 21:21:20.599636 2016] [mpm_event:notice] [pid 11066:tid 139929143601024] AH00491: caught SIGTERM, shutting down
<43>Jul 26 21:21:28 node-1 apache2_error [Tue Jul 26 21:21:21.684873 2016] [mpm_worker:notice] [pid 11389:tid 140019692767104] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 26 21:21:28 node-1 apache2_error [Tue Jul 26 21:21:21.684947 2016] [core:notice] [pid 11389:tid 140019692767104] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 21:21:31 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:31 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:31 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:31 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:31 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:31 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:34 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:34 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:34 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:34 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:34 node-1 multipathd: uevent trigger error
<27>Jul 26 21:21:34 node-1 multipathd: uevent trigger error
<43>Jul 26 21:22:48 node-1 apache2_error [Tue Jul 26 21:22:47.637903 2016] [mpm_worker:notice] [pid 11389:tid 140019692767104] AH00295: caught SIGTERM, shutting down
<43>Jul 26 21:22:48 node-1 apache2_error [Tue Jul 26 21:22:48.408495 2016] [mpm_worker:notice] [pid 27163:tid 139673795323776] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 21:22:48 node-1 apache2_error [Tue Jul 26 21:22:48.408529 2016] [core:notice] [pid 27163:tid 139673795323776] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 26 21:23:38 node-1 apache2_error [Tue Jul 26 21:23:33.745064 2016] [mpm_worker:notice] [pid 27163:tid 139673795323776] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 21:23:38 node-1 apache2_error [Tue Jul 26 21:23:33.939104 2016] [mpm_worker:warn] [pid 27163:tid 139673795323776] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 21:23:38 node-1 apache2_error [Tue Jul 26 21:23:33.942943 2016] [mpm_worker:notice] [pid 27163:tid 139673795323776] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 21:23:38 node-1 apache2_error [Tue Jul 26 21:23:33.951354 2016] [core:notice] [pid 27163:tid 139673795323776] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 21:24:18 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:18 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:18 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:18 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:18 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:18 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 21:24:22 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:22 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:22 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:22 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:22 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:22 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:24:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:03 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:03 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:03 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:08 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:08 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:08 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:08 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:08 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:53 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:53 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:53 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:53 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:53 node-1 multipathd: uevent trigger error
<27>Jul 26 21:25:53 node-1 multipathd: uevent trigger error
<27>Jul 26 21:26:08 node-1 multipathd: uevent trigger error
<27>Jul 26 21:26:08 node-1 multipathd: uevent trigger error
<27>Jul 26 21:26:08 node-1 multipathd: uevent trigger error
<27>Jul 26 21:26:08 node-1 multipathd: uevent trigger error
<27>Jul 26 21:26:08 node-1 multipathd: uevent trigger error
<27>Jul 26 21:27:03 node-1 multipathd: uevent trigger error
<27>Jul 26 21:27:03 node-1 multipathd: uevent trigger error
<27>Jul 26 21:27:03 node-1 multipathd: uevent trigger error
<27>Jul 26 21:27:03 node-1 multipathd: uevent trigger error
<27>Jul 26 21:27:03 node-1 multipathd: uevent trigger error
<27>Jul 26 21:27:28 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 21:28:18 node-1 multipathd: uevent trigger error
<27>Jul 26 21:28:18 node-1 multipathd: uevent trigger error
<27>Jul 26 21:28:18 node-1 multipathd: uevent trigger error
<27>Jul 26 21:28:18 node-1 multipathd: uevent trigger error
<27>Jul 26 21:28:18 node-1 multipathd: uevent trigger error
<27>Jul 26 21:28:18 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:19 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:19 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:19 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:19 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:19 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:19 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:25 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:25 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:25 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:25 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:25 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:25 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:47 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:47 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:47 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:47 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:47 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:47 node-1 multipathd: uevent trigger error
<27>Jul 26 21:29:47 node-1 multipathd: uevent trigger error
<27>Jul 26 21:30:29 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 21:32:21 node-1 multipathd: uevent trigger error
<27>Jul 26 21:32:21 node-1 multipathd: uevent trigger error
<27>Jul 26 21:32:21 node-1 multipathd: uevent trigger error
<27>Jul 26 21:32:21 node-1 multipathd: uevent trigger error
<27>Jul 26 21:32:22 node-1 multipathd: uevent trigger error
<27>Jul 26 21:32:22 node-1 multipathd: uevent trigger error
<27>Jul 26 21:32:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:32:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:32:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:32:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:32:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:32:43 node-1 multipathd: uevent trigger error
<27>Jul 26 21:32:43 node-1 multipathd: uevent trigger error
<27>Jul 26 21:32:43 node-1 multipathd: uevent trigger error
<27>Jul 26 21:32:43 node-1 multipathd: uevent trigger error
<27>Jul 26 21:32:43 node-1 multipathd: uevent trigger error
<27>Jul 26 21:32:43 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:31 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 21:33:32 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:32 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:32 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:32 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:32 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:53 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:53 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:53 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:53 node-1 multipathd: uevent trigger error
<27>Jul 26 21:33:53 node-1 multipathd: uevent trigger error
<27>Jul 26 21:34:41 node-1 multipathd: uevent trigger error
<27>Jul 26 21:34:41 node-1 multipathd: uevent trigger error
<27>Jul 26 21:34:41 node-1 multipathd: uevent trigger error
<27>Jul 26 21:34:41 node-1 multipathd: uevent trigger error
<27>Jul 26 21:34:41 node-1 multipathd: uevent trigger error
<27>Jul 26 21:34:47 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Jul 26 21:34:47 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Jul 26 21:34:48 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Jul 26 21:34:49 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Jul 26 21:34:49 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Jul 26 21:34:50 node-1 multipathd: uevent trigger error
<27>Jul 26 21:34:50 node-1 multipathd: uevent trigger error
<27>Jul 26 21:34:50 node-1 multipathd: uevent trigger error
<27>Jul 26 21:34:50 node-1 multipathd: uevent trigger error
<27>Jul 26 21:34:50 node-1 multipathd: uevent trigger error
<27>Jul 26 21:34:50 node-1 multipathd: uevent trigger error
<27>Jul 26 21:35:03 node-1 multipathd: uevent trigger error
<27>Jul 26 21:35:03 node-1 multipathd: uevent trigger error
<27>Jul 26 21:35:03 node-1 multipathd: uevent trigger error
<27>Jul 26 21:35:03 node-1 multipathd: uevent trigger error
<27>Jul 26 21:35:03 node-1 multipathd: uevent trigger error
<27>Jul 26 21:35:03 node-1 multipathd: uevent trigger error
<27>Jul 26 21:35:18 node-1 multipathd: uevent trigger error
<27>Jul 26 21:35:18 node-1 multipathd: uevent trigger error
<27>Jul 26 21:35:18 node-1 multipathd: uevent trigger error
<27>Jul 26 21:35:18 node-1 multipathd: uevent trigger error
<27>Jul 26 21:35:18 node-1 multipathd: uevent trigger error
<27>Jul 26 21:35:37 node-1 multipathd: uevent trigger error
<27>Jul 26 21:35:37 node-1 multipathd: uevent trigger error
<27>Jul 26 21:35:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:35:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:35:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:36:33 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 21:38:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:38:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:38:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:38:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:38:04 node-1 multipathd: uevent trigger error
<27>Jul 26 21:38:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:38:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:38:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:38:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:38:49 node-1 multipathd: uevent trigger error
<27>Jul 26 21:38:55 node-1 multipathd: uevent trigger error
<27>Jul 26 21:38:55 node-1 multipathd: uevent trigger error
<27>Jul 26 21:38:55 node-1 multipathd: uevent trigger error
<27>Jul 26 21:38:55 node-1 multipathd: uevent trigger error
<27>Jul 26 21:38:55 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:25 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:25 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:25 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:25 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:25 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:30 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:30 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:30 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:30 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:30 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:30 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:34 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:34 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:34 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:34 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 21:39:34 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:34 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:46 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:46 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:46 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:46 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:46 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:46 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:53 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:53 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:53 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:53 node-1 multipathd: uevent trigger error
<27>Jul 26 21:39:53 node-1 multipathd: uevent trigger error
<27>Jul 26 21:40:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:40:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:40:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:40:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:40:38 node-1 multipathd: uevent trigger error
<27>Jul 26 21:41:48 node-1 multipathd: uevent trigger error
<27>Jul 26 21:41:48 node-1 multipathd: uevent trigger error
<27>Jul 26 21:41:48 node-1 multipathd: uevent trigger error
<27>Jul 26 21:41:48 node-1 multipathd: uevent trigger error
<27>Jul 26 21:41:48 node-1 multipathd: uevent trigger error
<27>Jul 26 21:42:07 node-1 multipathd: uevent trigger error
<27>Jul 26 21:42:07 node-1 multipathd: uevent trigger error
<27>Jul 26 21:42:07 node-1 multipathd: uevent trigger error
<27>Jul 26 21:42:07 node-1 multipathd: uevent trigger error
<27>Jul 26 21:42:07 node-1 multipathd: uevent trigger error
<11>Jul 26 21:42:21 node-1 liberasurecode[30093]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:21 node-1 liberasurecode[30093]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:21 node-1 liberasurecode[30093]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:21 node-1 liberasurecode[30093]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:21 node-1 liberasurecode[30117]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:21 node-1 liberasurecode[30117]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:21 node-1 liberasurecode[30117]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:21 node-1 liberasurecode[30117]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:24 node-1 liberasurecode[30571]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:24 node-1 liberasurecode[30571]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:24 node-1 liberasurecode[30571]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:24 node-1 liberasurecode[30571]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:30 node-1 liberasurecode[31175]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:30 node-1 liberasurecode[31175]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:30 node-1 liberasurecode[31175]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:30 node-1 liberasurecode[31175]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:30 node-1 liberasurecode[31224]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:30 node-1 liberasurecode[31224]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:30 node-1 liberasurecode[31224]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:30 node-1 liberasurecode[31224]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:30 node-1 liberasurecode[31287]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:30 node-1 liberasurecode[31287]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:30 node-1 liberasurecode[31287]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:30 node-1 liberasurecode[31287]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:30 node-1 liberasurecode[31345]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:30 node-1 liberasurecode[31345]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:30 node-1 liberasurecode[31345]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:30 node-1 liberasurecode[31345]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:31 node-1 liberasurecode[31357]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:31 node-1 liberasurecode[31357]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:31 node-1 liberasurecode[31357]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:31 node-1 liberasurecode[31357]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:31 node-1 liberasurecode[31374]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:31 node-1 liberasurecode[31374]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:31 node-1 liberasurecode[31374]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:31 node-1 liberasurecode[31374]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:31 node-1 liberasurecode[31389]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:31 node-1 liberasurecode[31389]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:31 node-1 liberasurecode[31389]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:31 node-1 liberasurecode[31389]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 26 21:42:36 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<11>Jul 26 21:42:47 node-1 liberasurecode[1458]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:47 node-1 liberasurecode[1458]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:47 node-1 liberasurecode[1458]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:42:47 node-1 liberasurecode[1458]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 26 21:42:56 node-1 multipathd: uevent trigger error
<27>Jul 26 21:42:56 node-1 multipathd: uevent trigger error
<27>Jul 26 21:42:56 node-1 multipathd: uevent trigger error
<27>Jul 26 21:42:56 node-1 multipathd: uevent trigger error
<27>Jul 26 21:42:56 node-1 multipathd: uevent trigger error
<43>Jul 26 21:43:51 node-1 apache2_error [Tue Jul 26 21:43:46.154962 2016] [mpm_worker:notice] [pid 27163:tid 139673795323776] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 21:43:51 node-1 apache2_error [Tue Jul 26 21:43:46.539231 2016] [mpm_worker:warn] [pid 27163:tid 139673795323776] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 21:43:51 node-1 apache2_error [Tue Jul 26 21:43:46.545423 2016] [mpm_worker:notice] [pid 27163:tid 139673795323776] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 21:43:51 node-1 apache2_error [Tue Jul 26 21:43:46.545477 2016] [core:notice] [pid 27163:tid 139673795323776] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 21:44:28 node-1 multipathd: uevent trigger error
<27>Jul 26 21:44:28 node-1 multipathd: uevent trigger error
<27>Jul 26 21:44:28 node-1 multipathd: uevent trigger error
<27>Jul 26 21:44:28 node-1 multipathd: uevent trigger error
<27>Jul 26 21:44:28 node-1 multipathd: uevent trigger error
<43>Jul 26 21:44:31 node-1 apache2_error [Tue Jul 26 21:44:23.813433 2016] [mpm_worker:notice] [pid 27163:tid 139673795323776] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 21:44:31 node-1 apache2_error [Tue Jul 26 21:44:24.009349 2016] [mpm_worker:warn] [pid 27163:tid 139673795323776] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 21:44:31 node-1 apache2_error [Tue Jul 26 21:44:24.020096 2016] [mpm_worker:notice] [pid 27163:tid 139673795323776] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 21:44:31 node-1 apache2_error [Tue Jul 26 21:44:24.020121 2016] [core:notice] [pid 27163:tid 139673795323776] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 21:44:35 node-1 multipathd: uevent trigger error
<27>Jul 26 21:44:35 node-1 multipathd: uevent trigger error
<27>Jul 26 21:44:35 node-1 multipathd: uevent trigger error
<27>Jul 26 21:44:35 node-1 multipathd: uevent trigger error
<27>Jul 26 21:44:35 node-1 multipathd: uevent trigger error
<11>Jul 26 21:45:01 node-1 liberasurecode[23066]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:45:01 node-1 liberasurecode[23066]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:45:01 node-1 liberasurecode[23066]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:45:01 node-1 liberasurecode[23066]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Jul 26 21:45:11 node-1 apache2_error [Tue Jul 26 21:45:09.651614 2016] [mpm_worker:notice] [pid 27163:tid 139673795323776] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 21:45:11 node-1 apache2_error [Tue Jul 26 21:45:10.037940 2016] [mpm_worker:warn] [pid 27163:tid 139673795323776] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 21:45:11 node-1 apache2_error [Tue Jul 26 21:45:10.052813 2016] [mpm_worker:notice] [pid 27163:tid 139673795323776] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 21:45:11 node-1 apache2_error [Tue Jul 26 21:45:10.052843 2016] [core:notice] [pid 27163:tid 139673795323776] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 21:45:14 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:14 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:14 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:14 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:14 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:14 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:21 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:21 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:21 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:21 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:21 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:27 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:27 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:27 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:27 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:27 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:27 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:34 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:34 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:34 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:34 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:34 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:34 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:37 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 21:45:50 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:50 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:50 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:50 node-1 multipathd: uevent trigger error
<27>Jul 26 21:45:50 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:14 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:21 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 26 21:46:30 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:31 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:31 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:31 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:31 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:31 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:35 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:35 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:35 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:35 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:35 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:40 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:40 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:40 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:40 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:40 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:46 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:46 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:46 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:46 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:46 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:57 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 21:46:57 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:57 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:57 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:57 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:57 node-1 multipathd: uevent trigger error
<27>Jul 26 21:46:57 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:24 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:24 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:24 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:24 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:24 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:29 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:29 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:29 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:29 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:29 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:42 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:50 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:50 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:50 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:50 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:50 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:55 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:55 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:55 node-1 multipathd: uevent trigger error
<27>Jul 26 21:47:55 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:07 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:07 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:07 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:07 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:07 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:07 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:12 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:12 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:12 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:12 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:12 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:16 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:16 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:16 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:16 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:16 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:22 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:22 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:22 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:22 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:22 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:26 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:31 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:31 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:31 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:31 node-1 multipathd: uevent trigger error
<27>Jul 26 21:48:31 node-1 multipathd: uevent trigger error
<11>Jul 26 21:50:01 node-1 liberasurecode[28514]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:50:01 node-1 liberasurecode[28514]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:50:01 node-1 liberasurecode[28514]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:50:01 node-1 liberasurecode[28514]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
