Jul 28 11:58:00 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8370" x-info="http://www.rsyslog.com"] start
Jul 28 11:58:00 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 28 11:58:00 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 28 11:58:00 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 28 11:58:00 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 28 11:58:00 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 28 11:58:00 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 28 11:58:00 node-1 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 28 11:58:00 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=7211a690-b055-42f5-a8d1-1a53dadff6d0 nomdmonddf nomdmonisw
Jul 28 11:58:00 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 28 11:58:00 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 28 11:58:00 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 28 11:58:00 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 28 11:58:00 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 28 11:58:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 28 11:58:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 28 11:58:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 28 11:58:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 28 11:58:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 28 11:58:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 28 11:58:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 28 11:58:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 28 11:58:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 28 11:58:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 28 11:58:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 28 11:58:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 28 11:58:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 28 11:58:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 28 11:58:00 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 28 11:58:00 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 28 11:58:00 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 28 11:58:00 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 28 11:58:00 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 28 11:58:00 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 28 11:58:00 node-1 kernel: [    0.000000] No AGP bridge found
Jul 28 11:58:00 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 28 11:58:00 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 28 11:58:00 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 28 11:58:00 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 28 11:58:00 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 28 11:58:00 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 28 11:58:00 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 28 11:58:00 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 28 11:58:00 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 28 11:58:00 node-1 kernel: [    0.000000]   2 disabled
Jul 28 11:58:00 node-1 kernel: [    0.000000]   3 disabled
Jul 28 11:58:00 node-1 kernel: [    0.000000]   4 disabled
Jul 28 11:58:00 node-1 kernel: [    0.000000]   5 disabled
Jul 28 11:58:00 node-1 kernel: [    0.000000]   6 disabled
Jul 28 11:58:00 node-1 kernel: [    0.000000]   7 disabled
Jul 28 11:58:00 node-1 kernel: [    0.000000]   8 disabled
Jul 28 11:58:00 node-1 kernel: [    0.000000]   9 disabled
Jul 28 11:58:00 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 28 11:58:00 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 28 11:58:00 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 28 11:58:00 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 28 11:58:00 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 28 11:58:00 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 28 11:58:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 28 11:58:00 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 28 11:58:00 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 28 11:58:00 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 28 11:58:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 28 11:58:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 28 11:58:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 28 11:58:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 28 11:58:00 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 28 11:58:00 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 28 11:58:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 28 11:58:00 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 28 11:58:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 28 11:58:00 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 28 11:58:00 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 28 11:58:00 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 28 11:58:00 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 28 11:58:00 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 28 11:58:00 node-1 kernel: [    0.000000] Zone ranges:
Jul 28 11:58:00 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 28 11:58:00 node-1 kernel: [    0.000000] Early memory node ranges
Jul 28 11:58:00 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 28 11:58:00 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 28 11:58:00 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 28 11:58:00 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 28 11:58:00 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 28 11:58:00 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 28 11:58:00 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 28 11:58:00 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 28 11:58:00 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 28 11:58:00 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 28 11:58:00 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 28 11:58:00 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 28 11:58:00 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 28 11:58:00 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 28 11:58:00 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 28 11:58:00 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 28 11:58:00 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 28 11:58:00 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 28 11:58:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 28 11:58:00 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 28 11:58:00 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 28 11:58:00 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 28 11:58:00 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 28 11:58:00 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 28 11:58:00 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 28 11:58:00 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 28 11:58:00 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 28 11:58:00 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=7211a690-b055-42f5-a8d1-1a53dadff6d0 nomdmonddf nomdmonisw
Jul 28 11:58:00 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 28 11:58:00 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 28 11:58:00 node-1 kernel: [    0.000000] Checking aperture...
Jul 28 11:58:00 node-1 kernel: [    0.000000] No AGP bridge found
Jul 28 11:58:00 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 28 11:58:00 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 28 11:58:00 node-1 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 28 11:58:00 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 28 11:58:00 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 28 11:58:00 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 28 11:58:00 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 28 11:58:00 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 28 11:58:00 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 28 11:58:00 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 28 11:58:00 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 28 11:58:00 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 28 11:58:00 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 28 11:58:00 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 28 11:58:00 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 28 11:58:00 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 28 11:58:00 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 28 11:58:00 node-1 kernel: [    0.004000] tsc: Detected 3492.098 MHz processor
Jul 28 11:58:00 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.19 BogoMIPS (lpj=13968392)
Jul 28 11:58:00 node-1 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Jul 28 11:58:00 node-1 kernel: [    0.000046] Security Framework initialized
Jul 28 11:58:00 node-1 kernel: [    0.000065] AppArmor: AppArmor initialized
Jul 28 11:58:00 node-1 kernel: [    0.000066] Yama: becoming mindful.
Jul 28 11:58:00 node-1 kernel: [    0.001464] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 28 11:58:00 node-1 kernel: [    0.006368] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 28 11:58:00 node-1 kernel: [    0.008293] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 28 11:58:00 node-1 kernel: [    0.008322] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 28 11:58:00 node-1 kernel: [    0.008615] Initializing cgroup subsys memory
Jul 28 11:58:00 node-1 kernel: [    0.008623] Initializing cgroup subsys devices
Jul 28 11:58:00 node-1 kernel: [    0.008625] Initializing cgroup subsys freezer
Jul 28 11:58:00 node-1 kernel: [    0.008628] Initializing cgroup subsys blkio
Jul 28 11:58:00 node-1 kernel: [    0.008629] Initializing cgroup subsys perf_event
Jul 28 11:58:00 node-1 kernel: [    0.008632] Initializing cgroup subsys hugetlb
Jul 28 11:58:00 node-1 kernel: [    0.008651] CPU: Physical Processor ID: 0
Jul 28 11:58:00 node-1 kernel: [    0.008653] CPU: Processor Core ID: 0
Jul 28 11:58:00 node-1 kernel: [    0.008657] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 28 11:58:00 node-1 kernel: [    0.008657] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 28 11:58:00 node-1 kernel: [    0.009350] mce: CPU supports 22 MCE banks
Jul 28 11:58:00 node-1 kernel: [    0.009378] CPU0: Thermal monitoring enabled (TM1)
Jul 28 11:58:00 node-1 kernel: [    0.009399] process: using mwait in idle threads
Jul 28 11:58:00 node-1 kernel: [    0.009402] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 28 11:58:00 node-1 kernel: [    0.009402] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 28 11:58:00 node-1 kernel: [    0.009402] tlb_flushall_shift: 6
Jul 28 11:58:00 node-1 kernel: [    0.009492] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 28 11:58:00 node-1 kernel: [    0.010215] ACPI: Core revision 20131115
Jul 28 11:58:00 node-1 kernel: [    0.022894] ACPI: All ACPI Tables successfully acquired
Jul 28 11:58:00 node-1 kernel: [    0.023056] ftrace: allocating 28617 entries in 112 pages
Jul 28 11:58:00 node-1 kernel: [    0.031881] dmar: Host address width 46
Jul 28 11:58:00 node-1 kernel: [    0.031884] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 28 11:58:00 node-1 kernel: [    0.031889] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 28 11:58:00 node-1 kernel: [    0.031891] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 28 11:58:00 node-1 kernel: [    0.031895] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 28 11:58:00 node-1 kernel: [    0.031897] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 28 11:58:00 node-1 kernel: [    0.031898] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 28 11:58:00 node-1 kernel: [    0.031899] dmar: ATSR flags: 0x0
Jul 28 11:58:00 node-1 kernel: [    0.031900] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 28 11:58:00 node-1 kernel: [    0.031901] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 28 11:58:00 node-1 kernel: [    0.032018] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 28 11:58:00 node-1 kernel: [    0.032019] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 28 11:58:00 node-1 kernel: [    0.032020] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 28 11:58:00 node-1 kernel: [    0.032021] HPET id 0 under DRHD base 0xc7ffc000
Jul 28 11:58:00 node-1 kernel: [    0.032022] Your BIOS is broken and requested that x2apic be disabled.
Jul 28 11:58:00 node-1 kernel: [    0.032022] This will slightly decrease performance.
Jul 28 11:58:00 node-1 kernel: [    0.032022] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 28 11:58:00 node-1 kernel: [    0.032454] Enabled IRQ remapping in xapic mode
Jul 28 11:58:00 node-1 kernel: [    0.032455] x2apic not enabled, IRQ remapping is in xapic mode
Jul 28 11:58:00 node-1 kernel: [    0.032458] Switched APIC routing to physical flat.
Jul 28 11:58:00 node-1 kernel: [    0.033076] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 28 11:58:00 node-1 kernel: [    0.072728] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 28 11:58:00 node-1 kernel: [    0.072734] TSC deadline timer enabled
Jul 28 11:58:00 node-1 kernel: [    0.072741] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 28 11:58:00 node-1 kernel: [    0.072747] ... version:                3
Jul 28 11:58:00 node-1 kernel: [    0.072748] ... bit width:              48
Jul 28 11:58:00 node-1 kernel: [    0.072749] ... generic registers:      4
Jul 28 11:58:00 node-1 kernel: [    0.072750] ... value mask:             0000ffffffffffff
Jul 28 11:58:00 node-1 kernel: [    0.072751] ... max period:             0000ffffffffffff
Jul 28 11:58:00 node-1 kernel: [    0.072752] ... fixed-purpose events:   3
Jul 28 11:58:00 node-1 kernel: [    0.072753] ... event mask:             000000070000000f
Jul 28 11:58:00 node-1 kernel: [    0.074184] x86: Booting SMP configuration:
Jul 28 11:58:00 node-1 kernel: [    0.088390] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 28 11:58:00 node-1 kernel: [    0.074186] .... node  #0, CPUs:        #1  #2  #3
Jul 28 11:58:00 node-1 kernel: [    0.116300] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 28 11:58:00 node-1 kernel: [    0.270473] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 28 11:58:00 node-1 kernel: [    0.326092] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 28 11:58:00 node-1 kernel: [    0.383152] x86: Booted up 2 nodes, 16 CPUs
Jul 28 11:58:00 node-1 kernel: [    0.383155] smpboot: Total of 16 processors activated (111759.47 BogoMIPS)
Jul 28 11:58:00 node-1 kernel: [    0.407449] devtmpfs: initialized
Jul 28 11:58:00 node-1 kernel: [    0.410545] EVM: security.selinux
Jul 28 11:58:00 node-1 kernel: [    0.410547] EVM: security.SMACK64
Jul 28 11:58:00 node-1 kernel: [    0.410548] EVM: security.ima
Jul 28 11:58:00 node-1 kernel: [    0.410549] EVM: security.capability
Jul 28 11:58:00 node-1 kernel: [    0.410599] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 28 11:58:00 node-1 kernel: [    0.411282] pinctrl core: initialized pinctrl subsystem
Jul 28 11:58:00 node-1 kernel: [    0.411344] regulator-dummy: no parameters
Jul 28 11:58:00 node-1 kernel: [    0.411376] RTC time: 11:57:25, date: 07/28/16
Jul 28 11:58:00 node-1 kernel: [    0.411410] NET: Registered protocol family 16
Jul 28 11:58:00 node-1 kernel: [    0.411496] cpuidle: using governor ladder
Jul 28 11:58:00 node-1 kernel: [    0.411497] cpuidle: using governor menu
Jul 28 11:58:00 node-1 kernel: [    0.411532] ACPI: bus type PCI registered
Jul 28 11:58:00 node-1 kernel: [    0.411534] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 28 11:58:00 node-1 kernel: [    0.411580] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 28 11:58:00 node-1 kernel: [    0.411583] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 28 11:58:00 node-1 kernel: [    0.425328] PCI: Using configuration type 1 for base access
Jul 28 11:58:00 node-1 kernel: [    0.426343] bio: create slab <bio-0> at 0
Jul 28 11:58:00 node-1 kernel: [    0.426629] ACPI: Added _OSI(Module Device)
Jul 28 11:58:00 node-1 kernel: [    0.426631] ACPI: Added _OSI(Processor Device)
Jul 28 11:58:00 node-1 kernel: [    0.426632] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 28 11:58:00 node-1 kernel: [    0.426633] ACPI: Added _OSI(Processor Aggregator Device)
Jul 28 11:58:00 node-1 kernel: [    0.439283] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 28 11:58:00 node-1 kernel: [    0.454991] ACPI: Interpreter enabled
Jul 28 11:58:00 node-1 kernel: [    0.454996] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 28 11:58:00 node-1 kernel: [    0.455000] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 28 11:58:00 node-1 kernel: [    0.455003] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 28 11:58:00 node-1 kernel: [    0.455010] ACPI: (supports S0 S4 S5)
Jul 28 11:58:00 node-1 kernel: [    0.455011] ACPI: Using IOAPIC for interrupt routing
Jul 28 11:58:00 node-1 kernel: [    0.455051] HEST: Table parsing has been initialized.
Jul 28 11:58:00 node-1 kernel: [    0.455054] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 28 11:58:00 node-1 kernel: [    0.455604] ACPI: No dock devices found.
Jul 28 11:58:00 node-1 kernel: [    0.467161] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 28 11:58:00 node-1 kernel: [    0.467166] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 11:58:00 node-1 kernel: [    0.467170] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 28 11:58:00 node-1 kernel: [    0.467196] PCI host bridge to bus 0000:ff
Jul 28 11:58:00 node-1 kernel: [    0.467198] pci_bus 0000:ff: root bus resource [bus ff]
Jul 28 11:58:00 node-1 kernel: [    0.467206] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467244] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 28 11:58:00 node-1 kernel: [    0.467275] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467310] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467339] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 28 11:58:00 node-1 kernel: [    0.467369] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 28 11:58:00 node-1 kernel: [    0.467399] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467428] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467457] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467485] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467511] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467538] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467566] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467591] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467618] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467645] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467673] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467700] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467727] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 28 11:58:00 node-1 kernel: [    0.467755] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467781] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 28 11:58:00 node-1 kernel: [    0.467806] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467832] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467864] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 28 11:58:00 node-1 kernel: [    0.467900] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467933] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467963] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.467997] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468030] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468063] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468095] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468126] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468157] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468201] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468235] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468269] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468304] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468335] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468363] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468396] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468430] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468470] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468507] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468541] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468573] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468602] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468633] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468665] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468697] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468728] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468761] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468790] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468819] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468849] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468878] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468909] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.468943] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469001] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 28 11:58:00 node-1 kernel: [    0.469004] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 11:58:00 node-1 kernel: [    0.469006] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 28 11:58:00 node-1 kernel: [    0.469025] PCI host bridge to bus 0000:7f
Jul 28 11:58:00 node-1 kernel: [    0.469026] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 28 11:58:00 node-1 kernel: [    0.469031] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469059] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 28 11:58:00 node-1 kernel: [    0.469088] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469124] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469146] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 28 11:58:00 node-1 kernel: [    0.469171] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 28 11:58:00 node-1 kernel: [    0.469198] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469225] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469247] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469270] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469292] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469314] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469338] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469361] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469384] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469410] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469432] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469455] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469477] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 28 11:58:00 node-1 kernel: [    0.469501] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469523] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 28 11:58:00 node-1 kernel: [    0.469544] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469567] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469593] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 28 11:58:00 node-1 kernel: [    0.469625] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469651] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469679] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469706] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469731] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469759] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469786] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469814] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469839] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469867] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469895] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469924] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469951] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.469976] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470000] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470030] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470056] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470085] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470116] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470145] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470170] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470195] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470221] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470248] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470275] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470302] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470332] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470355] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470378] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470404] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470430] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470460] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.470487] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.471748] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 28 11:58:00 node-1 kernel: [    0.471752] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 11:58:00 node-1 kernel: [    0.472870] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 28 11:58:00 node-1 kernel: [    0.473382] PCI host bridge to bus 0000:00
Jul 28 11:58:00 node-1 kernel: [    0.473385] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 28 11:58:00 node-1 kernel: [    0.473386] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 28 11:58:00 node-1 kernel: [    0.473388] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 28 11:58:00 node-1 kernel: [    0.473389] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 28 11:58:00 node-1 kernel: [    0.473390] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 28 11:58:00 node-1 kernel: [    0.473392] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 28 11:58:00 node-1 kernel: [    0.473393] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 28 11:58:00 node-1 kernel: [    0.473399] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 28 11:58:00 node-1 kernel: [    0.473482] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 28 11:58:00 node-1 kernel: [    0.473512] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 28 11:58:00 node-1 kernel: [    0.473554] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 28 11:58:00 node-1 kernel: [    0.473574] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 28 11:58:00 node-1 kernel: [    0.473603] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 28 11:58:00 node-1 kernel: [    0.473643] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 28 11:58:00 node-1 kernel: [    0.473662] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 28 11:58:00 node-1 kernel: [    0.473691] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 28 11:58:00 node-1 kernel: [    0.473734] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 28 11:58:00 node-1 kernel: [    0.473752] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.473822] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.473899] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.473976] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 28 11:58:00 node-1 kernel: [    0.473981] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 28 11:58:00 node-1 kernel: [    0.474067] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 28 11:58:00 node-1 kernel: [    0.474216] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 28 11:58:00 node-1 kernel: [    0.474233] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 28 11:58:00 node-1 kernel: [    0.474311] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 28 11:58:00 node-1 kernel: [    0.474364] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 28 11:58:00 node-1 kernel: [    0.474386] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 28 11:58:00 node-1 kernel: [    0.474442] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 28 11:58:00 node-1 kernel: [    0.474485] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 28 11:58:00 node-1 kernel: [    0.474513] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 28 11:58:00 node-1 kernel: [    0.474569] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 28 11:58:00 node-1 kernel: [    0.474612] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 28 11:58:00 node-1 kernel: [    0.474637] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 28 11:58:00 node-1 kernel: [    0.474655] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 28 11:58:00 node-1 kernel: [    0.474732] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 28 11:58:00 node-1 kernel: [    0.474782] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 28 11:58:00 node-1 kernel: [    0.474808] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 28 11:58:00 node-1 kernel: [    0.475061] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 28 11:58:00 node-1 kernel: [    0.475067] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 28 11:58:00 node-1 kernel: [    0.475073] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 28 11:58:00 node-1 kernel: [    0.475079] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 28 11:58:00 node-1 kernel: [    0.475086] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 28 11:58:00 node-1 kernel: [    0.475116] pci 0000:01:00.0: supports D1 D2
Jul 28 11:58:00 node-1 kernel: [    0.485111] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 28 11:58:00 node-1 kernel: [    0.485117] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 28 11:58:00 node-1 kernel: [    0.485121] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 28 11:58:00 node-1 kernel: [    0.485273] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 28 11:58:00 node-1 kernel: [    0.485307] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 28 11:58:00 node-1 kernel: [    0.493108] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 28 11:58:00 node-1 kernel: [    0.493114] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 28 11:58:00 node-1 kernel: [    0.493118] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 11:58:00 node-1 kernel: [    0.493202] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 28 11:58:00 node-1 kernel: [    0.493289] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 28 11:58:00 node-1 kernel: [    0.493384] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 28 11:58:00 node-1 kernel: [    0.493442] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 28 11:58:00 node-1 kernel: [    0.493446] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 11:58:00 node-1 kernel: [    0.493448] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 11:58:00 node-1 kernel: [    0.493505] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 28 11:58:00 node-1 kernel: [    0.493627] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 28 11:58:00 node-1 kernel: [    0.493681] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 28 11:58:00 node-1 kernel: [    0.493684] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 11:58:00 node-1 kernel: [    0.493686] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 11:58:00 node-1 kernel: [    0.493735] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 28 11:58:00 node-1 kernel: [    0.493854] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 28 11:58:00 node-1 kernel: [    0.493894] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 28 11:58:00 node-1 kernel: [    0.494015] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 28 11:58:00 node-1 kernel: [    0.494054] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 28 11:58:00 node-1 kernel: [    0.494173] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 28 11:58:00 node-1 kernel: [    0.494211] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 28 11:58:00 node-1 kernel: [    0.494344] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 28 11:58:00 node-1 kernel: [    0.494388] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 28 11:58:00 node-1 kernel: [    0.494391] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 11:58:00 node-1 kernel: [    0.494393] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 11:58:00 node-1 kernel: [    0.494453] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 28 11:58:00 node-1 kernel: [    0.494515] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 28 11:58:00 node-1 kernel: [    0.494568] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 28 11:58:00 node-1 kernel: [    0.494609] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 28 11:58:00 node-1 kernel: [    0.494691] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 28 11:58:00 node-1 kernel: [    0.494797] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 28 11:58:00 node-1 kernel: [    0.494800] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 11:58:00 node-1 kernel: [    0.494802] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 28 11:58:00 node-1 kernel: [    0.494858] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 28 11:58:00 node-1 kernel: [    0.494911] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 28 11:58:00 node-1 kernel: [    0.494962] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 28 11:58:00 node-1 kernel: [    0.495174] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 28 11:58:00 node-1 kernel: [    0.495178] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 28 11:58:00 node-1 kernel: [    0.495261] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 28 11:58:00 node-1 kernel: [    0.495319] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 28 11:58:00 node-1 kernel: [    0.495367] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 28 11:58:00 node-1 kernel: [    0.495580] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 28 11:58:00 node-1 kernel: [    0.495583] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 28 11:58:00 node-1 kernel: [    0.495642] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 28 11:58:00 node-1 kernel: [    0.495703] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 28 11:58:00 node-1 kernel: [    0.495755] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 28 11:58:00 node-1 kernel: [    0.495976] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 28 11:58:00 node-1 kernel: [    0.495980] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 28 11:58:00 node-1 kernel: [    0.496154] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 28 11:58:00 node-1 kernel: [    0.496192] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 28 11:58:00 node-1 kernel: [    0.496267] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 28 11:58:00 node-1 kernel: [    0.496286] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 28 11:58:00 node-1 kernel: [    0.496299] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 28 11:58:00 node-1 kernel: [    0.496312] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 28 11:58:00 node-1 kernel: [    0.496362] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 28 11:58:00 node-1 kernel: [    0.501114] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 28 11:58:00 node-1 kernel: [    0.501135] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 28 11:58:00 node-1 kernel: [    0.501167] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 28 11:58:00 node-1 kernel: [    0.501656] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 28 11:58:00 node-1 kernel: [    0.501659] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 11:58:00 node-1 kernel: [    0.501783] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 28 11:58:00 node-1 kernel: [    0.501891] PCI host bridge to bus 0000:80
Jul 28 11:58:00 node-1 kernel: [    0.501893] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 28 11:58:00 node-1 kernel: [    0.501894] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 28 11:58:00 node-1 kernel: [    0.501896] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 28 11:58:00 node-1 kernel: [    0.501904] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.501968] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.502036] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 28 11:58:00 node-1 kernel: [    0.502099] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 28 11:58:00 node-1 kernel: [    0.502104] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 28 11:58:00 node-1 kernel: [    0.502175] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 28 11:58:00 node-1 kernel: [    0.502477] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 28 11:58:00 node-1 kernel: [    0.502508] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 28 11:58:00 node-1 kernel: [    0.502538] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 28 11:58:00 node-1 kernel: [    0.502567] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 28 11:58:00 node-1 kernel: [    0.502596] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 11:58:00 node-1 kernel: [    0.502626] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 11:58:00 node-1 kernel: [    0.502655] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 11:58:00 node-1 kernel: [    0.502685] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 11:58:00 node-1 kernel: [    0.502770] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 28 11:58:00 node-1 kernel: [    0.502775] ACPI: \_SB_.UNC1: notify handler is installed
Jul 28 11:58:00 node-1 kernel: [    0.502776] ACPI: \_SB_.UNC0: notify handler is installed
Jul 28 11:58:00 node-1 kernel: [    0.502791] ACPI: \_SB_.PCI0: notify handler is installed
Jul 28 11:58:00 node-1 kernel: [    0.502844] ACPI: \_SB_.PCI1: notify handler is installed
Jul 28 11:58:00 node-1 kernel: [    0.502924] Found 4 acpi root devices
Jul 28 11:58:00 node-1 kernel: [    0.503034] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 28 11:58:00 node-1 kernel: [    0.503036] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 28 11:58:00 node-1 kernel: [    0.503038] vgaarb: loaded
Jul 28 11:58:00 node-1 kernel: [    0.503039] vgaarb: bridge control possible 0000:0c:00.0
Jul 28 11:58:00 node-1 kernel: [    0.503164] SCSI subsystem initialized
Jul 28 11:58:00 node-1 kernel: [    0.503228] libata version 3.00 loaded.
Jul 28 11:58:00 node-1 kernel: [    0.503244] ACPI: bus type USB registered
Jul 28 11:58:00 node-1 kernel: [    0.503254] usbcore: registered new interface driver usbfs
Jul 28 11:58:00 node-1 kernel: [    0.503259] usbcore: registered new interface driver hub
Jul 28 11:58:00 node-1 kernel: [    0.503284] usbcore: registered new device driver usb
Jul 28 11:58:00 node-1 kernel: [    0.503452] PCI: Using ACPI for IRQ routing
Jul 28 11:58:00 node-1 kernel: [    0.507072] PCI: pci_cache_line_size set to 64 bytes
Jul 28 11:58:00 node-1 kernel: [    0.507283] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 28 11:58:00 node-1 kernel: [    0.507284] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 28 11:58:00 node-1 kernel: [    0.507285] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 28 11:58:00 node-1 kernel: [    0.507352] NetLabel: Initializing
Jul 28 11:58:00 node-1 kernel: [    0.507353] NetLabel:  domain hash size = 128
Jul 28 11:58:00 node-1 kernel: [    0.507354] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 28 11:58:00 node-1 kernel: [    0.507364] NetLabel:  unlabeled traffic allowed by default
Jul 28 11:58:00 node-1 kernel: [    0.507420] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 28 11:58:00 node-1 kernel: [    0.507424] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 28 11:58:00 node-1 kernel: [    0.509482] Switched to clocksource hpet
Jul 28 11:58:00 node-1 kernel: [    0.513390] AppArmor: AppArmor Filesystem Enabled
Jul 28 11:58:00 node-1 kernel: [    0.513405] pnp: PnP ACPI init
Jul 28 11:58:00 node-1 kernel: [    0.513412] ACPI: bus type PNP registered
Jul 28 11:58:00 node-1 kernel: [    0.513535] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 28 11:58:00 node-1 kernel: [    0.513543] pnp 00:01: [dma 4]
Jul 28 11:58:00 node-1 kernel: [    0.513555] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 28 11:58:00 node-1 kernel: [    0.513580] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 28 11:58:00 node-1 kernel: [    0.513600] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 28 11:58:00 node-1 kernel: [    0.513617] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 28 11:58:00 node-1 kernel: [    0.513649] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 28 11:58:00 node-1 kernel: [    0.513702] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 28 11:58:00 node-1 kernel: [    0.513704] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 28 11:58:00 node-1 kernel: [    0.513706] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 28 11:58:00 node-1 kernel: [    0.513707] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 28 11:58:00 node-1 kernel: [    0.513709] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 28 11:58:00 node-1 kernel: [    0.513713] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 28 11:58:00 node-1 kernel: [    0.513715] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 28 11:58:00 node-1 kernel: [    0.513717] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 28 11:58:00 node-1 kernel: [    0.513718] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 28 11:58:00 node-1 kernel: [    0.513720] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 28 11:58:00 node-1 kernel: [    0.513721] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 28 11:58:00 node-1 kernel: [    0.513723] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 28 11:58:00 node-1 kernel: [    0.513724] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 28 11:58:00 node-1 kernel: [    0.513727] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 28 11:58:00 node-1 kernel: [    0.513810] pnp 00:07: [dma 0 disabled]
Jul 28 11:58:00 node-1 kernel: [    0.513838] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 28 11:58:00 node-1 kernel: [    0.513913] pnp 00:08: [dma 0 disabled]
Jul 28 11:58:00 node-1 kernel: [    0.513944] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 28 11:58:00 node-1 kernel: [    0.513995] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 28 11:58:00 node-1 kernel: [    0.514356] pnp: PnP ACPI: found 10 devices
Jul 28 11:58:00 node-1 kernel: [    0.514357] ACPI: bus type PNP unregistered
Jul 28 11:58:00 node-1 kernel: [    0.520795] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 28 11:58:00 node-1 kernel: [    0.520799] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 28 11:58:00 node-1 kernel: [    0.520801] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 28 11:58:00 node-1 kernel: [    0.520806] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 28 11:58:00 node-1 kernel: [    0.520807] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 11:58:00 node-1 kernel: [    0.520822] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 28 11:58:00 node-1 kernel: [    0.520851] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 28 11:58:00 node-1 kernel: [    0.520866] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 28 11:58:00 node-1 kernel: [    0.520895] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 28 11:58:00 node-1 kernel: [    0.520909] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 28 11:58:00 node-1 kernel: [    0.520938] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 28 11:58:00 node-1 kernel: [    0.520953] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 28 11:58:00 node-1 kernel: [    0.520981] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 28 11:58:00 node-1 kernel: [    0.520983] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 11:58:00 node-1 kernel: [    0.520998] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 11:58:00 node-1 kernel: [    0.521027] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 28 11:58:00 node-1 kernel: [    0.521029] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 11:58:00 node-1 kernel: [    0.521044] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 11:58:00 node-1 kernel: [    0.521072] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 28 11:58:00 node-1 kernel: [    0.521074] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 11:58:00 node-1 kernel: [    0.521077] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 11:58:00 node-1 kernel: [    0.521081] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 28 11:58:00 node-1 kernel: [    0.521083] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 28 11:58:00 node-1 kernel: [    0.521085] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 11:58:00 node-1 kernel: [    0.521089] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 28 11:58:00 node-1 kernel: [    0.521094] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 28 11:58:00 node-1 kernel: [    0.521102] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 28 11:58:00 node-1 kernel: [    0.521105] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 28 11:58:00 node-1 kernel: [    0.521111] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 28 11:58:00 node-1 kernel: [    0.521112] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 28 11:58:00 node-1 kernel: [    0.521113] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 28 11:58:00 node-1 kernel: [    0.521114] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 28 11:58:00 node-1 kernel: [    0.521115] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 28 11:58:00 node-1 kernel: [    0.521116] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 28 11:58:00 node-1 kernel: [    0.521117] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 28 11:58:00 node-1 kernel: [    0.521117] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 28 11:58:00 node-1 kernel: [    0.521118] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 28 11:58:00 node-1 kernel: [    0.521119] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 28 11:58:00 node-1 kernel: [    0.521120] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 28 11:58:00 node-1 kernel: [    0.521121] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 28 11:58:00 node-1 kernel: [    0.521122] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 28 11:58:00 node-1 kernel: [    0.521123] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 28 11:58:00 node-1 kernel: [    0.521123] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 28 11:58:00 node-1 kernel: [    0.521124] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 28 11:58:00 node-1 kernel: [    0.521125] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 28 11:58:00 node-1 kernel: [    0.521126] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 28 11:58:00 node-1 kernel: [    0.521127] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 28 11:58:00 node-1 kernel: [    0.521128] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 28 11:58:00 node-1 kernel: [    0.521129] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 28 11:58:00 node-1 kernel: [    0.521130] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 28 11:58:00 node-1 kernel: [    0.521132] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 28 11:58:00 node-1 kernel: [    0.521133] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 28 11:58:00 node-1 kernel: [    0.521172] NET: Registered protocol family 2
Jul 28 11:58:00 node-1 kernel: [    0.521427] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 28 11:58:00 node-1 kernel: [    0.521765] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 28 11:58:00 node-1 kernel: [    0.521910] TCP: Hash tables configured (established 262144 bind 65536)
Jul 28 11:58:00 node-1 kernel: [    0.521954] TCP: reno registered
Jul 28 11:58:00 node-1 kernel: [    0.521982] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 28 11:58:00 node-1 kernel: [    0.522077] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 28 11:58:00 node-1 kernel: [    0.522224] NET: Registered protocol family 1
Jul 28 11:58:00 node-1 kernel: [    0.561579] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 28 11:58:00 node-1 kernel: [    0.561593] PCI: CLS 64 bytes, default 64
Jul 28 11:58:00 node-1 kernel: [    0.561669] Trying to unpack rootfs image as initramfs...
Jul 28 11:58:00 node-1 kernel: [    0.781015] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 28 11:58:00 node-1 kernel: [    0.781051] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 28 11:58:00 node-1 kernel: [    0.781053] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 28 11:58:00 node-1 kernel: [    0.781468] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 11:58:00 node-1 kernel: [    0.781474] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 11:58:00 node-1 kernel: [    0.781479] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 11:58:00 node-1 kernel: [    0.781485] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 11:58:00 node-1 kernel: [    0.781497] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 11:58:00 node-1 kernel: [    0.781514] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 11:58:00 node-1 kernel: [    0.781529] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 11:58:00 node-1 kernel: [    0.781545] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 11:58:00 node-1 kernel: [    0.781556] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 11:58:00 node-1 kernel: [    0.781565] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 11:58:00 node-1 kernel: [    0.781572] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 11:58:00 node-1 kernel: [    0.781578] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 11:58:00 node-1 kernel: [    0.781587] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 11:58:00 node-1 kernel: [    0.781599] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 11:58:00 node-1 kernel: [    0.781612] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 11:58:00 node-1 kernel: [    0.781624] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 11:58:00 node-1 kernel: [    0.781744] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 28 11:58:00 node-1 kernel: [    0.781750] Scanning for low memory corruption every 60 seconds
Jul 28 11:58:00 node-1 kernel: [    0.782192] Initialise system trusted keyring
Jul 28 11:58:00 node-1 kernel: [    0.782252] audit: initializing netlink socket (disabled)
Jul 28 11:58:00 node-1 kernel: [    0.782268] type=2000 audit(1469707044.736:1): initialized
Jul 28 11:58:00 node-1 kernel: [    0.800194] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 28 11:58:00 node-1 kernel: [    0.801738] zbud: loaded
Jul 28 11:58:00 node-1 kernel: [    0.801865] VFS: Disk quotas dquot_6.5.2
Jul 28 11:58:00 node-1 kernel: [    0.801902] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 28 11:58:00 node-1 kernel: [    0.802277] fuse init (API version 7.22)
Jul 28 11:58:00 node-1 kernel: [    0.802333] msgmni has been set to 32768
Jul 28 11:58:00 node-1 kernel: [    0.802387] Key type big_key registered
Jul 28 11:58:00 node-1 kernel: [    0.802884] Key type asymmetric registered
Jul 28 11:58:00 node-1 kernel: [    0.802886] Asymmetric key parser 'x509' registered
Jul 28 11:58:00 node-1 kernel: [    0.802908] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 28 11:58:00 node-1 kernel: [    0.802978] io scheduler noop registered
Jul 28 11:58:00 node-1 kernel: [    0.802979] io scheduler deadline registered (default)
Jul 28 11:58:00 node-1 kernel: [    0.803002] io scheduler cfq registered
Jul 28 11:58:00 node-1 kernel: [    0.803539] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    0.803741] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    0.803869] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    0.803975] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    0.804085] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    0.804174] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    0.804535] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 28 11:58:00 node-1 kernel: [    0.804560] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 28 11:58:00 node-1 kernel: [    0.804576] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 28 11:58:00 node-1 kernel: [    0.804589] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804592] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804594] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 28 11:58:00 node-1 kernel: [    0.804599] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804601] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804602] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804604] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804606] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804607] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804608] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804610] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804611] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804612] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804614] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804615] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804617] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 28 11:58:00 node-1 kernel: [    0.804622] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804625] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 28 11:58:00 node-1 kernel: [    0.804636] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804639] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 28 11:58:00 node-1 kernel: [    0.804649] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804651] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 28 11:58:00 node-1 kernel: [    0.804654] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 28 11:58:00 node-1 kernel: [    0.804682] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 28 11:58:00 node-1 kernel: [    0.804688] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 28 11:58:00 node-1 kernel: [    0.804693] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 28 11:58:00 node-1 kernel: [    0.804711] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 28 11:58:00 node-1 kernel: [    0.804751] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 28 11:58:00 node-1 kernel: [    0.804752] vesafb: scrolling: redraw
Jul 28 11:58:00 node-1 kernel: [    0.804754] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 28 11:58:00 node-1 kernel: [    0.825555] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 28 11:58:00 node-1 kernel: [    0.834093] Console: switching to colour frame buffer device 80x30
Jul 28 11:58:00 node-1 kernel: [    0.842764] fb0: VESA VGA frame buffer device
Jul 28 11:58:00 node-1 kernel: [    0.842960] intel_idle: MWAIT substates: 0x2120
Jul 28 11:58:00 node-1 kernel: [    0.842961] intel_idle: v0.4 model 0x3F
Jul 28 11:58:00 node-1 kernel: [    0.842961] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 28 11:58:00 node-1 kernel: [    0.843172] ipmi message handler version 39.2
Jul 28 11:58:00 node-1 kernel: [    0.843452] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 28 11:58:00 node-1 kernel: [    0.843884] ACPI: AC Adapter [P111] (on-line)
Jul 28 11:58:00 node-1 kernel: [    0.849116] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 28 11:58:00 node-1 kernel: [    0.860118] ACPI: Power Button [PWRB]
Jul 28 11:58:00 node-1 kernel: [    0.865866] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 28 11:58:00 node-1 kernel: [    0.877479] ACPI: Power Button [PWRF]
Jul 28 11:58:00 node-1 kernel: [    0.902998] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 28 11:58:00 node-1 kernel: [    0.914640] pstore: Registered erst as persistent store backend
Jul 28 11:58:00 node-1 kernel: [    0.920831] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 28 11:58:00 node-1 kernel: [    0.932770] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 28 11:58:00 node-1 kernel: [    0.959529] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 28 11:58:00 node-1 kernel: [    0.992831] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 28 11:58:00 node-1 kernel: [    1.006917] Linux agpgart interface v0.103
Jul 28 11:58:00 node-1 kernel: [    1.014562] brd: module loaded
Jul 28 11:58:00 node-1 kernel: [    1.021576] loop: module loaded
Jul 28 11:58:00 node-1 kernel: [    1.028279] libphy: Fixed MDIO Bus: probed
Jul 28 11:58:00 node-1 kernel: [    1.034746] tun: Universal TUN/TAP device driver, 1.6
Jul 28 11:58:00 node-1 kernel: [    1.041208] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 28 11:58:00 node-1 kernel: [    1.047727] PPP generic driver version 2.4.2
Jul 28 11:58:00 node-1 kernel: [    1.054115] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 28 11:58:00 node-1 kernel: [    1.060548] ehci-pci: EHCI PCI platform driver
Jul 28 11:58:00 node-1 kernel: [    1.067060] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 28 11:58:00 node-1 kernel: [    1.073464] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 28 11:58:00 node-1 kernel: [    1.085989] ehci-pci 0000:00:1a.0: debug port 2
Jul 28 11:58:00 node-1 kernel: [    1.096206] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 28 11:58:00 node-1 kernel: [    1.096225] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 28 11:58:00 node-1 kernel: [    1.112975] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 28 11:58:00 node-1 kernel: [    1.119040] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 28 11:58:00 node-1 kernel: [    1.125223] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 28 11:58:00 node-1 kernel: [    1.137142] usb usb1: Product: EHCI Host Controller
Jul 28 11:58:00 node-1 kernel: [    1.143169] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 28 11:58:00 node-1 kernel: [    1.149217] usb usb1: SerialNumber: 0000:00:1a.0
Jul 28 11:58:00 node-1 kernel: [    1.155186] hub 1-0:1.0: USB hub found
Jul 28 11:58:00 node-1 kernel: [    1.160952] hub 1-0:1.0: 2 ports detected
Jul 28 11:58:00 node-1 kernel: [    1.166761] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 28 11:58:00 node-1 kernel: [    1.172335] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 28 11:58:00 node-1 kernel: [    1.183223] ehci-pci 0000:00:1d.0: debug port 2
Jul 28 11:58:00 node-1 kernel: [    1.192526] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 28 11:58:00 node-1 kernel: [    1.192529] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 28 11:58:00 node-1 kernel: [    1.208894] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 28 11:58:00 node-1 kernel: [    1.214094] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 28 11:58:00 node-1 kernel: [    1.219391] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 28 11:58:00 node-1 kernel: [    1.229957] usb usb2: Product: EHCI Host Controller
Jul 28 11:58:00 node-1 kernel: [    1.235434] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 28 11:58:00 node-1 kernel: [    1.240976] usb usb2: SerialNumber: 0000:00:1d.0
Jul 28 11:58:00 node-1 kernel: [    1.246528] hub 2-0:1.0: USB hub found
Jul 28 11:58:00 node-1 kernel: [    1.251917] hub 2-0:1.0: 2 ports detected
Jul 28 11:58:00 node-1 kernel: [    1.257216] ehci-platform: EHCI generic platform driver
Jul 28 11:58:00 node-1 kernel: [    1.262452] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 28 11:58:00 node-1 kernel: [    1.267785] ohci-pci: OHCI PCI platform driver
Jul 28 11:58:00 node-1 kernel: [    1.273076] ohci-platform: OHCI generic platform driver
Jul 28 11:58:00 node-1 kernel: [    1.278277] uhci_hcd: USB Universal Host Controller Interface driver
Jul 28 11:58:00 node-1 kernel: [    1.283616] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 28 11:58:00 node-1 kernel: [    1.476672] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 28 11:58:00 node-1 kernel: [    1.672861] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 28 11:58:00 node-1 kernel: [    1.678428] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 28 11:58:00 node-1 kernel: [    1.684251] hub 1-1:1.0: USB hub found
Jul 28 11:58:00 node-1 kernel: [    1.689845] hub 1-1:1.0: 6 ports detected
Jul 28 11:58:00 node-1 kernel: [    1.776463] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 28 11:58:00 node-1 kernel: [    1.804387] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 28 11:58:00 node-1 kernel: [    2.072520] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 28 11:58:00 node-1 kernel: [    2.078034] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 28 11:58:00 node-1 kernel: [    2.083789] hub 2-1:1.0: USB hub found
Jul 28 11:58:00 node-1 kernel: [    2.089382] hub 2-1:1.0: 8 ports detected
Jul 28 11:58:00 node-1 kernel: [    2.325298] i8042: No controller found
Jul 28 11:58:00 node-1 kernel: [    2.330689] mousedev: PS/2 mouse device common for all mice
Jul 28 11:58:00 node-1 kernel: [    2.336174] rtc_cmos 00:02: RTC can wake from S4
Jul 28 11:58:00 node-1 kernel: [    2.341725] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 28 11:58:00 node-1 kernel: [    2.347265] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 28 11:58:00 node-1 kernel: [    2.358153] device-mapper: uevent: version 1.0.3
Jul 28 11:58:00 node-1 kernel: [    2.363647] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 28 11:58:00 node-1 kernel: [    2.364042] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 28 11:58:00 node-1 kernel: [    2.380316] ledtrig-cpu: registered to indicate activity on CPUs
Jul 28 11:58:00 node-1 kernel: [    2.386194] TCP: cubic registered
Jul 28 11:58:00 node-1 kernel: [    2.392040] NET: Registered protocol family 10
Jul 28 11:58:00 node-1 kernel: [    2.397972] NET: Registered protocol family 17
Jul 28 11:58:00 node-1 kernel: [    2.403611] Key type dns_resolver registered
Jul 28 11:58:00 node-1 kernel: [    2.409635] Loading compiled-in X.509 certificates
Jul 28 11:58:00 node-1 kernel: [    2.415767] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 28 11:58:00 node-1 kernel: [    2.427072] registered taskstats version 1
Jul 28 11:58:00 node-1 kernel: [    2.434935] Key type trusted registered
Jul 28 11:58:00 node-1 kernel: [    2.442398] Key type encrypted registered
Jul 28 11:58:00 node-1 kernel: [    2.447816] AppArmor: AppArmor sha1 policy hashing enabled
Jul 28 11:58:00 node-1 kernel: [    2.453266] IMA: No TPM chip found, activating TPM-bypass!
Jul 28 11:58:00 node-1 kernel: [    2.459366] regulator-dummy: disabling
Jul 28 11:58:00 node-1 kernel: [    2.464851]   Magic number: 8:718:985
Jul 28 11:58:00 node-1 kernel: [    2.470452] rtc_cmos 00:02: setting system clock to 2016-07-28 11:57:27 UTC (1469707047)
Jul 28 11:58:00 node-1 kernel: [    2.482755] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 28 11:58:00 node-1 kernel: [    2.488351] EDD information not available.
Jul 28 11:58:00 node-1 kernel: [    2.493997] PM: Hibernation image not present or could not be loaded.
Jul 28 11:58:00 node-1 kernel: [    2.494854] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 28 11:58:00 node-1 kernel: [    2.501003] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 28 11:58:00 node-1 kernel: [    2.501004] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 28 11:58:00 node-1 kernel: [    2.501005] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 28 11:58:00 node-1 kernel: [    2.501006] usb 2-1.4: Manufacturer: Avocent
Jul 28 11:58:00 node-1 kernel: [    2.501006] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 28 11:58:00 node-1 kernel: [    2.542096] Write protecting the kernel read-only data: 12288k
Jul 28 11:58:00 node-1 kernel: [    2.548346] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 28 11:58:00 node-1 kernel: [    2.560826] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 28 11:58:00 node-1 kernel: [    2.592475] device-mapper: multipath: version 1.6.0 loaded
Jul 28 11:58:00 node-1 kernel: [    2.600481] systemd-udevd[217]: starting version 204
Jul 28 11:58:00 node-1 kernel: [    2.625478] md: linear personality registered for level -1
Jul 28 11:58:00 node-1 kernel: [    2.640113] md: multipath personality registered for level -4
Jul 28 11:58:00 node-1 kernel: [    2.648088] md: raid0 personality registered for level 0
Jul 28 11:58:00 node-1 kernel: [    2.656566] md: raid1 personality registered for level 1
Jul 28 11:58:00 node-1 kernel: [    2.665231] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 28 11:58:00 node-1 kernel: [    2.671580] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 28 11:58:00 node-1 kernel: [    2.677945] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 28 11:58:00 node-1 kernel: [    2.677957] hidraw: raw HID events driver (C) Jiri Kosina
Jul 28 11:58:00 node-1 kernel: [    2.679267] megasas: FW now in Ready state
Jul 28 11:58:00 node-1 kernel: [    2.679598] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.679896] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.680029] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.680151] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.680245] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.680384] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.680440] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.680538] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.680637] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.680753] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.680841] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.680969] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.681200] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.681369] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.681529] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.681613] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.682177] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 28 11:58:00 node-1 kernel: [    2.712309] usbcore: registered new interface driver usbhid
Jul 28 11:58:00 node-1 kernel: [    2.718682] usbhid: USB HID core driver
Jul 28 11:58:00 node-1 kernel: [    2.719269] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 28 11:58:00 node-1 kernel: [    2.719280] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 28 11:58:00 node-1 kernel: [    2.719323] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 11:58:00 node-1 kernel: [    2.719946] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.720032] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.720079] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.720130] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.720389] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.731613] raid6: sse2x1   11159 MB/s
Jul 28 11:58:00 node-1 kernel: [    2.736856] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 28 11:58:00 node-1 kernel: [    2.736875] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 28 11:58:00 node-1 kernel: [    2.736878] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 11:58:00 node-1 kernel: [    2.737316] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.737421] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.737534] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.737599] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.737834] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.753288] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 28 11:58:00 node-1 kernel: [    2.753301] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 28 11:58:00 node-1 kernel: [    2.753328] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 11:58:00 node-1 kernel: [    2.753627] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.753694] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.753771] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.753868] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.754195] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.765883] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 28 11:58:00 node-1 kernel: [    2.765884] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 28 11:58:00 node-1 kernel: [    2.765886] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 11:58:00 node-1 kernel: [    2.766105] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.766195] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.766261] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.766358] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.766590] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 11:58:00 node-1 kernel: [    2.799728] raid6: sse2x2   12538 MB/s
Jul 28 11:58:00 node-1 kernel: [    2.867716] raid6: sse2x4    9569 MB/s
Jul 28 11:58:00 node-1 kernel: [    2.935450] raid6: avx2x1   14149 MB/s
Jul 28 11:58:00 node-1 kernel: [    3.007386] raid6: avx2x2   18852 MB/s
Jul 28 11:58:00 node-1 kernel: [    3.079319] raid6: avx2x4   21317 MB/s
Jul 28 11:58:00 node-1 kernel: [    3.085243] raid6: using algorithm avx2x4 (21317 MB/s)
Jul 28 11:58:00 node-1 kernel: [    3.091371] raid6: using avx2x2 recovery algorithm
Jul 28 11:58:00 node-1 kernel: [    3.097310] megasas:IOC Init cmd success
Jul 28 11:58:00 node-1 kernel: [    3.097311] Switched to clocksource tsc
Jul 28 11:58:00 node-1 kernel: [    3.109842] xor: automatically using best checksumming function:
Jul 28 11:58:00 node-1 kernel: [    3.125540] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Jul 28 11:58:00 node-1 kernel: [    3.131321] megasas: INIT adapter done
Jul 28 11:58:00 node-1 kernel: [    3.142851] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Jul 28 11:58:00 node-1 kernel: [    3.154767] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Jul 28 11:58:00 node-1 kernel: [    3.155289]    avx       : 35634.000 MB/sec
Jul 28 11:58:00 node-1 kernel: [    3.172477] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Jul 28 11:58:00 node-1 kernel: [    3.184275] async_tx: api initialized (async)
Jul 28 11:58:00 node-1 kernel: [    3.184436] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Jul 28 11:58:00 node-1 kernel: [    3.185338] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Jul 28 11:58:00 node-1 kernel: [    3.203248] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 28 11:58:00 node-1 kernel: [    3.203655] scsi0 : LSI SAS based MegaRAID driver
Jul 28 11:58:00 node-1 kernel: [    3.210809] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 28 11:58:00 node-1 kernel: [    3.222016] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 28 11:58:00 node-1 kernel: [    3.226217] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 28 11:58:00 node-1 kernel: [    3.226532] sd 0:2:0:0: [sda] Write Protect is off
Jul 28 11:58:00 node-1 kernel: [    3.226533] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 28 11:58:00 node-1 kernel: [    3.226605] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 28 11:58:00 node-1 kernel: [    3.226696] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 28 11:58:00 node-1 kernel: [    3.257024]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 28 11:58:00 node-1 kernel: [    3.258814] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 28 11:58:00 node-1 kernel: [    3.310684] md: raid6 personality registered for level 6
Jul 28 11:58:00 node-1 kernel: [    3.317804] md: raid5 personality registered for level 5
Jul 28 11:58:00 node-1 kernel: [    3.324716] md: raid4 personality registered for level 4
Jul 28 11:58:00 node-1 kernel: [    3.334399] md: raid10 personality registered for level 10
Jul 28 11:58:00 node-1 kernel: [    3.388284] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Jul 28 11:58:00 node-1 kernel: [    3.444076] random: lvm urandom read with 32 bits of entropy available
Jul 28 11:58:00 node-1 kernel: [    3.553948] bio: create slab <bio-1> at 1
Jul 28 11:58:00 node-1 kernel: [    4.273591] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 11:58:00 node-1 kernel: [    4.936610] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 28 11:58:00 node-1 kernel: [    4.967077] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 28 11:58:00 node-1 kernel: [    5.054465] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 28 11:58:00 node-1 kernel: [    5.108395] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 28 11:58:00 node-1 kernel: [    5.177125] random: nonblocking pool is initialized
Jul 28 11:58:00 node-1 kernel: [    5.250262] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 11:58:00 node-1 kernel: [    5.431496] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 28 11:58:00 node-1 kernel: [    5.468421] XFS (dm-0): Mounting Filesystem
Jul 28 11:58:00 node-1 kernel: [    5.761610] XFS (dm-0): Ending clean mount
Jul 28 11:58:00 node-1 kernel: [    5.792927] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 11:58:00 node-1 kernel: [    5.818490] XFS (dm-1): Mounting Filesystem
Jul 28 11:58:00 node-1 kernel: [    5.905180] XFS (dm-1): Ending clean mount
Jul 28 11:58:00 node-1 kernel: [    7.613893] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 28 11:58:00 node-1 kernel: [    7.627749] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 28 11:58:00 node-1 kernel: [    7.797114] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 28 11:58:00 node-1 kernel: [    7.797118] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 28 11:58:00 node-1 kernel: [    7.797122] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 28 11:58:00 node-1 kernel: [    7.797125] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 28 11:58:00 node-1 kernel: [    7.817188] systemd-udevd[776]: starting version 204
Jul 28 11:58:00 node-1 kernel: [    8.004298] power_meter ACPI000D:00: Found ACPI power meter.
Jul 28 11:58:00 node-1 kernel: [    8.004308] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 28 11:58:00 node-1 kernel: [    8.017465] IPMI System Interface driver.
Jul 28 11:58:00 node-1 kernel: [    8.017559] ipmi_si: probing via ACPI
Jul 28 11:58:00 node-1 kernel: [    8.017573] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 28 11:58:00 node-1 kernel: [    8.017574] ipmi_si: Adding ACPI-specified kcs state machine
Jul 28 11:58:00 node-1 kernel: [    8.017599] ipmi_si: probing via SMBIOS
Jul 28 11:58:00 node-1 kernel: [    8.017600] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 28 11:58:00 node-1 kernel: [    8.017601] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 28 11:58:00 node-1 kernel: [    8.017603] ipmi_si: probing via SPMI
Jul 28 11:58:00 node-1 kernel: [    8.017605] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 28 11:58:00 node-1 kernel: [    8.017605] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 28 11:58:00 node-1 kernel: [    8.017607] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 28 11:58:00 node-1 kernel: [    8.048711] wmi: Mapper loaded
Jul 28 11:58:00 node-1 kernel: [    8.049766] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 28 11:58:00 node-1 kernel: [    8.049771] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 11:58:00 node-1 kernel: [    8.049774] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 28 11:58:00 node-1 kernel: [    8.049775] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 11:58:00 node-1 kernel: [    8.049801] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 28 11:58:00 node-1 kernel: [    8.103887] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 28 11:58:00 node-1 kernel: [    8.163102] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 28 11:58:00 node-1 kernel: [    8.163108] ipmi_si 00:09: IPMI kcs interface initialized
Jul 28 11:58:00 node-1 kernel: [    8.191459] systemd-udevd[805]: renamed network interface eth1 to enp7s0
Jul 28 11:58:00 node-1 kernel: [    8.217464] systemd-udevd[795]: renamed network interface eth0 to enp6s0
Jul 28 11:58:00 node-1 kernel: [    8.235377] systemd-udevd[793]: renamed network interface eth2 to enp8s0
Jul 28 11:58:00 node-1 kernel: [    8.251360] systemd-udevd[796]: renamed network interface eth3 to enp9s0
Jul 28 11:58:00 node-1 kernel: [    8.542807] type=1400 audit(1469707053.574:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1068 comm="apparmor_parser"
Jul 28 11:58:00 node-1 kernel: [    8.542961] type=1400 audit(1469707053.574:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1068 comm="apparmor_parser"
Jul 28 11:58:00 node-1 kernel: [    8.543086] type=1400 audit(1469707053.574:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1068 comm="apparmor_parser"
Jul 28 11:58:00 node-1 kernel: [    8.543950] type=1400 audit(1469707053.574:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1065 comm="apparmor_parser"
Jul 28 11:58:00 node-1 kernel: [    8.544098] type=1400 audit(1469707053.574:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1065 comm="apparmor_parser"
Jul 28 11:58:00 node-1 kernel: [    8.544218] type=1400 audit(1469707053.574:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1065 comm="apparmor_parser"
Jul 28 11:58:00 node-1 kernel: [    8.549238] type=1400 audit(1469707053.578:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1069 comm="apparmor_parser"
Jul 28 11:58:00 node-1 kernel: [    8.549387] type=1400 audit(1469707053.578:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1069 comm="apparmor_parser"
Jul 28 11:58:00 node-1 kernel: [    8.549505] type=1400 audit(1469707053.578:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1069 comm="apparmor_parser"
Jul 28 11:58:00 node-1 kernel: [    8.550479] type=1400 audit(1469707053.578:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1067 comm="apparmor_parser"
Jul 28 11:58:00 node-1 kernel: [    9.049757] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 28 11:58:00 node-1 kernel: [    9.052242] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 28 11:58:00 node-1 kernel: [    9.256261] enic 0000:06:00.0 enp6s0: Link UP
Jul 28 11:58:00 node-1 kernel: [    9.257282] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 28 11:58:00 node-1 kernel: [    9.257287] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 28 11:58:00 node-1 kernel: [   18.982289] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 28 11:58:00 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 28 11:58:01 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 28 11:58:01 node-1 kernel: [   37.392019] init: failsafe main process (8397) killed by TERM signal
Jul 28 11:58:01 node-1 dbus[8434]: [system] AppArmor D-Bus mediation is enabled
Jul 28 11:58:02 node-1 kernel: [   37.646569] audit_printk_skb: 30 callbacks suppressed
Jul 28 11:58:02 node-1 kernel: [   37.646570] type=1400 audit(1469707082.023:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8523 comm="apparmor_parser"
Jul 28 11:58:02 node-1 kernel: [   37.647637] type=1400 audit(1469707082.023:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8522 comm="apparmor_parser"
Jul 28 11:58:02 node-1 kernel: [   37.647640] type=1400 audit(1469707082.023:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8522 comm="apparmor_parser"
Jul 28 11:58:02 node-1 kernel: [   37.647642] type=1400 audit(1469707082.023:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8522 comm="apparmor_parser"
Jul 28 11:58:02 node-1 kernel: [   37.647858] type=1400 audit(1469707082.023:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8522 comm="apparmor_parser"
Jul 28 11:58:02 node-1 kernel: [   37.647860] type=1400 audit(1469707082.023:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8522 comm="apparmor_parser"
Jul 28 11:58:02 node-1 kernel: [   37.647973] type=1400 audit(1469707082.023:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8522 comm="apparmor_parser"
Jul 28 11:58:02 node-1 kernel: [   37.713985] type=1400 audit(1469707082.091:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8525 comm="apparmor_parser"
Jul 28 11:58:02 node-1 anacron[8590]: Anacron 2.3 started on 2016-07-28
Jul 28 11:58:02 node-1 cron[8555]: (CRON) INFO (pidfile fd = 3)
Jul 28 11:58:02 node-1 cron[8597]: (CRON) STARTUP (fork ok)
Jul 28 11:58:02 node-1 anacron[8590]: Will run job `cron.daily' in 5 min.
Jul 28 11:58:02 node-1 anacron[8590]: Will run job `cron.weekly' in 10 min.
Jul 28 11:58:02 node-1 anacron[8590]: Will run job `cron.monthly' in 15 min.
Jul 28 11:58:02 node-1 anacron[8590]: Jobs will be executed sequentially
Jul 28 11:58:02 node-1 multipathd: path checkers start up
Jul 28 11:58:02 node-1 cron[8597]: (CRON) INFO (Running @reboot jobs)
Jul 28 11:58:02 node-1 postfix/master[8734]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 28 11:58:05 node-1 puppet-agent[8919]: Reopening log files
Jul 28 11:58:05 node-1 puppet-agent[8919]: Could not request certificate: Connection refused - connect(2)
Jul 28 11:58:19 node-1 puppet-user[9127]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 28 11:58:19 node-1 puppet-user[9127]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 28 11:58:20 node-1 puppet-user[9127]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 28 11:58:20 node-1 puppet-user[9127]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 28 11:58:20 node-1 puppet-user[9127]: Finished catalog run in 0.83 seconds
Jul 28 11:58:22 node-1 multipathd: uevent trigger error
Jul 28 11:58:22 node-1 puppet-user[9552]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 28 11:58:22 node-1 puppet-user[9552]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Jul 28 11:58:22 node-1 puppet-user[9552]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 28 11:58:22 node-1 puppet-user[9552]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 28 11:58:22 node-1 puppet-user[9552]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Jul 28 11:58:22 node-1 puppet-user[9552]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 28 11:58:22 node-1 puppet-user[9552]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 28 11:58:22 node-1 puppet-user[9552]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 28 11:58:22 node-1 puppet-user[9552]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 28 11:58:22 node-1 puppet-user[9552]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 28 11:58:22 node-1 puppet-user[9552]: Finished catalog run in 0.05 seconds
Jul 28 11:58:23 node-1 puppet-user[10009]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 28 11:58:23 node-1 puppet-user[10009]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 28 11:58:23 node-1 puppet-user[10009]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 28 11:58:23 node-1 puppet-user[10009]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 28 11:58:23 node-1 puppet-user[10009]: Finished catalog run in 0.03 seconds
Jul 28 11:58:25 node-1 puppet-user[10472]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 28 11:58:25 node-1 puppet-user[10472]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 28 11:58:25 node-1 puppet-user[10472]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 28 11:58:25 node-1 puppet-user[10472]: Finished catalog run in 0.04 seconds
Jul 28 11:58:26 node-1 puppet-user[10919]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 28 11:58:26 node-1 puppet-user[10919]: Compiled catalog for node-1.domain.tld in environment production in 0.18 seconds
Jul 28 11:58:27 node-1 puppet-user[10919]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 28 11:58:27 node-1 puppet-user[10919]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Jul 28 11:58:27 node-1 puppet-user[10919]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Jul 28 11:58:27 node-1 puppet-user[10919]: Finished catalog run in 0.80 seconds
Jul 28 11:58:29 node-1 puppet-user[11601]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 28 11:58:29 node-1 puppet-user[11601]: Compiled catalog for node-1.domain.tld in environment production in 0.22 seconds
Jul 28 11:58:29 node-1 puppet-user[11601]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Jul 28 11:58:29 node-1 puppet-user[11601]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 28 11:58:29 node-1 puppet-user[11601]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 28 11:58:29 node-1 puppet-user[11601]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Jul 28 11:58:29 node-1 puppet-user[11601]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 28 11:58:29 node-1 puppet-user[11601]: Finished catalog run in 0.31 seconds
Jul 28 11:58:31 node-1 puppet-user[12079]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 28 11:58:31 node-1 puppet-user[12079]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Jul 28 11:58:31 node-1 puppet-user[12079]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 28 11:58:31 node-1 kernel: [   66.732486] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 28 11:58:31 node-1 kernel: [   66.732538] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Jul 28 11:58:31 node-1 puppet-user[12079]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Jul 28 11:58:31 node-1 puppet-user[12079]: Finished catalog run in 0.05 seconds
Jul 28 11:58:33 node-1 puppet-user[12546]: (Scope(Class[main])) MODULAR: sync_time
Jul 28 11:58:33 node-1 puppet-user[12546]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 28 11:58:33 node-1 ntpdate[12962]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 28 11:58:39 node-1 ntpdate[12962]: adjust time server 10.20.0.2 offset 0.000425 sec
Jul 28 11:58:39 node-1 puppet-user[12546]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 28 11:58:39 node-1 puppet-user[12546]: Finished catalog run in 6.18 seconds
Jul 28 11:58:40 node-1 kernel: [   75.347651] init: plymouth-upstart-bridge main process ended, respawning
Jul 28 11:58:40 node-1 puppet-agent[8919]: Could not run: SIGTERM
Jul 28 11:58:40 node-1 kernel: [   75.642123] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 28 11:58:40 node-1 ec2: 
Jul 28 11:58:40 node-1 ec2: #############################################################
Jul 28 11:58:40 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 28 11:58:40 node-1 ec2: 1024 37:34:cc:03:ea:ca:87:f5:0b:eb:c1:ce:c3:6f:e7:1d  root@node-1.domain.tld (DSA)
Jul 28 11:58:40 node-1 ec2: 256 90:c4:0f:80:94:29:d7:e8:94:a7:b7:0a:57:3e:a5:32  root@node-1.domain.tld (ECDSA)
Jul 28 11:58:40 node-1 ec2: 256 66:17:a3:01:0d:6b:3f:39:f9:09:dd:a1:4d:7c:6f:bb  root@node-1.domain.tld (ED25519)
Jul 28 11:58:40 node-1 ec2: 2048 67:d5:fa:76:8d:10:42:84:14:aa:a7:a6:87:62:39:ff  root@node-1.domain.tld (RSA)
Jul 28 11:58:40 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 28 11:58:40 node-1 ec2: #############################################################
Jul 28 11:59:01 node-1 CRON[13306]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 28 11:59:13 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 11:59:13 node-1 nailgun-agent: I, [2016-07-28T11:59:13.817545 #13309]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 28 11:59:26 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 11:59:26 node-1 nailgun-agent: I, [2016-07-28T11:59:26.831275 #13309]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 28 11:59:27 node-1 puppet-user[13476]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 28 11:59:27 node-1 puppet-user[13476]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Jul 28 11:59:27 node-1 puppet-user[13476]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 28 11:59:27 node-1 puppet-user[13476]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Jul 28 11:59:27 node-1 puppet-user[13476]: Finished catalog run in 0.07 seconds
Jul 28 11:59:29 node-1 puppet-user[14087]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 28 11:59:30 node-1 puppet-user[14087]: Compiled catalog for node-1.domain.tld in environment production in 1.23 seconds
Jul 28 11:59:31 node-1 puppet-user[14087]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Jul 28 11:59:31 node-1 puppet-user[14087]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Jul 28 11:59:31 node-1 puppet-user[14087]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Jul 28 11:59:31 node-1 puppet-user[14087]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 28 11:59:31 node-1 puppet-user[14087]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Jul 28 11:59:31 node-1 puppet-user[14087]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 28 11:59:31 node-1 puppet-user[14087]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 28 11:59:31 node-1 puppet-user[14087]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 28 11:59:31 node-1 puppet-user[14087]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 28 11:59:31 node-1 puppet-user[14087]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 28 11:59:31 node-1 puppet-user[14087]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 28 11:59:31 node-1 puppet-user[14087]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 28 11:59:31 node-1 puppet-user[14087]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 28 11:59:31 node-1 puppet-user[14087]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Jul 28 11:59:31 node-1 puppet-user[14087]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 28 11:59:31 node-1 puppet-user[14087]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 28 11:59:47 node-1 puppet-user[14087]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 28 11:59:47 node-1 puppet-user[14087]: Finished catalog run in 16.80 seconds
Jul 28 11:59:49 node-1 puppet-user[14973]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 28 11:59:50 node-1 puppet-user[14973]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Jul 28 11:59:54 node-1 puppet-user[14973]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 28 12:00:01 node-1 CRON[16205]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 28 12:00:24 node-1 puppet-user[14973]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 28 12:00:25 node-1 puppet-user[14973]: Finished catalog run in 34.83 seconds
Jul 28 12:00:26 node-1 puppet-user[17432]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 28 12:00:27 node-1 puppet-user[17432]: Compiled catalog for node-1.domain.tld in environment production in 0.61 seconds
Jul 28 12:00:27 node-1 puppet-user[17432]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 28 12:00:27 node-1 puppet-user[17432]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 28 12:00:27 node-1 puppet-user[17432]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 28 12:00:27 node-1 puppet-user[17432]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 28 12:00:27 node-1 puppet-user[17432]: Finished catalog run in 0.11 seconds
Jul 28 12:00:28 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 12:00:28 node-1 nailgun-agent: I, [2016-07-28T12:00:28.018641 #16210]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 28 12:00:29 node-1 puppet-user[17973]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 28 12:00:30 node-1 puppet-user[17973]: Compiled catalog for node-1.domain.tld in environment production in 0.85 seconds
Jul 28 12:00:30 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 28 12:00:30 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 28 12:00:30 node-1 crontab[18468]: (root) LIST (root)
Jul 28 12:00:30 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 28 12:00:30 node-1 crontab[18471]: (root) REPLACE (root)
Jul 28 12:00:33 node-1 puppet-user[17973]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 28 12:00:34 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 28 12:00:35 node-1 puppet-user[17973]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 28 12:00:35 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8370" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 12:00:35 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 28 12:00:37 node-1 multipathd: uevent trigger error
<27>Jul 28 12:00:37 node-1 multipathd: uevent trigger error
<27>Jul 28 12:00:37 node-1 multipathd: uevent trigger error
<27>Jul 28 12:00:37 node-1 multipathd: uevent trigger error
<27>Jul 28 12:00:37 node-1 multipathd: uevent trigger error
<27>Jul 28 12:00:55 node-1 multipathd: uevent trigger error
<27>Jul 28 12:00:55 node-1 multipathd: uevent trigger error
<27>Jul 28 12:00:55 node-1 multipathd: uevent trigger error
<27>Jul 28 12:00:55 node-1 multipathd: uevent trigger error
<27>Jul 28 12:00:58 node-1 multipathd: uevent trigger error
<27>Jul 28 12:00:58 node-1 multipathd: uevent trigger error
<27>Jul 28 12:00:58 node-1 multipathd: uevent trigger error
<27>Jul 28 12:00:58 node-1 multipathd: uevent trigger error
<27>Jul 28 12:00:58 node-1 multipathd: uevent trigger error
<27>Jul 28 12:01:00 node-1 multipathd: uevent trigger error
<27>Jul 28 12:01:00 node-1 multipathd: uevent trigger error
<27>Jul 28 12:01:00 node-1 multipathd: uevent trigger error
<27>Jul 28 12:01:00 node-1 multipathd: uevent trigger error
<27>Jul 28 12:01:00 node-1 multipathd: uevent trigger error
<27>Jul 28 12:01:00 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:00 node-1 ntpdate[30004]: no servers can be used, exiting
<27>Jul 28 12:02:01 node-1 ntpdate[30299]: no servers can be used, exiting
<27>Jul 28 12:02:32 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:32 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:32 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:32 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:32 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:36 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:36 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:36 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:36 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:47 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:47 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:47 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:47 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:47 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:02:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:03:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:03:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:03:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:03:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:03:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:03:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:03:59 node-1 multipathd: uevent trigger error
<27>Jul 28 12:03:59 node-1 multipathd: uevent trigger error
<27>Jul 28 12:03:59 node-1 multipathd: uevent trigger error
<27>Jul 28 12:03:59 node-1 multipathd: uevent trigger error
<27>Jul 28 12:03:59 node-1 multipathd: uevent trigger error
<27>Jul 28 12:04:01 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 12:04:01 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 28 12:04:07 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 12:04:08 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 28 12:04:13 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 28 12:04:19 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 12:04:19 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 28 12:04:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:04:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:04:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:04:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:04:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:04:44 node-1 multipathd: uevent trigger error
<27>Jul 28 12:04:44 node-1 multipathd: uevent trigger error
<27>Jul 28 12:04:44 node-1 multipathd: uevent trigger error
<27>Jul 28 12:04:44 node-1 multipathd: uevent trigger error
<27>Jul 28 12:04:44 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:18 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:18 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:18 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:18 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:18 node-1 multipathd: uevent trigger error
<129>Jul 28 12:05:20 node-1 haproxy[24782]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:05:20 node-1 haproxy[24782]: proxy odl-neutron-endpoint has no server available!
<129>Jul 28 12:05:21 node-1 haproxy[24787]: Server odl-jetty/node-1 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 49ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:05:21 node-1 haproxy[24787]: proxy odl-jetty has no server available!
<27>Jul 28 12:05:44 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:44 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:44 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:44 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:44 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:44 node-1 multipathd: uevent trigger error
<129>Jul 28 12:05:46 node-1 haproxy[27659]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:05:46 node-1 haproxy[27659]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:05:47 node-1 haproxy[27668]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:05:47 node-1 haproxy[27668]: proxy mysqld has no server available!
<27>Jul 28 12:05:49 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:49 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:49 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:49 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:53 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:53 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:53 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:53 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:53 node-1 multipathd: uevent trigger error
<129>Jul 28 12:05:55 node-1 haproxy[30311]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:05:55 node-1 haproxy[30311]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:05:56 node-1 haproxy[30315]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:05:56 node-1 haproxy[30315]: proxy mysqld has no server available!
<129>Jul 28 12:05:56 node-1 haproxy[30315]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:05:56 node-1 haproxy[30315]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:05:56 node-1 haproxy[30315]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:05:56 node-1 haproxy[30315]: proxy object-storage has no server available!
<27>Jul 28 12:05:58 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:58 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:58 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:58 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:58 node-1 multipathd: uevent trigger error
<27>Jul 28 12:05:58 node-1 multipathd: uevent trigger error
<129>Jul 28 12:06:01 node-1 haproxy[31690]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:01 node-1 haproxy[31690]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:01 node-1 haproxy[31690]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:01 node-1 haproxy[31690]: proxy neutron has no server available!
<129>Jul 28 12:06:01 node-1 haproxy[31690]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:01 node-1 haproxy[31690]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:01 node-1 haproxy[31690]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:01 node-1 haproxy[31690]: proxy mysqld has no server available!
<129>Jul 28 12:06:02 node-1 haproxy[31694]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:02 node-1 haproxy[31694]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:02 node-1 haproxy[31694]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:02 node-1 haproxy[31694]: proxy object-storage has no server available!
<27>Jul 28 12:06:04 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:04 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:04 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:04 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:04 node-1 multipathd: uevent trigger error
<129>Jul 28 12:06:06 node-1 haproxy[718]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:06 node-1 haproxy[718]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:06 node-1 haproxy[718]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:06 node-1 haproxy[718]: proxy keystone-1 has no server available!
<129>Jul 28 12:06:07 node-1 haproxy[722]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:07 node-1 haproxy[722]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:07 node-1 haproxy[722]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:07 node-1 haproxy[722]: proxy keystone-2 has no server available!
<129>Jul 28 12:06:07 node-1 haproxy[722]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:07 node-1 haproxy[722]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:07 node-1 haproxy[722]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:07 node-1 haproxy[722]: proxy neutron has no server available!
<129>Jul 28 12:06:07 node-1 haproxy[722]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:07 node-1 haproxy[722]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:08 node-1 haproxy[722]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:08 node-1 haproxy[722]: proxy mysqld has no server available!
<129>Jul 28 12:06:08 node-1 haproxy[722]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:08 node-1 haproxy[722]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:08 node-1 haproxy[722]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:08 node-1 haproxy[722]: proxy object-storage has no server available!
<27>Jul 28 12:06:09 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:09 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:09 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:09 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:09 node-1 multipathd: uevent trigger error
<129>Jul 28 12:06:11 node-1 haproxy[2269]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:12 node-1 haproxy[2273]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:12 node-1 haproxy[2273]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:12 node-1 haproxy[2273]: proxy keystone-1 has no server available!
<129>Jul 28 12:06:12 node-1 haproxy[2273]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:12 node-1 haproxy[2273]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:12 node-1 haproxy[2273]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:12 node-1 haproxy[2273]: proxy keystone-2 has no server available!
<129>Jul 28 12:06:12 node-1 haproxy[2273]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:12 node-1 haproxy[2273]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:12 node-1 haproxy[2273]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:12 node-1 haproxy[2273]: proxy neutron has no server available!
<129>Jul 28 12:06:12 node-1 haproxy[2273]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:12 node-1 haproxy[2273]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:13 node-1 haproxy[2273]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:13 node-1 haproxy[2273]: proxy mysqld has no server available!
<129>Jul 28 12:06:13 node-1 haproxy[2273]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:13 node-1 haproxy[2273]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:13 node-1 haproxy[2273]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:13 node-1 haproxy[2273]: proxy object-storage has no server available!
<129>Jul 28 12:06:13 node-1 haproxy[2273]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:13 node-1 haproxy[2273]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:13 node-1 haproxy[2273]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:13 node-1 haproxy[2273]: proxy aodh has no server available!
<27>Jul 28 12:06:15 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:15 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:15 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:15 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:15 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:15 node-1 multipathd: uevent trigger error
<129>Jul 28 12:06:17 node-1 haproxy[3682]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:17 node-1 haproxy[3682]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:17 node-1 haproxy[3682]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:17 node-1 haproxy[3682]: proxy keystone-1 has no server available!
<129>Jul 28 12:06:17 node-1 haproxy[3682]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:17 node-1 haproxy[3682]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:17 node-1 haproxy[3682]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:17 node-1 haproxy[3682]: proxy keystone-2 has no server available!
<129>Jul 28 12:06:17 node-1 haproxy[3682]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:18 node-1 haproxy[3686]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:18 node-1 haproxy[3686]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:18 node-1 haproxy[3686]: proxy neutron has no server available!
<129>Jul 28 12:06:18 node-1 haproxy[3686]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:18 node-1 haproxy[3686]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:18 node-1 haproxy[3686]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:18 node-1 haproxy[3686]: proxy mysqld has no server available!
<129>Jul 28 12:06:18 node-1 haproxy[3686]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:18 node-1 haproxy[3686]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:18 node-1 haproxy[3686]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:18 node-1 haproxy[3686]: proxy object-storage has no server available!
<129>Jul 28 12:06:18 node-1 haproxy[3686]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:18 node-1 haproxy[3686]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:18 node-1 haproxy[3686]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:18 node-1 haproxy[3686]: proxy aodh has no server available!
<129>Jul 28 12:06:19 node-1 haproxy[3686]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:19 node-1 haproxy[3686]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:19 node-1 haproxy[3686]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:19 node-1 haproxy[3686]: proxy ceilometer has no server available!
<27>Jul 28 12:06:20 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:20 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:20 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:20 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:20 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:20 node-1 multipathd: uevent trigger error
<129>Jul 28 12:06:22 node-1 haproxy[5159]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:22 node-1 haproxy[5159]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:22 node-1 haproxy[5159]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:22 node-1 haproxy[5159]: proxy keystone-1 has no server available!
<129>Jul 28 12:06:23 node-1 haproxy[5165]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:23 node-1 haproxy[5165]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:23 node-1 haproxy[5165]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:23 node-1 haproxy[5165]: proxy keystone-2 has no server available!
<129>Jul 28 12:06:23 node-1 haproxy[5165]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:23 node-1 haproxy[5165]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:23 node-1 haproxy[5165]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:23 node-1 haproxy[5165]: proxy neutron has no server available!
<129>Jul 28 12:06:23 node-1 haproxy[5165]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:23 node-1 haproxy[5165]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:23 node-1 haproxy[5165]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:23 node-1 haproxy[5165]: proxy mysqld has no server available!
<129>Jul 28 12:06:23 node-1 haproxy[5165]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:23 node-1 haproxy[5165]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:24 node-1 haproxy[5165]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:24 node-1 haproxy[5165]: proxy object-storage has no server available!
<129>Jul 28 12:06:24 node-1 haproxy[5165]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:24 node-1 haproxy[5165]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:24 node-1 haproxy[5165]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:24 node-1 haproxy[5165]: proxy aodh has no server available!
<129>Jul 28 12:06:24 node-1 haproxy[5165]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:24 node-1 haproxy[5165]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:24 node-1 haproxy[5165]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:24 node-1 haproxy[5165]: proxy ceilometer has no server available!
<27>Jul 28 12:06:25 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:25 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:25 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:25 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:25 node-1 multipathd: uevent trigger error
<129>Jul 28 12:06:28 node-1 haproxy[6751]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:28 node-1 haproxy[6751]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:28 node-1 haproxy[6751]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:28 node-1 haproxy[6751]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:28 node-1 haproxy[6751]: proxy keystone-1 has no server available!
<129>Jul 28 12:06:28 node-1 haproxy[6751]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:28 node-1 haproxy[6751]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:28 node-1 haproxy[6751]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:28 node-1 haproxy[6751]: proxy keystone-2 has no server available!
<129>Jul 28 12:06:28 node-1 haproxy[6751]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:28 node-1 haproxy[6751]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:28 node-1 haproxy[6751]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:28 node-1 haproxy[6751]: proxy neutron has no server available!
<129>Jul 28 12:06:29 node-1 haproxy[6755]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:29 node-1 haproxy[6755]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:29 node-1 haproxy[6755]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:29 node-1 haproxy[6755]: proxy mysqld has no server available!
<129>Jul 28 12:06:29 node-1 haproxy[6755]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:29 node-1 haproxy[6755]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:29 node-1 haproxy[6755]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:29 node-1 haproxy[6755]: proxy object-storage has no server available!
<129>Jul 28 12:06:29 node-1 haproxy[6755]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:29 node-1 haproxy[6755]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:29 node-1 haproxy[6755]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:29 node-1 haproxy[6755]: proxy aodh has no server available!
<129>Jul 28 12:06:29 node-1 haproxy[6755]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:29 node-1 haproxy[6755]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:29 node-1 haproxy[6755]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:29 node-1 haproxy[6755]: proxy ceilometer has no server available!
<27>Jul 28 12:06:31 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:31 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:31 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:31 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:31 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:31 node-1 multipathd: uevent trigger error
<129>Jul 28 12:06:33 node-1 haproxy[8274]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:34 node-1 haproxy[8278]: proxy keystone-1 has no server available!
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:34 node-1 haproxy[8278]: proxy keystone-2 has no server available!
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:34 node-1 haproxy[8278]: proxy glance-api has no server available!
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:34 node-1 haproxy[8278]: proxy glance-glare has no server available!
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:34 node-1 haproxy[8278]: proxy neutron has no server available!
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:34 node-1 haproxy[8278]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:35 node-1 haproxy[8278]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:35 node-1 haproxy[8278]: proxy glance-registry has no server available!
<129>Jul 28 12:06:35 node-1 haproxy[8278]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:35 node-1 haproxy[8278]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:35 node-1 haproxy[8278]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:35 node-1 haproxy[8278]: proxy mysqld has no server available!
<129>Jul 28 12:06:35 node-1 haproxy[8278]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:35 node-1 haproxy[8278]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:35 node-1 haproxy[8278]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:35 node-1 haproxy[8278]: proxy object-storage has no server available!
<129>Jul 28 12:06:35 node-1 haproxy[8278]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:35 node-1 haproxy[8278]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:35 node-1 haproxy[8278]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:35 node-1 haproxy[8278]: proxy aodh has no server available!
<129>Jul 28 12:06:35 node-1 haproxy[8278]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:35 node-1 haproxy[8278]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:35 node-1 haproxy[8278]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:35 node-1 haproxy[8278]: proxy ceilometer has no server available!
<27>Jul 28 12:06:37 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:37 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:37 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:37 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:37 node-1 multipathd: uevent trigger error
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:40 node-1 haproxy[9791]: proxy keystone-1 has no server available!
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:40 node-1 haproxy[9791]: proxy keystone-2 has no server available!
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:40 node-1 haproxy[9791]: proxy nova-api has no server available!
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:40 node-1 haproxy[9791]: proxy nova-metadata-api has no server available!
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:40 node-1 haproxy[9791]: proxy glance-api has no server available!
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:40 node-1 haproxy[9791]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:41 node-1 haproxy[9795]: proxy glance-glare has no server available!
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:41 node-1 haproxy[9795]: proxy neutron has no server available!
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:41 node-1 haproxy[9795]: proxy glance-registry has no server available!
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:41 node-1 haproxy[9795]: proxy mysqld has no server available!
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:41 node-1 haproxy[9795]: proxy object-storage has no server available!
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:41 node-1 haproxy[9795]: proxy aodh has no server available!
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:41 node-1 haproxy[9795]: proxy ceilometer has no server available!
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:41 node-1 haproxy[9795]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:41 node-1 haproxy[9795]: proxy nova-novncproxy has no server available!
<27>Jul 28 12:06:43 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:43 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:43 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:43 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:43 node-1 multipathd: uevent trigger error
<129>Jul 28 12:06:45 node-1 haproxy[11219]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:45 node-1 haproxy[11219]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:45 node-1 haproxy[11219]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:45 node-1 haproxy[11219]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:45 node-1 haproxy[11219]: proxy keystone-1 has no server available!
<129>Jul 28 12:06:45 node-1 haproxy[11219]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:45 node-1 haproxy[11219]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:45 node-1 haproxy[11219]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:45 node-1 haproxy[11219]: proxy keystone-2 has no server available!
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:46 node-1 haproxy[11223]: proxy nova-api has no server available!
<129>Jul 28 12:06:46 node-1 haproxy[11223]: 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.
<27>Jul 28 12:06:46 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:46 node-1 haproxy[11223]: proxy nova-metadata-api has no server available!
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:46 node-1 haproxy[11223]: proxy cinder-api has no server available!
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:46 node-1 haproxy[11223]: proxy glance-api has no server available!
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:46 node-1 haproxy[11223]: proxy glance-glare has no server available!
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:46 node-1 haproxy[11223]: proxy neutron has no server available!
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:46 node-1 haproxy[11223]: proxy glance-registry has no server available!
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:46 node-1 haproxy[11223]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:46 node-1 haproxy[11223]: proxy mysqld has no server available!
<129>Jul 28 12:06:47 node-1 haproxy[11223]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:47 node-1 haproxy[11223]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:47 node-1 haproxy[11223]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:47 node-1 haproxy[11223]: proxy object-storage has no server available!
<129>Jul 28 12:06:47 node-1 haproxy[11223]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:47 node-1 haproxy[11223]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:47 node-1 haproxy[11223]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:47 node-1 haproxy[11223]: proxy aodh has no server available!
<129>Jul 28 12:06:47 node-1 haproxy[11223]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:47 node-1 haproxy[11223]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:47 node-1 haproxy[11223]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:47 node-1 haproxy[11223]: proxy ceilometer has no server available!
<129>Jul 28 12:06:47 node-1 haproxy[11223]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:47 node-1 haproxy[11223]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:47 node-1 haproxy[11223]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:47 node-1 haproxy[11223]: proxy nova-novncproxy has no server available!
<27>Jul 28 12:06:48 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:48 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:48 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:48 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:48 node-1 multipathd: uevent trigger error
<129>Jul 28 12:06:51 node-1 haproxy[12719]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:51 node-1 haproxy[12719]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:51 node-1 haproxy[12719]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:51 node-1 haproxy[12719]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:51 node-1 haproxy[12719]: proxy keystone-1 has no server available!
<129>Jul 28 12:06:51 node-1 haproxy[12719]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:51 node-1 haproxy[12719]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:51 node-1 haproxy[12719]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:51 node-1 haproxy[12719]: proxy keystone-2 has no server available!
<129>Jul 28 12:06:51 node-1 haproxy[12719]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:51 node-1 haproxy[12719]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:52 node-1 haproxy[12723]: proxy nova-api has no server available!
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:52 node-1 haproxy[12723]: proxy nova-metadata-api has no server available!
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:52 node-1 haproxy[12723]: proxy cinder-api has no server available!
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:52 node-1 haproxy[12723]: proxy glance-api has no server available!
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:52 node-1 haproxy[12723]: proxy glance-glare has no server available!
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:52 node-1 haproxy[12723]: proxy neutron has no server available!
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:52 node-1 haproxy[12723]: proxy glance-registry has no server available!
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:52 node-1 haproxy[12723]: proxy mysqld has no server available!
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:52 node-1 haproxy[12723]: proxy object-storage has no server available!
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:52 node-1 haproxy[12723]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:52 node-1 haproxy[12723]: proxy aodh has no server available!
<129>Jul 28 12:06:53 node-1 haproxy[12723]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:53 node-1 haproxy[12723]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:53 node-1 haproxy[12723]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:53 node-1 haproxy[12723]: proxy ceilometer has no server available!
<129>Jul 28 12:06:53 node-1 haproxy[12723]: Server heat-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:53 node-1 haproxy[12723]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:53 node-1 haproxy[12723]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:53 node-1 haproxy[12723]: proxy heat-api has no server available!
<129>Jul 28 12:06:53 node-1 haproxy[12723]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:53 node-1 haproxy[12723]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:53 node-1 haproxy[12723]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:53 node-1 haproxy[12723]: proxy heat-api-cfn has no server available!
<129>Jul 28 12:06:53 node-1 haproxy[12723]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:53 node-1 haproxy[12723]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 12:06:53 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<129>Jul 28 12:06:53 node-1 haproxy[12723]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:53 node-1 haproxy[12723]: proxy heat-api-cloudwatch has no server available!
<129>Jul 28 12:06:53 node-1 haproxy[12723]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:53 node-1 haproxy[12723]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 12:06:53 node-1 haproxy[12723]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 12:06:53 node-1 haproxy[12723]: proxy nova-novncproxy has no server available!
<27>Jul 28 12:06:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:58 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:58 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:58 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:58 node-1 multipathd: uevent trigger error
<27>Jul 28 12:06:58 node-1 multipathd: uevent trigger error
<27>Jul 28 12:07:08 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 28 12:07:33 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 28 12:07:35 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 28 12:08:27 node-1 multipathd: uevent trigger error
<27>Jul 28 12:08:27 node-1 multipathd: uevent trigger error
<27>Jul 28 12:08:27 node-1 multipathd: uevent trigger error
<27>Jul 28 12:08:27 node-1 multipathd: uevent trigger error
<27>Jul 28 12:08:27 node-1 multipathd: uevent trigger error
<27>Jul 28 12:10:08 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 12:10:48 node-1 multipathd: uevent trigger error
<27>Jul 28 12:10:48 node-1 multipathd: uevent trigger error
<27>Jul 28 12:10:48 node-1 multipathd: uevent trigger error
<27>Jul 28 12:10:48 node-1 multipathd: uevent trigger error
<27>Jul 28 12:10:55 node-1 multipathd: uevent trigger error
<27>Jul 28 12:10:55 node-1 multipathd: uevent trigger error
<27>Jul 28 12:10:55 node-1 multipathd: uevent trigger error
<27>Jul 28 12:10:56 node-1 multipathd: uevent trigger error
<43>Jul 28 12:11:16 node-1 apache2_error [Thu Jul 28 12:11:09.547364 2016] [mpm_event:notice] [pid 25207:tid 140086020011904] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 28 12:11:16 node-1 apache2_error [Thu Jul 28 12:11:09.547490 2016] [core:notice] [pid 25207:tid 140086020011904] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 28 12:11:16 node-1 apache2_error [Thu Jul 28 12:11:12.681939 2016] [mpm_event:notice] [pid 25207:tid 140086020011904] AH00491: caught SIGTERM, shutting down
<43>Jul 28 12:11:16 node-1 apache2_error [Thu Jul 28 12:11:13.771132 2016] [mpm_worker:notice] [pid 25814:tid 140429932685184] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 28 12:11:16 node-1 apache2_error [Thu Jul 28 12:11:13.771181 2016] [core:notice] [pid 25814:tid 140429932685184] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 12:11:18 node-1 multipathd: uevent trigger error
<27>Jul 28 12:11:18 node-1 multipathd: uevent trigger error
<27>Jul 28 12:11:18 node-1 multipathd: uevent trigger error
<27>Jul 28 12:11:18 node-1 multipathd: uevent trigger error
<27>Jul 28 12:11:18 node-1 multipathd: uevent trigger error
<27>Jul 28 12:11:23 node-1 multipathd: uevent trigger error
<27>Jul 28 12:11:23 node-1 multipathd: uevent trigger error
<27>Jul 28 12:11:23 node-1 multipathd: uevent trigger error
<27>Jul 28 12:11:23 node-1 multipathd: uevent trigger error
<27>Jul 28 12:11:23 node-1 multipathd: uevent trigger error
<27>Jul 28 12:11:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:11:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:11:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:11:26 node-1 multipathd: uevent trigger error
<43>Jul 28 12:12:36 node-1 apache2_error [Thu Jul 28 12:12:33.786714 2016] [mpm_worker:notice] [pid 25814:tid 140429932685184] AH00295: caught SIGTERM, shutting down
<43>Jul 28 12:12:36 node-1 apache2_error [Thu Jul 28 12:12:34.536089 2016] [mpm_worker:notice] [pid 7157:tid 140405842061184] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 12:12:36 node-1 apache2_error [Thu Jul 28 12:12:34.536115 2016] [core:notice] [pid 7157:tid 140405842061184] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 12:13:23 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 28 12:13:26 node-1 apache2_error [Thu Jul 28 12:13:18.436344 2016] [mpm_worker:notice] [pid 7157:tid 140405842061184] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 12:13:26 node-1 apache2_error [Thu Jul 28 12:13:18.628912 2016] [mpm_worker:warn] [pid 7157:tid 140405842061184] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 12:13:26 node-1 apache2_error [Thu Jul 28 12:13:18.632894 2016] [mpm_worker:notice] [pid 7157:tid 140405842061184] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 12:13:26 node-1 apache2_error [Thu Jul 28 12:13:18.632922 2016] [core:notice] [pid 7157:tid 140405842061184] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 12:14:03 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:03 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:03 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:03 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:03 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:07 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:07 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:07 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:07 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:07 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:12 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:12 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:12 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:12 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:27 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:27 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:27 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:27 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:28 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:45 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:45 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:45 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:45 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:45 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:14:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:15:04 node-1 multipathd: uevent trigger error
<27>Jul 28 12:15:04 node-1 multipathd: uevent trigger error
<27>Jul 28 12:15:04 node-1 multipathd: uevent trigger error
<27>Jul 28 12:15:04 node-1 multipathd: uevent trigger error
<27>Jul 28 12:16:03 node-1 multipathd: uevent trigger error
<27>Jul 28 12:16:03 node-1 multipathd: uevent trigger error
<27>Jul 28 12:16:03 node-1 multipathd: uevent trigger error
<27>Jul 28 12:16:03 node-1 multipathd: uevent trigger error
<27>Jul 28 12:16:24 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 12:17:16 node-1 multipathd: uevent trigger error
<27>Jul 28 12:17:16 node-1 multipathd: uevent trigger error
<27>Jul 28 12:17:16 node-1 multipathd: uevent trigger error
<27>Jul 28 12:17:16 node-1 multipathd: uevent trigger error
<27>Jul 28 12:17:16 node-1 multipathd: uevent trigger error
<27>Jul 28 12:18:14 node-1 multipathd: uevent trigger error
<27>Jul 28 12:18:14 node-1 multipathd: uevent trigger error
<27>Jul 28 12:18:14 node-1 multipathd: uevent trigger error
<27>Jul 28 12:18:14 node-1 multipathd: uevent trigger error
<27>Jul 28 12:18:14 node-1 multipathd: uevent trigger error
<27>Jul 28 12:18:41 node-1 multipathd: uevent trigger error
<27>Jul 28 12:18:41 node-1 multipathd: uevent trigger error
<27>Jul 28 12:18:41 node-1 multipathd: uevent trigger error
<27>Jul 28 12:18:41 node-1 multipathd: uevent trigger error
<27>Jul 28 12:18:42 node-1 multipathd: uevent trigger error
<27>Jul 28 12:18:48 node-1 multipathd: uevent trigger error
<27>Jul 28 12:18:48 node-1 multipathd: uevent trigger error
<27>Jul 28 12:18:48 node-1 multipathd: uevent trigger error
<27>Jul 28 12:18:48 node-1 multipathd: uevent trigger error
<27>Jul 28 12:18:48 node-1 multipathd: uevent trigger error
<27>Jul 28 12:19:26 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 12:21:16 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:16 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:16 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:16 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:16 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:33 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:33 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:34 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:34 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:34 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:34 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:39 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:39 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:39 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:39 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:39 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:39 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:45 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:45 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:45 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:45 node-1 multipathd: uevent trigger error
<27>Jul 28 12:21:45 node-1 multipathd: uevent trigger error
<27>Jul 28 12:22:06 node-1 multipathd: uevent trigger error
<27>Jul 28 12:22:06 node-1 multipathd: uevent trigger error
<27>Jul 28 12:22:06 node-1 multipathd: uevent trigger error
<27>Jul 28 12:22:06 node-1 multipathd: uevent trigger error
<27>Jul 28 12:22:06 node-1 multipathd: uevent trigger error
<27>Jul 28 12:22:10 node-1 multipathd: uevent trigger error
<27>Jul 28 12:22:10 node-1 multipathd: uevent trigger error
<27>Jul 28 12:22:10 node-1 multipathd: uevent trigger error
<27>Jul 28 12:22:10 node-1 multipathd: uevent trigger error
<27>Jul 28 12:22:10 node-1 multipathd: uevent trigger error
<27>Jul 28 12:22:10 node-1 multipathd: uevent trigger error
<27>Jul 28 12:22:28 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 12:22:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:22:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:22:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:22:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:22:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:23:37 node-1 multipathd: uevent trigger error
<27>Jul 28 12:23:37 node-1 multipathd: uevent trigger error
<27>Jul 28 12:23:38 node-1 multipathd: uevent trigger error
<27>Jul 28 12:23:38 node-1 multipathd: uevent trigger error
<27>Jul 28 12:23:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:23:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:23:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:23:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:24:12 node-1 multipathd: uevent trigger error
<27>Jul 28 12:24:12 node-1 multipathd: uevent trigger error
<27>Jul 28 12:24:12 node-1 multipathd: uevent trigger error
<27>Jul 28 12:24:12 node-1 multipathd: uevent trigger error
<27>Jul 28 12:24:12 node-1 multipathd: uevent trigger error
<27>Jul 28 12:25:29 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 12:26:35 node-1 multipathd: uevent trigger error
<27>Jul 28 12:26:35 node-1 multipathd: uevent trigger error
<27>Jul 28 12:26:35 node-1 multipathd: uevent trigger error
<27>Jul 28 12:26:35 node-1 multipathd: uevent trigger error
<27>Jul 28 12:26:35 node-1 multipathd: uevent trigger error
<27>Jul 28 12:27:10 node-1 multipathd: uevent trigger error
<27>Jul 28 12:27:10 node-1 multipathd: uevent trigger error
<27>Jul 28 12:27:10 node-1 multipathd: uevent trigger error
<27>Jul 28 12:27:10 node-1 multipathd: uevent trigger error
<27>Jul 28 12:27:15 node-1 multipathd: uevent trigger error
<27>Jul 28 12:27:15 node-1 multipathd: uevent trigger error
<27>Jul 28 12:27:15 node-1 multipathd: uevent trigger error
<27>Jul 28 12:27:15 node-1 multipathd: uevent trigger error
<27>Jul 28 12:27:15 node-1 multipathd: uevent trigger error
<27>Jul 28 12:27:56 node-1 multipathd: uevent trigger error
<27>Jul 28 12:27:56 node-1 multipathd: uevent trigger error
<27>Jul 28 12:27:56 node-1 multipathd: uevent trigger error
<27>Jul 28 12:27:56 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:00 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:00 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:00 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:00 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:00 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:04 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:04 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:04 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:04 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:17 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:17 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:17 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:17 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:23 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:23 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:23 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:23 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:31 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 12:28:56 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:56 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:56 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:56 node-1 multipathd: uevent trigger error
<27>Jul 28 12:28:56 node-1 multipathd: uevent trigger error
<27>Jul 28 12:30:02 node-1 multipathd: uevent trigger error
<27>Jul 28 12:30:02 node-1 multipathd: uevent trigger error
<27>Jul 28 12:30:02 node-1 multipathd: uevent trigger error
<27>Jul 28 12:30:02 node-1 multipathd: uevent trigger error
<27>Jul 28 12:30:02 node-1 multipathd: uevent trigger error
<27>Jul 28 12:30:20 node-1 multipathd: uevent trigger error
<27>Jul 28 12:30:20 node-1 multipathd: uevent trigger error
<27>Jul 28 12:30:20 node-1 multipathd: uevent trigger error
<27>Jul 28 12:30:20 node-1 multipathd: uevent trigger error
<11>Jul 28 12:30:34 node-1 liberasurecode[26806]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:34 node-1 liberasurecode[26806]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:34 node-1 liberasurecode[26806]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:34 node-1 liberasurecode[26806]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:34 node-1 liberasurecode[26830]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:34 node-1 liberasurecode[26830]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:34 node-1 liberasurecode[26830]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:34 node-1 liberasurecode[26830]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:37 node-1 liberasurecode[27782]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:37 node-1 liberasurecode[27782]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:37 node-1 liberasurecode[27782]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:37 node-1 liberasurecode[27782]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:42 node-1 liberasurecode[29750]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:42 node-1 liberasurecode[29750]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:42 node-1 liberasurecode[29750]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:42 node-1 liberasurecode[29750]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:42 node-1 liberasurecode[29793]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:42 node-1 liberasurecode[29793]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:42 node-1 liberasurecode[29793]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:42 node-1 liberasurecode[29793]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:42 node-1 liberasurecode[29838]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:42 node-1 liberasurecode[29838]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:42 node-1 liberasurecode[29838]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:42 node-1 liberasurecode[29838]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:43 node-1 liberasurecode[29911]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:43 node-1 liberasurecode[29911]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:43 node-1 liberasurecode[29911]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:43 node-1 liberasurecode[29911]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:43 node-1 liberasurecode[29926]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:43 node-1 liberasurecode[29926]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:43 node-1 liberasurecode[29926]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:43 node-1 liberasurecode[29926]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:43 node-1 liberasurecode[29941]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:43 node-1 liberasurecode[29941]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:43 node-1 liberasurecode[29941]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:43 node-1 liberasurecode[29941]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:43 node-1 liberasurecode[29956]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:43 node-1 liberasurecode[29956]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:43 node-1 liberasurecode[29956]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:43 node-1 liberasurecode[29956]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:51 node-1 liberasurecode[30386]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:51 node-1 liberasurecode[30386]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:51 node-1 liberasurecode[30386]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:30:51 node-1 liberasurecode[30386]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 28 12:31:00 node-1 multipathd: uevent trigger error
<27>Jul 28 12:31:00 node-1 multipathd: uevent trigger error
<27>Jul 28 12:31:00 node-1 multipathd: uevent trigger error
<27>Jul 28 12:31:00 node-1 multipathd: uevent trigger error
<27>Jul 28 12:31:00 node-1 multipathd: uevent trigger error
<27>Jul 28 12:31:32 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 28 12:31:47 node-1 apache2_error [Thu Jul 28 12:31:47.430461 2016] [mpm_worker:notice] [pid 7157:tid 140405842061184] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 12:31:47 node-1 apache2_error [Thu Jul 28 12:31:47.814183 2016] [mpm_worker:warn] [pid 7157:tid 140405842061184] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 12:31:47 node-1 apache2_error [Thu Jul 28 12:31:47.819203 2016] [mpm_worker:notice] [pid 7157:tid 140405842061184] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 12:31:47 node-1 apache2_error [Thu Jul 28 12:31:47.819222 2016] [core:notice] [pid 7157:tid 140405842061184] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 28 12:32:28 node-1 apache2_error [Thu Jul 28 12:32:24.946007 2016] [mpm_worker:notice] [pid 7157:tid 140405842061184] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 12:32:28 node-1 apache2_error [Thu Jul 28 12:32:25.139707 2016] [mpm_worker:warn] [pid 7157:tid 140405842061184] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 12:32:28 node-1 apache2_error [Thu Jul 28 12:32:25.147872 2016] [mpm_worker:notice] [pid 7157:tid 140405842061184] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 12:32:28 node-1 apache2_error [Thu Jul 28 12:32:25.147906 2016] [core:notice] [pid 7157:tid 140405842061184] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 12:32:28 node-1 multipathd: uevent trigger error
<27>Jul 28 12:32:28 node-1 multipathd: uevent trigger error
<27>Jul 28 12:32:28 node-1 multipathd: uevent trigger error
<27>Jul 28 12:32:28 node-1 multipathd: uevent trigger error
<27>Jul 28 12:32:28 node-1 multipathd: uevent trigger error
<27>Jul 28 12:32:36 node-1 multipathd: uevent trigger error
<27>Jul 28 12:32:36 node-1 multipathd: uevent trigger error
<27>Jul 28 12:32:36 node-1 multipathd: uevent trigger error
<27>Jul 28 12:32:36 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:13 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:13 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:13 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:13 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:13 node-1 multipathd: uevent trigger error
<43>Jul 28 12:33:18 node-1 apache2_error [Thu Jul 28 12:33:10.046995 2016] [mpm_worker:notice] [pid 7157:tid 140405842061184] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 12:33:18 node-1 apache2_error [Thu Jul 28 12:33:10.804865 2016] [mpm_worker:warn] [pid 7157:tid 140405842061184] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 12:33:18 node-1 apache2_error [Thu Jul 28 12:33:10.812554 2016] [mpm_worker:notice] [pid 7157:tid 140405842061184] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 12:33:18 node-1 apache2_error [Thu Jul 28 12:33:10.812581 2016] [core:notice] [pid 7157:tid 140405842061184] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 12:33:20 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:20 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:20 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:20 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:20 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:43 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:43 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:43 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:43 node-1 multipathd: uevent trigger error
<27>Jul 28 12:33:43 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:04 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:11 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:11 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:11 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:11 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:19 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 28 12:34:27 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:27 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:27 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:27 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:27 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:32 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:32 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:32 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:32 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:37 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:37 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:37 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:37 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:52 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:52 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:52 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:52 node-1 multipathd: uevent trigger error
<27>Jul 28 12:34:52 node-1 multipathd: uevent trigger error
<11>Jul 28 12:35:01 node-1 liberasurecode[20497]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:35:01 node-1 liberasurecode[20497]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:35:01 node-1 liberasurecode[20497]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 12:35:01 node-1 liberasurecode[20497]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 28 12:35:13 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 12:35:19 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:19 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:19 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:19 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:19 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:33 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:33 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:33 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:33 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:33 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:47 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:47 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:47 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:47 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:47 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:54 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:59 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:59 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:59 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:59 node-1 multipathd: uevent trigger error
<27>Jul 28 12:35:59 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:13 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:13 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:13 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:13 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:13 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:26 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:31 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:31 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:31 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:31 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:36 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:36 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:36 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:36 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:41 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:41 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:41 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:41 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:45 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:45 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:45 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:45 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:45 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:50 node-1 multipathd: uevent trigger error
<27>Jul 28 12:36:50 node-1 multipathd: uevent trigger error
