Jul 25 03:44:10 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8360" x-info="http://www.rsyslog.com"] start
Jul 25 03:44:10 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 25 03:44:10 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 25 03:44:10 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 25 03:44:10 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 25 03:44:10 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 25 03:44:10 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 25 03:44:10 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 25 03:44:10 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=902f5efd-b5c6-45a5-93ae-edd3d25b6ec5 nomdmonddf nomdmonisw
Jul 25 03:44:10 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 25 03:44:10 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 25 03:44:10 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 25 03:44:10 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 25 03:44:10 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 25 03:44:10 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 25 03:44:10 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 25 03:44:10 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 25 03:44:10 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 25 03:44:10 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 25 03:44:10 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 25 03:44:10 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 25 03:44:10 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 25 03:44:10 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 25 03:44:10 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 25 03:44:10 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 25 03:44:10 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 25 03:44:10 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 25 03:44:10 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 25 03:44:10 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 25 03:44:10 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 25 03:44:10 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 25 03:44:10 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 25 03:44:10 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 25 03:44:10 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 25 03:44:10 node-1 kernel: [    0.000000] No AGP bridge found
Jul 25 03:44:10 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 25 03:44:10 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 25 03:44:10 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 25 03:44:10 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 25 03:44:10 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 25 03:44:10 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 25 03:44:10 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 25 03:44:10 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 25 03:44:10 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 25 03:44:10 node-1 kernel: [    0.000000]   2 disabled
Jul 25 03:44:10 node-1 kernel: [    0.000000]   3 disabled
Jul 25 03:44:10 node-1 kernel: [    0.000000]   4 disabled
Jul 25 03:44:10 node-1 kernel: [    0.000000]   5 disabled
Jul 25 03:44:10 node-1 kernel: [    0.000000]   6 disabled
Jul 25 03:44:10 node-1 kernel: [    0.000000]   7 disabled
Jul 25 03:44:10 node-1 kernel: [    0.000000]   8 disabled
Jul 25 03:44:10 node-1 kernel: [    0.000000]   9 disabled
Jul 25 03:44:10 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 25 03:44:10 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 25 03:44:10 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 25 03:44:10 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 25 03:44:10 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 25 03:44:10 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 25 03:44:10 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 25 03:44:10 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 25 03:44:10 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 25 03:44:10 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 25 03:44:10 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 25 03:44:10 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 25 03:44:10 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 25 03:44:10 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 25 03:44:10 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 25 03:44:10 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 25 03:44:10 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 25 03:44:10 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 25 03:44:10 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 25 03:44:10 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 25 03:44:10 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 25 03:44:10 node-1 kernel: [    0.000000] RAMDISK: [mem 0x3581e000-0x36c06fff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 25 03:44:10 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 25 03:44:10 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 25 03:44:10 node-1 kernel: [    0.000000] Zone ranges:
Jul 25 03:44:10 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 25 03:44:10 node-1 kernel: [    0.000000] Early memory node ranges
Jul 25 03:44:10 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 25 03:44:10 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 25 03:44:10 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 25 03:44:10 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 25 03:44:10 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 25 03:44:10 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 25 03:44:10 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 25 03:44:10 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 25 03:44:10 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 25 03:44:10 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 25 03:44:10 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 25 03:44:10 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 25 03:44:10 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 25 03:44:10 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 25 03:44:10 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 25 03:44:10 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 25 03:44:10 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 25 03:44:10 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 25 03:44:10 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 25 03:44:10 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 25 03:44:10 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 25 03:44:10 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 25 03:44:10 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 25 03:44:10 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 25 03:44:10 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 25 03:44:10 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 25 03:44:10 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 25 03:44:10 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=902f5efd-b5c6-45a5-93ae-edd3d25b6ec5 nomdmonddf nomdmonisw
Jul 25 03:44:10 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 25 03:44:10 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 25 03:44:10 node-1 kernel: [    0.000000] Checking aperture...
Jul 25 03:44:10 node-1 kernel: [    0.000000] No AGP bridge found
Jul 25 03:44:10 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 25 03:44:10 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 25 03:44:10 node-1 kernel: [    0.000000] Memory: 32653308K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627188K reserved)
Jul 25 03:44:10 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 25 03:44:10 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 25 03:44:10 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 25 03:44:10 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 25 03:44:10 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 25 03:44:10 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 25 03:44:10 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 25 03:44:10 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 25 03:44:10 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 25 03:44:10 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 25 03:44:10 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 25 03:44:10 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 25 03:44:10 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 25 03:44:10 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 25 03:44:10 node-1 kernel: [    0.004000] tsc: Detected 3492.022 MHz processor
Jul 25 03:44:10 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.04 BogoMIPS (lpj=13968088)
Jul 25 03:44:10 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 25 03:44:10 node-1 kernel: [    0.000047] Security Framework initialized
Jul 25 03:44:10 node-1 kernel: [    0.000065] AppArmor: AppArmor initialized
Jul 25 03:44:10 node-1 kernel: [    0.000066] Yama: becoming mindful.
Jul 25 03:44:10 node-1 kernel: [    0.001456] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 25 03:44:10 node-1 kernel: [    0.006406] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 25 03:44:10 node-1 kernel: [    0.008328] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 25 03:44:10 node-1 kernel: [    0.008356] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 25 03:44:10 node-1 kernel: [    0.008633] Initializing cgroup subsys memory
Jul 25 03:44:10 node-1 kernel: [    0.008640] Initializing cgroup subsys devices
Jul 25 03:44:10 node-1 kernel: [    0.008642] Initializing cgroup subsys freezer
Jul 25 03:44:10 node-1 kernel: [    0.008644] Initializing cgroup subsys blkio
Jul 25 03:44:10 node-1 kernel: [    0.008645] Initializing cgroup subsys perf_event
Jul 25 03:44:10 node-1 kernel: [    0.008648] Initializing cgroup subsys hugetlb
Jul 25 03:44:10 node-1 kernel: [    0.008667] CPU: Physical Processor ID: 0
Jul 25 03:44:10 node-1 kernel: [    0.008668] CPU: Processor Core ID: 0
Jul 25 03:44:10 node-1 kernel: [    0.008672] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 25 03:44:10 node-1 kernel: [    0.008672] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 25 03:44:10 node-1 kernel: [    0.009365] mce: CPU supports 22 MCE banks
Jul 25 03:44:10 node-1 kernel: [    0.009392] CPU0: Thermal monitoring enabled (TM1)
Jul 25 03:44:10 node-1 kernel: [    0.009413] process: using mwait in idle threads
Jul 25 03:44:10 node-1 kernel: [    0.009416] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 25 03:44:10 node-1 kernel: [    0.009416] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 25 03:44:10 node-1 kernel: [    0.009416] tlb_flushall_shift: 6
Jul 25 03:44:10 node-1 kernel: [    0.009506] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 25 03:44:10 node-1 kernel: [    0.010228] ACPI: Core revision 20131115
Jul 25 03:44:10 node-1 kernel: [    0.022886] ACPI: All ACPI Tables successfully acquired
Jul 25 03:44:10 node-1 kernel: [    0.023036] ftrace: allocating 28617 entries in 112 pages
Jul 25 03:44:10 node-1 kernel: [    0.031856] dmar: Host address width 46
Jul 25 03:44:10 node-1 kernel: [    0.031858] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 25 03:44:10 node-1 kernel: [    0.031864] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 25 03:44:10 node-1 kernel: [    0.031866] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 25 03:44:10 node-1 kernel: [    0.031870] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 25 03:44:10 node-1 kernel: [    0.031871] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 25 03:44:10 node-1 kernel: [    0.031873] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 25 03:44:10 node-1 kernel: [    0.031874] dmar: ATSR flags: 0x0
Jul 25 03:44:10 node-1 kernel: [    0.031875] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 25 03:44:10 node-1 kernel: [    0.031876] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 25 03:44:10 node-1 kernel: [    0.031992] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 25 03:44:10 node-1 kernel: [    0.031993] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 25 03:44:10 node-1 kernel: [    0.031994] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 25 03:44:10 node-1 kernel: [    0.031995] HPET id 0 under DRHD base 0xc7ffc000
Jul 25 03:44:10 node-1 kernel: [    0.031996] Your BIOS is broken and requested that x2apic be disabled.
Jul 25 03:44:10 node-1 kernel: [    0.031996] This will slightly decrease performance.
Jul 25 03:44:10 node-1 kernel: [    0.031996] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 25 03:44:10 node-1 kernel: [    0.032429] Enabled IRQ remapping in xapic mode
Jul 25 03:44:10 node-1 kernel: [    0.032430] x2apic not enabled, IRQ remapping is in xapic mode
Jul 25 03:44:10 node-1 kernel: [    0.032434] Switched APIC routing to physical flat.
Jul 25 03:44:10 node-1 kernel: [    0.033048] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 25 03:44:10 node-1 kernel: [    0.072699] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 25 03:44:10 node-1 kernel: [    0.072704] TSC deadline timer enabled
Jul 25 03:44:10 node-1 kernel: [    0.072712] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 25 03:44:10 node-1 kernel: [    0.072718] ... version:                3
Jul 25 03:44:10 node-1 kernel: [    0.072719] ... bit width:              48
Jul 25 03:44:10 node-1 kernel: [    0.072720] ... generic registers:      4
Jul 25 03:44:10 node-1 kernel: [    0.072721] ... value mask:             0000ffffffffffff
Jul 25 03:44:10 node-1 kernel: [    0.072722] ... max period:             0000ffffffffffff
Jul 25 03:44:10 node-1 kernel: [    0.072723] ... fixed-purpose events:   3
Jul 25 03:44:10 node-1 kernel: [    0.072724] ... event mask:             000000070000000f
Jul 25 03:44:10 node-1 kernel: [    0.074150] x86: Booting SMP configuration:
Jul 25 03:44:10 node-1 kernel: [    0.088253] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 25 03:44:10 node-1 kernel: [    0.074152] .... node  #0, CPUs:        #1  #2  #3
Jul 25 03:44:10 node-1 kernel: [    0.116163] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 25 03:44:10 node-1 kernel: [    0.270314] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 25 03:44:10 node-1 kernel: [    0.325935] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 25 03:44:10 node-1 kernel: [    0.383002] x86: Booted up 2 nodes, 16 CPUs
Jul 25 03:44:10 node-1 kernel: [    0.383005] smpboot: Total of 16 processors activated (111756.97 BogoMIPS)
Jul 25 03:44:10 node-1 kernel: [    0.407318] devtmpfs: initialized
Jul 25 03:44:10 node-1 kernel: [    0.410425] EVM: security.selinux
Jul 25 03:44:10 node-1 kernel: [    0.410427] EVM: security.SMACK64
Jul 25 03:44:10 node-1 kernel: [    0.410428] EVM: security.ima
Jul 25 03:44:10 node-1 kernel: [    0.410429] EVM: security.capability
Jul 25 03:44:10 node-1 kernel: [    0.410478] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 25 03:44:10 node-1 kernel: [    0.411164] pinctrl core: initialized pinctrl subsystem
Jul 25 03:44:10 node-1 kernel: [    0.411226] regulator-dummy: no parameters
Jul 25 03:44:10 node-1 kernel: [    0.411257] RTC time:  3:43:34, date: 07/25/16
Jul 25 03:44:10 node-1 kernel: [    0.411291] NET: Registered protocol family 16
Jul 25 03:44:10 node-1 kernel: [    0.411374] cpuidle: using governor ladder
Jul 25 03:44:10 node-1 kernel: [    0.411375] cpuidle: using governor menu
Jul 25 03:44:10 node-1 kernel: [    0.411410] ACPI: bus type PCI registered
Jul 25 03:44:10 node-1 kernel: [    0.411412] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 25 03:44:10 node-1 kernel: [    0.411458] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 25 03:44:10 node-1 kernel: [    0.411461] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 25 03:44:10 node-1 kernel: [    0.425193] PCI: Using configuration type 1 for base access
Jul 25 03:44:10 node-1 kernel: [    0.426187] bio: create slab <bio-0> at 0
Jul 25 03:44:10 node-1 kernel: [    0.426461] ACPI: Added _OSI(Module Device)
Jul 25 03:44:10 node-1 kernel: [    0.426462] ACPI: Added _OSI(Processor Device)
Jul 25 03:44:10 node-1 kernel: [    0.426463] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 25 03:44:10 node-1 kernel: [    0.426465] ACPI: Added _OSI(Processor Aggregator Device)
Jul 25 03:44:10 node-1 kernel: [    0.439098] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 25 03:44:10 node-1 kernel: [    0.449674] ACPI: Interpreter enabled
Jul 25 03:44:10 node-1 kernel: [    0.449680] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 25 03:44:10 node-1 kernel: [    0.449684] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 25 03:44:10 node-1 kernel: [    0.449686] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 25 03:44:10 node-1 kernel: [    0.449693] ACPI: (supports S0 S4 S5)
Jul 25 03:44:10 node-1 kernel: [    0.449694] ACPI: Using IOAPIC for interrupt routing
Jul 25 03:44:10 node-1 kernel: [    0.449738] HEST: Table parsing has been initialized.
Jul 25 03:44:10 node-1 kernel: [    0.449741] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 25 03:44:10 node-1 kernel: [    0.450294] ACPI: No dock devices found.
Jul 25 03:44:10 node-1 kernel: [    0.461946] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 25 03:44:10 node-1 kernel: [    0.461950] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 03:44:10 node-1 kernel: [    0.461954] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 25 03:44:10 node-1 kernel: [    0.461980] PCI host bridge to bus 0000:ff
Jul 25 03:44:10 node-1 kernel: [    0.461982] pci_bus 0000:ff: root bus resource [bus ff]
Jul 25 03:44:10 node-1 kernel: [    0.461990] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462029] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 25 03:44:10 node-1 kernel: [    0.462059] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462094] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462123] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 25 03:44:10 node-1 kernel: [    0.462152] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 25 03:44:10 node-1 kernel: [    0.462183] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462212] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462241] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462270] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462296] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462323] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462351] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462378] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462405] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462432] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462461] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462488] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462515] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 25 03:44:10 node-1 kernel: [    0.462544] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462570] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 25 03:44:10 node-1 kernel: [    0.462596] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462622] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462652] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 25 03:44:10 node-1 kernel: [    0.462688] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462720] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462750] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462781] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462812] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462845] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462879] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462912] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462942] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.462975] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463006] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463037] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463069] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463099] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463127] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463160] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463193] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463230] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463265] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463297] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463327] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463358] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463390] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463420] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463450] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463481] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463512] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463541] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463570] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463599] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463628] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463659] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463690] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463747] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 25 03:44:10 node-1 kernel: [    0.463750] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 03:44:10 node-1 kernel: [    0.463753] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 25 03:44:10 node-1 kernel: [    0.463770] PCI host bridge to bus 0000:7f
Jul 25 03:44:10 node-1 kernel: [    0.463772] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 25 03:44:10 node-1 kernel: [    0.463777] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463804] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 25 03:44:10 node-1 kernel: [    0.463832] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463862] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463887] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 25 03:44:10 node-1 kernel: [    0.463912] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 25 03:44:10 node-1 kernel: [    0.463939] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463966] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.463993] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464016] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464038] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464061] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464085] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464107] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464130] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464157] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464178] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464201] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464224] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 25 03:44:10 node-1 kernel: [    0.464247] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464269] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 25 03:44:10 node-1 kernel: [    0.464291] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464314] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464340] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 25 03:44:10 node-1 kernel: [    0.464373] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464399] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464425] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464451] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464476] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464504] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464531] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464558] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464583] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464610] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464637] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464665] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464693] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464718] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464743] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464771] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464796] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464822] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464851] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464877] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464904] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464929] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464955] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.464982] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.465009] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.465035] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.465065] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.465089] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.465111] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.465137] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.465162] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.465191] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.465216] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.466459] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 25 03:44:10 node-1 kernel: [    0.466463] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 03:44:10 node-1 kernel: [    0.467584] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 25 03:44:10 node-1 kernel: [    0.468097] PCI host bridge to bus 0000:00
Jul 25 03:44:10 node-1 kernel: [    0.468100] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 25 03:44:10 node-1 kernel: [    0.468101] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 25 03:44:10 node-1 kernel: [    0.468103] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 25 03:44:10 node-1 kernel: [    0.468104] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 25 03:44:10 node-1 kernel: [    0.468105] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 25 03:44:10 node-1 kernel: [    0.468107] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 25 03:44:10 node-1 kernel: [    0.468108] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 25 03:44:10 node-1 kernel: [    0.468114] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 25 03:44:10 node-1 kernel: [    0.468195] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 25 03:44:10 node-1 kernel: [    0.468226] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 25 03:44:10 node-1 kernel: [    0.468267] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 25 03:44:10 node-1 kernel: [    0.468286] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 25 03:44:10 node-1 kernel: [    0.468315] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 25 03:44:10 node-1 kernel: [    0.468355] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 25 03:44:10 node-1 kernel: [    0.468374] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 25 03:44:10 node-1 kernel: [    0.468403] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 25 03:44:10 node-1 kernel: [    0.468443] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 25 03:44:10 node-1 kernel: [    0.468459] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.468528] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.468604] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.468679] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 25 03:44:10 node-1 kernel: [    0.468684] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 25 03:44:10 node-1 kernel: [    0.468768] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 25 03:44:10 node-1 kernel: [    0.468915] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 25 03:44:10 node-1 kernel: [    0.468932] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 25 03:44:10 node-1 kernel: [    0.469011] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 25 03:44:10 node-1 kernel: [    0.469065] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 25 03:44:10 node-1 kernel: [    0.469086] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 25 03:44:10 node-1 kernel: [    0.469141] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 25 03:44:10 node-1 kernel: [    0.469185] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 25 03:44:10 node-1 kernel: [    0.469211] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 25 03:44:10 node-1 kernel: [    0.469267] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 25 03:44:10 node-1 kernel: [    0.469310] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 25 03:44:10 node-1 kernel: [    0.469334] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 25 03:44:10 node-1 kernel: [    0.469352] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 25 03:44:10 node-1 kernel: [    0.469430] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 25 03:44:10 node-1 kernel: [    0.469479] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 25 03:44:10 node-1 kernel: [    0.469505] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 25 03:44:10 node-1 kernel: [    0.469751] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 25 03:44:10 node-1 kernel: [    0.469757] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 25 03:44:10 node-1 kernel: [    0.469763] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 25 03:44:10 node-1 kernel: [    0.469769] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 25 03:44:10 node-1 kernel: [    0.469776] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 25 03:44:10 node-1 kernel: [    0.469806] pci 0000:01:00.0: supports D1 D2
Jul 25 03:44:10 node-1 kernel: [    0.479895] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 25 03:44:10 node-1 kernel: [    0.479901] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 25 03:44:10 node-1 kernel: [    0.479906] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 25 03:44:10 node-1 kernel: [    0.480105] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 25 03:44:10 node-1 kernel: [    0.480139] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 25 03:44:10 node-1 kernel: [    0.487893] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 25 03:44:10 node-1 kernel: [    0.487899] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 25 03:44:10 node-1 kernel: [    0.487903] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 03:44:10 node-1 kernel: [    0.487987] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 25 03:44:10 node-1 kernel: [    0.488060] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 25 03:44:10 node-1 kernel: [    0.488154] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 25 03:44:10 node-1 kernel: [    0.488235] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 25 03:44:10 node-1 kernel: [    0.488253] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 03:44:10 node-1 kernel: [    0.488255] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 03:44:10 node-1 kernel: [    0.488316] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 25 03:44:10 node-1 kernel: [    0.488439] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 25 03:44:10 node-1 kernel: [    0.488491] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 25 03:44:10 node-1 kernel: [    0.488494] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 03:44:10 node-1 kernel: [    0.488496] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 03:44:10 node-1 kernel: [    0.488545] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 25 03:44:10 node-1 kernel: [    0.488664] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 25 03:44:10 node-1 kernel: [    0.488705] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 25 03:44:10 node-1 kernel: [    0.488824] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 25 03:44:10 node-1 kernel: [    0.488862] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 25 03:44:10 node-1 kernel: [    0.488981] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 25 03:44:10 node-1 kernel: [    0.489019] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 25 03:44:10 node-1 kernel: [    0.489138] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 25 03:44:10 node-1 kernel: [    0.489180] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 25 03:44:10 node-1 kernel: [    0.489183] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 03:44:10 node-1 kernel: [    0.489185] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 03:44:10 node-1 kernel: [    0.489244] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 25 03:44:10 node-1 kernel: [    0.489324] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 25 03:44:10 node-1 kernel: [    0.489375] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 25 03:44:10 node-1 kernel: [    0.489416] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 25 03:44:10 node-1 kernel: [    0.489498] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 25 03:44:10 node-1 kernel: [    0.489605] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 25 03:44:10 node-1 kernel: [    0.489608] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 03:44:10 node-1 kernel: [    0.489610] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 25 03:44:10 node-1 kernel: [    0.489666] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 25 03:44:10 node-1 kernel: [    0.489720] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 25 03:44:10 node-1 kernel: [    0.489769] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 25 03:44:10 node-1 kernel: [    0.489981] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 25 03:44:10 node-1 kernel: [    0.489984] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 25 03:44:10 node-1 kernel: [    0.490047] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 25 03:44:10 node-1 kernel: [    0.490100] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 25 03:44:10 node-1 kernel: [    0.490149] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 25 03:44:10 node-1 kernel: [    0.490383] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 25 03:44:10 node-1 kernel: [    0.490387] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 25 03:44:10 node-1 kernel: [    0.490445] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 25 03:44:10 node-1 kernel: [    0.490507] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 25 03:44:10 node-1 kernel: [    0.490562] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 25 03:44:10 node-1 kernel: [    0.490783] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 25 03:44:10 node-1 kernel: [    0.490786] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 25 03:44:10 node-1 kernel: [    0.490959] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 25 03:44:10 node-1 kernel: [    0.490997] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 25 03:44:10 node-1 kernel: [    0.491073] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 25 03:44:10 node-1 kernel: [    0.491092] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 25 03:44:10 node-1 kernel: [    0.491105] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 25 03:44:10 node-1 kernel: [    0.491118] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 25 03:44:10 node-1 kernel: [    0.491168] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 25 03:44:10 node-1 kernel: [    0.495899] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 25 03:44:10 node-1 kernel: [    0.495908] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 25 03:44:10 node-1 kernel: [    0.495961] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 25 03:44:10 node-1 kernel: [    0.496469] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 25 03:44:10 node-1 kernel: [    0.496472] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 03:44:10 node-1 kernel: [    0.496591] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 25 03:44:10 node-1 kernel: [    0.496698] PCI host bridge to bus 0000:80
Jul 25 03:44:10 node-1 kernel: [    0.496700] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 25 03:44:10 node-1 kernel: [    0.496702] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 25 03:44:10 node-1 kernel: [    0.496703] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 25 03:44:10 node-1 kernel: [    0.496711] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.496774] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.496841] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 25 03:44:10 node-1 kernel: [    0.496902] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 25 03:44:10 node-1 kernel: [    0.496907] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 25 03:44:10 node-1 kernel: [    0.496978] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 25 03:44:10 node-1 kernel: [    0.497274] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 25 03:44:10 node-1 kernel: [    0.497305] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 25 03:44:10 node-1 kernel: [    0.497335] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 25 03:44:10 node-1 kernel: [    0.497364] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 25 03:44:10 node-1 kernel: [    0.497393] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 03:44:10 node-1 kernel: [    0.497423] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 03:44:10 node-1 kernel: [    0.497452] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 03:44:10 node-1 kernel: [    0.497481] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 03:44:10 node-1 kernel: [    0.497565] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 25 03:44:10 node-1 kernel: [    0.497569] ACPI: \_SB_.UNC1: notify handler is installed
Jul 25 03:44:10 node-1 kernel: [    0.497571] ACPI: \_SB_.UNC0: notify handler is installed
Jul 25 03:44:10 node-1 kernel: [    0.497586] ACPI: \_SB_.PCI0: notify handler is installed
Jul 25 03:44:10 node-1 kernel: [    0.497639] ACPI: \_SB_.PCI1: notify handler is installed
Jul 25 03:44:10 node-1 kernel: [    0.497718] Found 4 acpi root devices
Jul 25 03:44:10 node-1 kernel: [    0.497823] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 25 03:44:10 node-1 kernel: [    0.497825] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 25 03:44:10 node-1 kernel: [    0.497827] vgaarb: loaded
Jul 25 03:44:10 node-1 kernel: [    0.497828] vgaarb: bridge control possible 0000:0c:00.0
Jul 25 03:44:10 node-1 kernel: [    0.497954] SCSI subsystem initialized
Jul 25 03:44:10 node-1 kernel: [    0.498019] libata version 3.00 loaded.
Jul 25 03:44:10 node-1 kernel: [    0.498035] ACPI: bus type USB registered
Jul 25 03:44:10 node-1 kernel: [    0.498045] usbcore: registered new interface driver usbfs
Jul 25 03:44:10 node-1 kernel: [    0.498050] usbcore: registered new interface driver hub
Jul 25 03:44:10 node-1 kernel: [    0.498072] usbcore: registered new device driver usb
Jul 25 03:44:10 node-1 kernel: [    0.498236] PCI: Using ACPI for IRQ routing
Jul 25 03:44:10 node-1 kernel: [    0.501852] PCI: pci_cache_line_size set to 64 bytes
Jul 25 03:44:10 node-1 kernel: [    0.502054] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 25 03:44:10 node-1 kernel: [    0.502055] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 25 03:44:10 node-1 kernel: [    0.502056] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 25 03:44:10 node-1 kernel: [    0.502122] NetLabel: Initializing
Jul 25 03:44:10 node-1 kernel: [    0.502123] NetLabel:  domain hash size = 128
Jul 25 03:44:10 node-1 kernel: [    0.502124] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 25 03:44:10 node-1 kernel: [    0.502134] NetLabel:  unlabeled traffic allowed by default
Jul 25 03:44:10 node-1 kernel: [    0.502189] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 25 03:44:10 node-1 kernel: [    0.502193] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 25 03:44:10 node-1 kernel: [    0.504263] Switched to clocksource hpet
Jul 25 03:44:10 node-1 kernel: [    0.508778] AppArmor: AppArmor Filesystem Enabled
Jul 25 03:44:10 node-1 kernel: [    0.508816] pnp: PnP ACPI init
Jul 25 03:44:10 node-1 kernel: [    0.508828] ACPI: bus type PNP registered
Jul 25 03:44:10 node-1 kernel: [    0.509009] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 25 03:44:10 node-1 kernel: [    0.509021] pnp 00:01: [dma 4]
Jul 25 03:44:10 node-1 kernel: [    0.509039] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 25 03:44:10 node-1 kernel: [    0.509073] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 25 03:44:10 node-1 kernel: [    0.509098] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 25 03:44:10 node-1 kernel: [    0.509118] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 25 03:44:10 node-1 kernel: [    0.509166] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 25 03:44:10 node-1 kernel: [    0.509278] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 25 03:44:10 node-1 kernel: [    0.509280] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 25 03:44:10 node-1 kernel: [    0.509282] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 25 03:44:10 node-1 kernel: [    0.509283] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 25 03:44:10 node-1 kernel: [    0.509285] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 25 03:44:10 node-1 kernel: [    0.509286] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 25 03:44:10 node-1 kernel: [    0.509290] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 25 03:44:10 node-1 kernel: [    0.509291] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 25 03:44:10 node-1 kernel: [    0.509293] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 25 03:44:10 node-1 kernel: [    0.509295] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 25 03:44:10 node-1 kernel: [    0.509296] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 25 03:44:10 node-1 kernel: [    0.509298] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 25 03:44:10 node-1 kernel: [    0.509299] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 25 03:44:10 node-1 kernel: [    0.509301] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 25 03:44:10 node-1 kernel: [    0.509402] pnp 00:07: [dma 0 disabled]
Jul 25 03:44:10 node-1 kernel: [    0.509435] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 25 03:44:10 node-1 kernel: [    0.509516] pnp 00:08: [dma 0 disabled]
Jul 25 03:44:10 node-1 kernel: [    0.509551] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 25 03:44:10 node-1 kernel: [    0.509609] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 25 03:44:10 node-1 kernel: [    0.510054] pnp: PnP ACPI: found 10 devices
Jul 25 03:44:10 node-1 kernel: [    0.510056] ACPI: bus type PNP unregistered
Jul 25 03:44:10 node-1 kernel: [    0.516079] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 25 03:44:10 node-1 kernel: [    0.516083] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 25 03:44:10 node-1 kernel: [    0.516086] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 25 03:44:10 node-1 kernel: [    0.516091] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 25 03:44:10 node-1 kernel: [    0.516093] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 03:44:10 node-1 kernel: [    0.516108] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 25 03:44:10 node-1 kernel: [    0.516137] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 25 03:44:10 node-1 kernel: [    0.516151] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 25 03:44:10 node-1 kernel: [    0.516180] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 25 03:44:10 node-1 kernel: [    0.516195] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 25 03:44:10 node-1 kernel: [    0.516224] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 25 03:44:10 node-1 kernel: [    0.516265] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 25 03:44:10 node-1 kernel: [    0.516293] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 25 03:44:10 node-1 kernel: [    0.516295] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 03:44:10 node-1 kernel: [    0.516310] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 03:44:10 node-1 kernel: [    0.516343] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 25 03:44:10 node-1 kernel: [    0.516345] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 03:44:10 node-1 kernel: [    0.516359] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 03:44:10 node-1 kernel: [    0.516387] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 25 03:44:10 node-1 kernel: [    0.516389] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 03:44:10 node-1 kernel: [    0.516392] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 03:44:10 node-1 kernel: [    0.516397] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 25 03:44:10 node-1 kernel: [    0.516398] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 25 03:44:10 node-1 kernel: [    0.516401] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 03:44:10 node-1 kernel: [    0.516405] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 25 03:44:10 node-1 kernel: [    0.516411] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 25 03:44:10 node-1 kernel: [    0.516420] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 25 03:44:10 node-1 kernel: [    0.516424] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 25 03:44:10 node-1 kernel: [    0.516431] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 25 03:44:10 node-1 kernel: [    0.516432] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 25 03:44:10 node-1 kernel: [    0.516433] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 25 03:44:10 node-1 kernel: [    0.516434] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 25 03:44:10 node-1 kernel: [    0.516435] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 25 03:44:10 node-1 kernel: [    0.516436] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 25 03:44:10 node-1 kernel: [    0.516437] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 25 03:44:10 node-1 kernel: [    0.516438] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 25 03:44:10 node-1 kernel: [    0.516439] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 25 03:44:10 node-1 kernel: [    0.516440] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 25 03:44:10 node-1 kernel: [    0.516441] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 25 03:44:10 node-1 kernel: [    0.516442] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 25 03:44:10 node-1 kernel: [    0.516443] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 25 03:44:10 node-1 kernel: [    0.516444] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 25 03:44:10 node-1 kernel: [    0.516445] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 25 03:44:10 node-1 kernel: [    0.516446] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 25 03:44:10 node-1 kernel: [    0.516447] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 25 03:44:10 node-1 kernel: [    0.516447] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 25 03:44:10 node-1 kernel: [    0.516449] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 25 03:44:10 node-1 kernel: [    0.516450] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 25 03:44:10 node-1 kernel: [    0.516451] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 25 03:44:10 node-1 kernel: [    0.516453] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 25 03:44:10 node-1 kernel: [    0.516455] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 25 03:44:10 node-1 kernel: [    0.516456] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 25 03:44:10 node-1 kernel: [    0.516497] NET: Registered protocol family 2
Jul 25 03:44:10 node-1 kernel: [    0.516794] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 25 03:44:10 node-1 kernel: [    0.517176] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 25 03:44:10 node-1 kernel: [    0.517344] TCP: Hash tables configured (established 262144 bind 65536)
Jul 25 03:44:10 node-1 kernel: [    0.517389] TCP: reno registered
Jul 25 03:44:10 node-1 kernel: [    0.517420] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 25 03:44:10 node-1 kernel: [    0.517530] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 25 03:44:10 node-1 kernel: [    0.517702] NET: Registered protocol family 1
Jul 25 03:44:10 node-1 kernel: [    0.556349] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 25 03:44:10 node-1 kernel: [    0.556364] PCI: CLS 64 bytes, default 64
Jul 25 03:44:10 node-1 kernel: [    0.556446] Trying to unpack rootfs image as initramfs...
Jul 25 03:44:10 node-1 kernel: [    0.778721] Freeing initrd memory: 20388K (ffff88003581e000 - ffff880036c07000)
Jul 25 03:44:10 node-1 kernel: [    0.778771] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 25 03:44:10 node-1 kernel: [    0.778774] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 25 03:44:10 node-1 kernel: [    0.779180] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 03:44:10 node-1 kernel: [    0.779194] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 03:44:10 node-1 kernel: [    0.779207] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 03:44:10 node-1 kernel: [    0.779219] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 03:44:10 node-1 kernel: [    0.779233] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 03:44:10 node-1 kernel: [    0.779239] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 03:44:10 node-1 kernel: [    0.779245] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 03:44:10 node-1 kernel: [    0.779251] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 03:44:10 node-1 kernel: [    0.779260] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 03:44:10 node-1 kernel: [    0.779281] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 03:44:10 node-1 kernel: [    0.779291] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 03:44:10 node-1 kernel: [    0.779297] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 03:44:10 node-1 kernel: [    0.779304] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 03:44:10 node-1 kernel: [    0.779310] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 03:44:10 node-1 kernel: [    0.779316] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 03:44:10 node-1 kernel: [    0.779322] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 03:44:10 node-1 kernel: [    0.779379] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 25 03:44:10 node-1 kernel: [    0.779381] Scanning for low memory corruption every 60 seconds
Jul 25 03:44:10 node-1 kernel: [    0.779679] Initialise system trusted keyring
Jul 25 03:44:10 node-1 kernel: [    0.779726] audit: initializing netlink socket (disabled)
Jul 25 03:44:10 node-1 kernel: [    0.779737] type=2000 audit(1469418213.732:1): initialized
Jul 25 03:44:10 node-1 kernel: [    0.797628] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 25 03:44:10 node-1 kernel: [    0.799116] zbud: loaded
Jul 25 03:44:10 node-1 kernel: [    0.799238] VFS: Disk quotas dquot_6.5.2
Jul 25 03:44:10 node-1 kernel: [    0.799279] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 25 03:44:10 node-1 kernel: [    0.799634] fuse init (API version 7.22)
Jul 25 03:44:10 node-1 kernel: [    0.799689] msgmni has been set to 32768
Jul 25 03:44:10 node-1 kernel: [    0.799734] Key type big_key registered
Jul 25 03:44:10 node-1 kernel: [    0.800225] Key type asymmetric registered
Jul 25 03:44:10 node-1 kernel: [    0.800227] Asymmetric key parser 'x509' registered
Jul 25 03:44:10 node-1 kernel: [    0.800249] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 25 03:44:10 node-1 kernel: [    0.800315] io scheduler noop registered
Jul 25 03:44:10 node-1 kernel: [    0.800317] io scheduler deadline registered (default)
Jul 25 03:44:10 node-1 kernel: [    0.800336] io scheduler cfq registered
Jul 25 03:44:10 node-1 kernel: [    0.800743] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    0.800914] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    0.801032] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    0.801146] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    0.801264] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    0.801368] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    0.801730] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 25 03:44:10 node-1 kernel: [    0.801755] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 25 03:44:10 node-1 kernel: [    0.801771] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 25 03:44:10 node-1 kernel: [    0.801783] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801785] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801788] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 25 03:44:10 node-1 kernel: [    0.801793] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801795] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801796] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801797] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801799] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801800] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801802] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801803] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801805] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801806] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801807] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801809] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801819] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 25 03:44:10 node-1 kernel: [    0.801833] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801835] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 25 03:44:10 node-1 kernel: [    0.801846] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801849] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 25 03:44:10 node-1 kernel: [    0.801860] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801861] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 25 03:44:10 node-1 kernel: [    0.801864] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 25 03:44:10 node-1 kernel: [    0.801893] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 25 03:44:10 node-1 kernel: [    0.801899] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 25 03:44:10 node-1 kernel: [    0.801903] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 25 03:44:10 node-1 kernel: [    0.801911] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 25 03:44:10 node-1 kernel: [    0.801949] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 25 03:44:10 node-1 kernel: [    0.801950] vesafb: scrolling: redraw
Jul 25 03:44:10 node-1 kernel: [    0.801951] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 25 03:44:10 node-1 kernel: [    0.822979] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 25 03:44:10 node-1 kernel: [    0.831507] Console: switching to colour frame buffer device 80x30
Jul 25 03:44:10 node-1 kernel: [    0.840206] fb0: VESA VGA frame buffer device
Jul 25 03:44:10 node-1 kernel: [    0.840399] intel_idle: MWAIT substates: 0x2120
Jul 25 03:44:10 node-1 kernel: [    0.840400] intel_idle: v0.4 model 0x3F
Jul 25 03:44:10 node-1 kernel: [    0.840401] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 25 03:44:10 node-1 kernel: [    0.840643] ipmi message handler version 39.2
Jul 25 03:44:10 node-1 kernel: [    0.840913] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 25 03:44:10 node-1 kernel: [    0.841346] ACPI: AC Adapter [P111] (on-line)
Jul 25 03:44:10 node-1 kernel: [    0.846560] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 25 03:44:10 node-1 kernel: [    0.857546] ACPI: Power Button [PWRB]
Jul 25 03:44:10 node-1 kernel: [    0.863326] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 25 03:44:10 node-1 kernel: [    0.875014] ACPI: Power Button [PWRF]
Jul 25 03:44:10 node-1 kernel: [    0.901757] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 25 03:44:10 node-1 kernel: [    0.913397] pstore: Registered erst as persistent store backend
Jul 25 03:44:10 node-1 kernel: [    0.919586] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 25 03:44:10 node-1 kernel: [    0.931510] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 25 03:44:10 node-1 kernel: [    0.958239] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 25 03:44:10 node-1 kernel: [    0.991526] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 25 03:44:10 node-1 kernel: [    1.005604] Linux agpgart interface v0.103
Jul 25 03:44:10 node-1 kernel: [    1.013268] brd: module loaded
Jul 25 03:44:10 node-1 kernel: [    1.020309] loop: module loaded
Jul 25 03:44:10 node-1 kernel: [    1.027011] libphy: Fixed MDIO Bus: probed
Jul 25 03:44:10 node-1 kernel: [    1.033459] tun: Universal TUN/TAP device driver, 1.6
Jul 25 03:44:10 node-1 kernel: [    1.039916] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 25 03:44:10 node-1 kernel: [    1.046424] PPP generic driver version 2.4.2
Jul 25 03:44:10 node-1 kernel: [    1.052824] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 25 03:44:10 node-1 kernel: [    1.059249] ehci-pci: EHCI PCI platform driver
Jul 25 03:44:10 node-1 kernel: [    1.065751] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 25 03:44:10 node-1 kernel: [    1.072143] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 25 03:44:10 node-1 kernel: [    1.084643] ehci-pci 0000:00:1a.0: debug port 2
Jul 25 03:44:10 node-1 kernel: [    1.094810] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 25 03:44:10 node-1 kernel: [    1.094827] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 25 03:44:10 node-1 kernel: [    1.111738] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 25 03:44:10 node-1 kernel: [    1.117810] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 25 03:44:10 node-1 kernel: [    1.123963] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 25 03:44:10 node-1 kernel: [    1.135863] usb usb1: Product: EHCI Host Controller
Jul 25 03:44:10 node-1 kernel: [    1.141883] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 25 03:44:10 node-1 kernel: [    1.147929] usb usb1: SerialNumber: 0000:00:1a.0
Jul 25 03:44:10 node-1 kernel: [    1.153889] hub 1-0:1.0: USB hub found
Jul 25 03:44:10 node-1 kernel: [    1.159636] hub 1-0:1.0: 2 ports detected
Jul 25 03:44:10 node-1 kernel: [    1.165412] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 25 03:44:10 node-1 kernel: [    1.170992] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 25 03:44:10 node-1 kernel: [    1.181853] ehci-pci 0000:00:1d.0: debug port 2
Jul 25 03:44:10 node-1 kernel: [    1.191132] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 25 03:44:10 node-1 kernel: [    1.191135] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 25 03:44:10 node-1 kernel: [    1.207656] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 25 03:44:10 node-1 kernel: [    1.212870] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 25 03:44:10 node-1 kernel: [    1.218191] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 25 03:44:10 node-1 kernel: [    1.228801] usb usb2: Product: EHCI Host Controller
Jul 25 03:44:10 node-1 kernel: [    1.234287] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 25 03:44:10 node-1 kernel: [    1.239864] usb usb2: SerialNumber: 0000:00:1d.0
Jul 25 03:44:10 node-1 kernel: [    1.245438] hub 2-0:1.0: USB hub found
Jul 25 03:44:10 node-1 kernel: [    1.250864] hub 2-0:1.0: 2 ports detected
Jul 25 03:44:10 node-1 kernel: [    1.256245] ehci-platform: EHCI generic platform driver
Jul 25 03:44:10 node-1 kernel: [    1.261548] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 25 03:44:10 node-1 kernel: [    1.266929] ohci-pci: OHCI PCI platform driver
Jul 25 03:44:10 node-1 kernel: [    1.272316] ohci-platform: OHCI generic platform driver
Jul 25 03:44:10 node-1 kernel: [    1.277555] uhci_hcd: USB Universal Host Controller Interface driver
Jul 25 03:44:10 node-1 kernel: [    1.282975] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 25 03:44:10 node-1 kernel: [    1.475436] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 25 03:44:10 node-1 kernel: [    1.775206] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 25 03:44:10 node-1 kernel: [    1.791474] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 25 03:44:10 node-1 kernel: [    1.797069] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 25 03:44:10 node-1 kernel: [    1.802742] hub 1-1:1.0: USB hub found
Jul 25 03:44:10 node-1 kernel: [    1.808335] hub 1-1:1.0: 6 ports detected
Jul 25 03:44:10 node-1 kernel: [    1.923075] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 25 03:44:10 node-1 kernel: [    2.322036] i8042: No controller found
Jul 25 03:44:10 node-1 kernel: [    2.327621] mousedev: PS/2 mouse device common for all mice
Jul 25 03:44:10 node-1 kernel: [    2.333380] rtc_cmos 00:02: RTC can wake from S4
Jul 25 03:44:10 node-1 kernel: [    2.335459] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 25 03:44:10 node-1 kernel: [    2.335460] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 25 03:44:10 node-1 kernel: [    2.336095] hub 2-1:1.0: USB hub found
Jul 25 03:44:10 node-1 kernel: [    2.336336] hub 2-1:1.0: 8 ports detected
Jul 25 03:44:10 node-1 kernel: [    2.361774] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 25 03:44:10 node-1 kernel: [    2.367550] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 25 03:44:10 node-1 kernel: [    2.378998] device-mapper: uevent: version 1.0.3
Jul 25 03:44:10 node-1 kernel: [    2.384742] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 25 03:44:10 node-1 kernel: [    2.396182] ledtrig-cpu: registered to indicate activity on CPUs
Jul 25 03:44:10 node-1 kernel: [    2.402181] TCP: cubic registered
Jul 25 03:44:10 node-1 kernel: [    2.408071] NET: Registered protocol family 10
Jul 25 03:44:10 node-1 kernel: [    2.414122] NET: Registered protocol family 17
Jul 25 03:44:10 node-1 kernel: [    2.419883] Key type dns_resolver registered
Jul 25 03:44:10 node-1 kernel: [    2.425936] Loading compiled-in X.509 certificates
Jul 25 03:44:10 node-1 kernel: [    2.432140] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 25 03:44:10 node-1 kernel: [    2.443762] registered taskstats version 1
Jul 25 03:44:10 node-1 kernel: [    2.451845] Key type trusted registered
Jul 25 03:44:10 node-1 kernel: [    2.459442] Key type encrypted registered
Jul 25 03:44:10 node-1 kernel: [    2.464941] AppArmor: AppArmor sha1 policy hashing enabled
Jul 25 03:44:10 node-1 kernel: [    2.470461] IMA: No TPM chip found, activating TPM-bypass!
Jul 25 03:44:10 node-1 kernel: [    2.476578] regulator-dummy: disabling
Jul 25 03:44:10 node-1 kernel: [    2.482054]   Magic number: 8:883:715
Jul 25 03:44:10 node-1 kernel: [    2.487561] pci 0000:7f:10.5: hash matches
Jul 25 03:44:10 node-1 kernel: [    2.493118] acpi LNXCPU:1f: hash matches
Jul 25 03:44:10 node-1 kernel: [    2.498608] rtc_cmos 00:02: setting system clock to 2016-07-25 03:43:36 UTC (1469418216)
Jul 25 03:44:10 node-1 kernel: [    2.510991] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 25 03:44:10 node-1 kernel: [    2.516568] EDD information not available.
Jul 25 03:44:10 node-1 kernel: [    2.522093] PM: Hibernation image not present or could not be loaded.
Jul 25 03:44:10 node-1 kernel: [    2.522953] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 25 03:44:10 node-1 kernel: [    2.534244] Write protecting the kernel read-only data: 12288k
Jul 25 03:44:10 node-1 kernel: [    2.540559] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 25 03:44:10 node-1 kernel: [    2.553300] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 25 03:44:10 node-1 kernel: [    2.584905] device-mapper: multipath: version 1.6.0 loaded
Jul 25 03:44:10 node-1 kernel: [    2.592622] systemd-udevd[218]: starting version 204
Jul 25 03:44:10 node-1 kernel: [    2.610474] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 25 03:44:10 node-1 kernel: [    2.618526] md: linear personality registered for level -1
Jul 25 03:44:10 node-1 kernel: [    2.633669] md: multipath personality registered for level -4
Jul 25 03:44:10 node-1 kernel: [    2.642041] md: raid0 personality registered for level 0
Jul 25 03:44:10 node-1 kernel: [    2.650898] md: raid1 personality registered for level 1
Jul 25 03:44:10 node-1 kernel: [    2.660976] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 25 03:44:10 node-1 kernel: [    2.667216] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 25 03:44:10 node-1 kernel: [    2.673473] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 25 03:44:10 node-1 kernel: [    2.675343] megasas: FW now in Ready state
Jul 25 03:44:10 node-1 kernel: [    2.675771] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.675885] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.675986] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.676107] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.676195] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.676336] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.676494] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.676605] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.676765] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.676880] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.676998] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.677140] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.677263] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.677405] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.677557] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.677744] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.678744] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 25 03:44:10 node-1 kernel: [    2.706441] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 25 03:44:10 node-1 kernel: [    2.719716] 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 25 03:44:10 node-1 kernel: [    2.726438] raid6: sse2x1   11345 MB/s
Jul 25 03:44:10 node-1 kernel: [    2.740322] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 03:44:10 node-1 kernel: [    2.747328] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.747331] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.747335] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.747339] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.747375] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 03:44:10 node-1 kernel: [    2.770968] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 25 03:44:10 node-1 kernel: [    2.784350] 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 25 03:44:10 node-1 kernel: [    2.794588] raid6: sse2x2   12808 MB/s
Jul 25 03:44:10 node-1 kernel: [    2.804595] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 03:44:10 node-1 kernel: [    2.862273] raid6: sse2x4    9987 MB/s
Jul 25 03:44:10 node-1 kernel: [    2.934212] raid6: avx2x1   14944 MB/s
Jul 25 03:44:10 node-1 kernel: [    3.006142] raid6: avx2x2   18872 MB/s
Jul 25 03:44:10 node-1 kernel: [    3.078075] raid6: avx2x4   21381 MB/s
Jul 25 03:44:10 node-1 kernel: [    3.084273] raid6: using algorithm avx2x4 (21381 MB/s)
Jul 25 03:44:10 node-1 kernel: [    3.090384] raid6: using avx2x2 recovery algorithm
Jul 25 03:44:10 node-1 kernel: [    3.096353] Switched to clocksource tsc
Jul 25 03:44:10 node-1 kernel: [    3.096353] megasas:IOC Init cmd success
Jul 25 03:44:10 node-1 kernel: [    3.096513] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    3.096682] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    3.096747] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    3.096883] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    3.097336] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 03:44:10 node-1 kernel: [    3.111864] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 25 03:44:10 node-1 kernel: [    3.111898] 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 25 03:44:10 node-1 kernel: [    3.111899] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 03:44:10 node-1 kernel: [    3.112125] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    3.112225] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    3.112315] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    3.112489] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    3.112668] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 03:44:10 node-1 kernel: [    3.115476] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 25 03:44:10 node-1 kernel: [    3.115491] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 25 03:44:10 node-1 kernel: [    3.115493] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 25 03:44:10 node-1 kernel: [    3.115494] usb 2-1.4: Manufacturer: Avocent
Jul 25 03:44:10 node-1 kernel: [    3.115498] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 25 03:44:10 node-1 kernel: [    3.122492] megasas: INIT adapter done
Jul 25 03:44:10 node-1 kernel: [    3.127213] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 25 03:44:10 node-1 kernel: [    3.127228] 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 25 03:44:10 node-1 kernel: [    3.127252] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 03:44:10 node-1 kernel: [    3.127605] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    3.127749] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    3.127894] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    3.128079] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 25 03:44:10 node-1 kernel: [    3.128300] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 03:44:10 node-1 kernel: [    3.194170] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 25 03:44:10 node-1 kernel: [    3.195501] scsi0 : LSI SAS based MegaRAID driver
Jul 25 03:44:10 node-1 kernel: [    3.203465] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 25 03:44:10 node-1 kernel: [    3.271149] hidraw: raw HID events driver (C) Jiri Kosina
Jul 25 03:44:10 node-1 kernel: [    3.273165] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 25 03:44:10 node-1 kernel: [    3.277353] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 25 03:44:10 node-1 kernel: [    3.277579] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 25 03:44:10 node-1 kernel: [    3.277671] sd 0:2:0:0: [sda] Write Protect is off
Jul 25 03:44:10 node-1 kernel: [    3.277672] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 25 03:44:10 node-1 kernel: [    3.277760] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 25 03:44:10 node-1 kernel: [    3.302133]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 25 03:44:10 node-1 kernel: [    3.303680] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 25 03:44:10 node-1 kernel: [    3.341721] xor: automatically using best checksumming function:
Jul 25 03:44:10 node-1 kernel: [    3.350957] usbcore: registered new interface driver usbhid
Jul 25 03:44:10 node-1 kernel: [    3.357458] usbhid: USB HID core driver
Jul 25 03:44:10 node-1 kernel: [    3.364589] 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 25 03:44:10 node-1 kernel: [    3.377497] 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 25 03:44:10 node-1 kernel: [    3.385829]    avx       : 39450.000 MB/sec
Jul 25 03:44:10 node-1 kernel: [    3.397790] 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 25 03:44:10 node-1 kernel: [    3.411379] async_tx: api initialized (async)
Jul 25 03:44:10 node-1 kernel: [    3.411617] 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 25 03:44:10 node-1 kernel: [    3.412084] 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 25 03:44:10 node-1 kernel: [    3.412750] 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 25 03:44:10 node-1 kernel: [    3.464111] md: raid6 personality registered for level 6
Jul 25 03:44:10 node-1 kernel: [    3.471296] md: raid5 personality registered for level 5
Jul 25 03:44:10 node-1 kernel: [    3.478346] md: raid4 personality registered for level 4
Jul 25 03:44:10 node-1 kernel: [    3.488380] md: raid10 personality registered for level 10
Jul 25 03:44:10 node-1 kernel: [    3.522502] random: lvm urandom read with 31 bits of entropy available
Jul 25 03:44:10 node-1 kernel: [    3.551294] multipathd (369): /proc/369/oom_adj is deprecated, please use /proc/369/oom_score_adj instead.
Jul 25 03:44:10 node-1 kernel: [    3.645176] bio: create slab <bio-1> at 1
Jul 25 03:44:10 node-1 kernel: [    4.403572] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 25 03:44:10 node-1 kernel: [    5.088117] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 25 03:44:10 node-1 kernel: [    5.131235] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 25 03:44:10 node-1 kernel: [    5.143897] random: nonblocking pool is initialized
Jul 25 03:44:10 node-1 kernel: [    5.241906] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 25 03:44:10 node-1 kernel: [    5.277829] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 25 03:44:10 node-1 kernel: [    5.330216] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 25 03:44:10 node-1 kernel: [    5.517306] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 25 03:44:10 node-1 kernel: [    5.549530] XFS (dm-0): Mounting Filesystem
Jul 25 03:44:10 node-1 kernel: [    5.811450] XFS (dm-0): Ending clean mount
Jul 25 03:44:10 node-1 kernel: [    5.884622] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 25 03:44:10 node-1 kernel: [    5.917495] XFS (dm-1): Mounting Filesystem
Jul 25 03:44:10 node-1 kernel: [    6.055465] XFS (dm-1): Ending clean mount
Jul 25 03:44:10 node-1 kernel: [    7.867172] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 25 03:44:10 node-1 kernel: [    7.880650] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 25 03:44:10 node-1 kernel: [    8.016622] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 25 03:44:10 node-1 kernel: [    8.016627] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 25 03:44:10 node-1 kernel: [    8.016631] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 25 03:44:10 node-1 kernel: [    8.016635] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 25 03:44:10 node-1 kernel: [    8.053724] systemd-udevd[772]: starting version 204
Jul 25 03:44:10 node-1 kernel: [    8.258802] power_meter ACPI000D:00: Found ACPI power meter.
Jul 25 03:44:10 node-1 kernel: [    8.258813] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 25 03:44:10 node-1 kernel: [    8.265633] wmi: Mapper loaded
Jul 25 03:44:10 node-1 kernel: [    8.269360] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 25 03:44:10 node-1 kernel: [    8.269365] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 25 03:44:10 node-1 kernel: [    8.269368] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 25 03:44:10 node-1 kernel: [    8.269369] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 25 03:44:10 node-1 kernel: [    8.269417] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 25 03:44:10 node-1 kernel: [    8.284597] IPMI System Interface driver.
Jul 25 03:44:10 node-1 kernel: [    8.284622] ipmi_si: probing via ACPI
Jul 25 03:44:10 node-1 kernel: [    8.284639] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 25 03:44:10 node-1 kernel: [    8.284640] ipmi_si: Adding ACPI-specified kcs state machine
Jul 25 03:44:10 node-1 kernel: [    8.284648] ipmi_si: probing via SMBIOS
Jul 25 03:44:10 node-1 kernel: [    8.284649] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 25 03:44:10 node-1 kernel: [    8.284649] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 25 03:44:10 node-1 kernel: [    8.284651] ipmi_si: probing via SPMI
Jul 25 03:44:10 node-1 kernel: [    8.284651] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 25 03:44:10 node-1 kernel: [    8.284652] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 25 03:44:10 node-1 kernel: [    8.284653] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 25 03:44:10 node-1 kernel: [    8.300735] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 25 03:44:10 node-1 kernel: [    8.382259] systemd-udevd[792]: renamed network interface eth2 to enp8s0
Jul 25 03:44:10 node-1 kernel: [    8.405959] systemd-udevd[800]: renamed network interface eth0 to enp6s0
Jul 25 03:44:10 node-1 kernel: [    8.427091] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 25 03:44:10 node-1 kernel: [    8.427098] ipmi_si 00:09: IPMI kcs interface initialized
Jul 25 03:44:10 node-1 kernel: [    8.434527] systemd-udevd[789]: renamed network interface eth1 to enp7s0
Jul 25 03:44:10 node-1 kernel: [    8.445946] systemd-udevd[790]: renamed network interface eth3 to enp9s0
Jul 25 03:44:10 node-1 kernel: [    8.775557] type=1400 audit(1469418222.779:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1049 comm="apparmor_parser"
Jul 25 03:44:10 node-1 kernel: [    8.775715] type=1400 audit(1469418222.779:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1049 comm="apparmor_parser"
Jul 25 03:44:10 node-1 kernel: [    8.775851] type=1400 audit(1469418222.779:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1049 comm="apparmor_parser"
Jul 25 03:44:10 node-1 kernel: [    8.785521] type=1400 audit(1469418222.791:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1047 comm="apparmor_parser"
Jul 25 03:44:10 node-1 kernel: [    8.785673] type=1400 audit(1469418222.791:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1047 comm="apparmor_parser"
Jul 25 03:44:10 node-1 kernel: [    8.785817] type=1400 audit(1469418222.791:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1047 comm="apparmor_parser"
Jul 25 03:44:10 node-1 kernel: [    8.785892] type=1400 audit(1469418222.791:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1052 comm="apparmor_parser"
Jul 25 03:44:10 node-1 kernel: [    8.786053] type=1400 audit(1469418222.791:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1050 comm="apparmor_parser"
Jul 25 03:44:10 node-1 kernel: [    8.786058] type=1400 audit(1469418222.791:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1052 comm="apparmor_parser"
Jul 25 03:44:10 node-1 kernel: [    8.786220] type=1400 audit(1469418222.791:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1052 comm="apparmor_parser"
Jul 25 03:44:10 node-1 kernel: [    9.329178] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 25 03:44:10 node-1 kernel: [    9.341398] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 25 03:44:10 node-1 kernel: [    9.491659] enic 0000:06:00.0 enp6s0: Link UP
Jul 25 03:44:10 node-1 kernel: [    9.492083] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 25 03:44:10 node-1 kernel: [    9.492089] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 25 03:44:10 node-1 kernel: [   19.049344] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 25 03:44:10 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 25 03:44:11 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 25 03:44:12 node-1 kernel: [   38.150811] init: failsafe main process (8387) killed by TERM signal
Jul 25 03:44:12 node-1 dbus[8427]: [system] AppArmor D-Bus mediation is enabled
Jul 25 03:44:12 node-1 kernel: [   38.345502] audit_printk_skb: 30 callbacks suppressed
Jul 25 03:44:12 node-1 kernel: [   38.345504] type=1400 audit(1469418252.245:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8507 comm="apparmor_parser"
Jul 25 03:44:12 node-1 kernel: [   38.345752] type=1400 audit(1469418252.245:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8505 comm="apparmor_parser"
Jul 25 03:44:12 node-1 kernel: [   38.345758] type=1400 audit(1469418252.245:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8505 comm="apparmor_parser"
Jul 25 03:44:12 node-1 kernel: [   38.345762] type=1400 audit(1469418252.245:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8505 comm="apparmor_parser"
Jul 25 03:44:12 node-1 kernel: [   38.346012] type=1400 audit(1469418252.245:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8505 comm="apparmor_parser"
Jul 25 03:44:12 node-1 kernel: [   38.346015] type=1400 audit(1469418252.245:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8505 comm="apparmor_parser"
Jul 25 03:44:12 node-1 kernel: [   38.346142] type=1400 audit(1469418252.245:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8505 comm="apparmor_parser"
Jul 25 03:44:12 node-1 kernel: [   38.445700] type=1400 audit(1469418252.345:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8509 comm="apparmor_parser"
Jul 25 03:44:12 node-1 cron[8545]: (CRON) INFO (pidfile fd = 3)
Jul 25 03:44:12 node-1 anacron[8582]: Anacron 2.3 started on 2016-07-25
Jul 25 03:44:12 node-1 cron[8585]: (CRON) STARTUP (fork ok)
Jul 25 03:44:12 node-1 anacron[8582]: Will run job `cron.daily' in 5 min.
Jul 25 03:44:12 node-1 anacron[8582]: Will run job `cron.weekly' in 10 min.
Jul 25 03:44:12 node-1 anacron[8582]: Will run job `cron.monthly' in 15 min.
Jul 25 03:44:12 node-1 anacron[8582]: Jobs will be executed sequentially
Jul 25 03:44:12 node-1 multipathd: path checkers start up
Jul 25 03:44:12 node-1 cron[8585]: (CRON) INFO (Running @reboot jobs)
Jul 25 03:44:13 node-1 postfix/master[8725]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 25 03:44:16 node-1 puppet-agent[8909]: Reopening log files
Jul 25 03:44:16 node-1 puppet-agent[8909]: Could not request certificate: Connection refused - connect(2)
Jul 25 03:44:31 node-1 puppet-user[9117]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 25 03:44:31 node-1 puppet-user[9117]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Jul 25 03:44:32 node-1 puppet-user[9117]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 25 03:44:32 node-1 puppet-user[9117]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 25 03:44:32 node-1 puppet-user[9117]: Finished catalog run in 0.88 seconds
Jul 25 03:44:33 node-1 multipathd: uevent trigger error
Jul 25 03:44:33 node-1 puppet-user[9537]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 25 03:44:33 node-1 puppet-user[9537]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Jul 25 03:44:33 node-1 puppet-user[9537]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 25 03:44:33 node-1 puppet-user[9537]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 25 03:44:33 node-1 puppet-user[9537]: (/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 25 03:44:33 node-1 puppet-user[9537]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 25 03:44:33 node-1 puppet-user[9537]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 25 03:44:33 node-1 puppet-user[9537]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 25 03:44:33 node-1 puppet-user[9537]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 25 03:44:33 node-1 puppet-user[9537]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 25 03:44:33 node-1 puppet-user[9537]: Finished catalog run in 0.05 seconds
Jul 25 03:44:35 node-1 puppet-user[9994]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 25 03:44:35 node-1 puppet-user[9994]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 25 03:44:35 node-1 puppet-user[9994]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 25 03:44:35 node-1 puppet-user[9994]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 25 03:44:35 node-1 puppet-user[9994]: Finished catalog run in 0.05 seconds
Jul 25 03:44:36 node-1 puppet-user[10452]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 25 03:44:36 node-1 puppet-user[10452]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 25 03:44:36 node-1 puppet-user[10452]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 25 03:44:36 node-1 puppet-user[10452]: Finished catalog run in 0.03 seconds
Jul 25 03:44:38 node-1 puppet-user[10894]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 25 03:44:38 node-1 puppet-user[10894]: Compiled catalog for node-1.domain.tld in environment production in 0.18 seconds
Jul 25 03:44:38 node-1 puppet-user[10894]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 25 03:44:38 node-1 puppet-user[10894]: (/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 25 03:44:38 node-1 puppet-user[10894]: Finished catalog run in 0.40 seconds
Jul 25 03:44:40 node-1 puppet-user[11368]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 25 03:44:40 node-1 puppet-user[11368]: Compiled catalog for node-1.domain.tld in environment production in 0.21 seconds
Jul 25 03:44:40 node-1 puppet-user[11368]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 25 03:44:40 node-1 puppet-user[11368]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 25 03:44:40 node-1 puppet-user[11368]: (/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 25 03:44:40 node-1 puppet-user[11368]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 25 03:44:40 node-1 puppet-user[11368]: Finished catalog run in 0.22 seconds
Jul 25 03:44:42 node-1 puppet-user[11841]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 25 03:44:42 node-1 puppet-user[11841]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Jul 25 03:44:42 node-1 puppet-user[11841]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 25 03:44:42 node-1 kernel: [   68.387158] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 25 03:44:42 node-1 kernel: [   68.387209] 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 25 03:44:42 node-1 puppet-user[11841]: (/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 25 03:44:42 node-1 puppet-user[11841]: Finished catalog run in 0.05 seconds
Jul 25 03:44:44 node-1 puppet-user[12488]: (Scope(Class[main])) MODULAR: sync_time
Jul 25 03:44:44 node-1 puppet-user[12488]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 25 03:44:44 node-1 ntpdate[12899]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 25 03:44:50 node-1 ntpdate[12899]: adjust time server 10.20.0.2 offset 0.058997 sec
Jul 25 03:44:50 node-1 puppet-user[12488]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 25 03:44:50 node-1 puppet-user[12488]: Finished catalog run in 6.17 seconds
Jul 25 03:44:54 node-1 kernel: [   80.448943] init: plymouth-upstart-bridge main process ended, respawning
Jul 25 03:44:54 node-1 puppet-agent[8909]: Could not run: SIGTERM
Jul 25 03:44:54 node-1 kernel: [   80.703780] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 25 03:44:54 node-1 ec2: 
Jul 25 03:44:54 node-1 ec2: #############################################################
Jul 25 03:44:54 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 25 03:44:54 node-1 ec2: 1024 eb:1a:c2:92:8b:b5:1b:13:f5:8b:cd:77:7d:f3:c2:4c  root@node-1.domain.tld (DSA)
Jul 25 03:44:54 node-1 ec2: 256 fc:fc:76:60:64:28:b9:cc:2c:c2:9e:f2:b3:53:91:f7  root@node-1.domain.tld (ECDSA)
Jul 25 03:44:54 node-1 ec2: 256 8d:73:3c:20:3c:96:10:7e:13:17:fd:14:45:0b:fe:8a  root@node-1.domain.tld (ED25519)
Jul 25 03:44:54 node-1 ec2: 2048 03:67:47:61:6f:81:18:4a:fd:32:61:7e:23:b8:4e:09  root@node-1.domain.tld (RSA)
Jul 25 03:44:54 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 25 03:44:54 node-1 ec2: #############################################################
Jul 25 03:44:56 node-1 puppet-user[13262]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 25 03:44:56 node-1 puppet-user[13262]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Jul 25 03:44:56 node-1 puppet-user[13262]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 25 03:44:56 node-1 puppet-user[13262]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Jul 25 03:44:56 node-1 puppet-user[13262]: Finished catalog run in 0.07 seconds
Jul 25 03:44:57 node-1 puppet-user[13718]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 25 03:44:59 node-1 puppet-user[13718]: Compiled catalog for node-1.domain.tld in environment production in 1.33 seconds
Jul 25 03:44:59 node-1 puppet-user[13718]: (/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 25 03:44:59 node-1 puppet-user[13718]: (/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 25 03:44:59 node-1 puppet-user[13718]: (/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 25 03:44:59 node-1 puppet-user[13718]: (/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 25 03:44:59 node-1 puppet-user[13718]: (/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 25 03:44:59 node-1 puppet-user[13718]: (/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 25 03:44:59 node-1 puppet-user[13718]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 25 03:44:59 node-1 puppet-user[13718]: (/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 25 03:44:59 node-1 puppet-user[13718]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 25 03:44:59 node-1 puppet-user[13718]: (/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 25 03:44:59 node-1 puppet-user[13718]: (/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 25 03:44:59 node-1 puppet-user[13718]: (/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 25 03:44:59 node-1 puppet-user[13718]: (/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 25 03:44:59 node-1 puppet-user[13718]: (/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 25 03:44:59 node-1 puppet-user[13718]: (/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 25 03:44:59 node-1 puppet-user[13718]: (/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 25 03:45:01 node-1 CRON[14270]: (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 25 03:45:15 node-1 puppet-user[13718]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 25 03:45:15 node-1 puppet-user[13718]: Finished catalog run in 16.64 seconds
Jul 25 03:45:18 node-1 puppet-user[14747]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 25 03:45:18 node-1 puppet-user[14747]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Jul 25 03:45:22 node-1 puppet-user[14747]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 25 03:45:23 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 03:45:23 node-1 nailgun-agent: I, [2016-07-25T03:45:23.764047 #14273]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 25 03:45:36 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 03:45:37 node-1 nailgun-agent: I, [2016-07-25T03:45:36.994108 #14273]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 25 03:45:53 node-1 puppet-user[14747]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 25 03:45:53 node-1 puppet-user[14747]: Finished catalog run in 35.23 seconds
Jul 25 03:45:55 node-1 puppet-user[17527]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 25 03:45:56 node-1 puppet-user[17527]: Compiled catalog for node-1.domain.tld in environment production in 0.65 seconds
Jul 25 03:45:56 node-1 puppet-user[17527]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 25 03:45:56 node-1 puppet-user[17527]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 25 03:45:56 node-1 puppet-user[17527]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 25 03:45:56 node-1 puppet-user[17527]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 25 03:45:56 node-1 puppet-user[17527]: Finished catalog run in 0.10 seconds
Jul 25 03:45:58 node-1 puppet-user[17989]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 25 03:45:59 node-1 puppet-user[17989]: Compiled catalog for node-1.domain.tld in environment production in 0.97 seconds
Jul 25 03:45:59 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 25 03:45:59 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 25 03:45:59 node-1 crontab[18421]: (root) LIST (root)
Jul 25 03:45:59 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 25 03:45:59 node-1 crontab[18422]: (root) REPLACE (root)
Jul 25 03:46:01 node-1 CRON[18499]: (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 25 03:46:01 node-1 puppet-user[17989]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/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 25 03:46:03 node-1 puppet-user[17989]: (/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 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/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 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/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 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/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 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/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 25 03:46:03 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 25 03:46:03 node-1 puppet-user[17989]: (/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 25 03:46:03 node-1 puppet-user[17989]: (/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 25 03:46:03 node-1 puppet-user[17989]: (/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 25 03:46:04 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 25 03:46:04 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 25 03:46:04 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 25 03:46:04 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 25 03:46:04 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 25 03:46:04 node-1 puppet-user[17989]: (/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 25 03:46:04 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 25 03:46:04 node-1 puppet-user[17989]: (/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 25 03:46:04 node-1 puppet-user[17989]: (/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 25 03:46:04 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 25 03:46:04 node-1 puppet-user[17989]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 25 03:46:04 node-1 puppet-user[17989]: (/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 25 03:46:04 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8360" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 03:46:04 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 25 03:46:06 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:06 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:06 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:06 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:25 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:25 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:25 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:25 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:27 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:27 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:27 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:27 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:27 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:30 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:30 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:30 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:30 node-1 multipathd: uevent trigger error
<27>Jul 25 03:46:30 node-1 multipathd: uevent trigger error
<27>Jul 25 03:47:30 node-1 ntpdate[30036]: no servers can be used, exiting
<27>Jul 25 03:47:31 node-1 ntpdate[30398]: no servers can be used, exiting
<27>Jul 25 03:48:02 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:02 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:02 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:02 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:06 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:06 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:06 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:06 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:18 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:18 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:18 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:18 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:18 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:21 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:21 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:21 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:21 node-1 multipathd: uevent trigger error
<27>Jul 25 03:48:21 node-1 multipathd: uevent trigger error
<27>Jul 25 03:49:22 node-1 multipathd: uevent trigger error
<27>Jul 25 03:49:22 node-1 multipathd: uevent trigger error
<27>Jul 25 03:49:22 node-1 multipathd: uevent trigger error
<27>Jul 25 03:49:22 node-1 multipathd: uevent trigger error
<27>Jul 25 03:49:22 node-1 multipathd: uevent trigger error
<27>Jul 25 03:49:30 node-1 multipathd: uevent trigger error
<27>Jul 25 03:49:30 node-1 multipathd: uevent trigger error
<27>Jul 25 03:49:30 node-1 multipathd: uevent trigger error
<27>Jul 25 03:49:30 node-1 multipathd: uevent trigger error
<27>Jul 25 03:49:30 node-1 multipathd: uevent trigger error
<27>Jul 25 03:49:33 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 03:49:33 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 25 03:49:39 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 03:49:39 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 25 03:49:45 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 25 03:49:50 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 03:49:50 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 25 03:49:57 node-1 multipathd: uevent trigger error
<27>Jul 25 03:49:57 node-1 multipathd: uevent trigger error
<27>Jul 25 03:49:57 node-1 multipathd: uevent trigger error
<27>Jul 25 03:49:57 node-1 multipathd: uevent trigger error
<27>Jul 25 03:49:57 node-1 multipathd: uevent trigger error
<27>Jul 25 03:49:57 node-1 multipathd: uevent trigger error
<27>Jul 25 03:50:10 node-1 multipathd: uevent trigger error
<27>Jul 25 03:50:10 node-1 multipathd: uevent trigger error
<27>Jul 25 03:50:10 node-1 multipathd: uevent trigger error
<27>Jul 25 03:50:10 node-1 multipathd: uevent trigger error
<27>Jul 25 03:50:10 node-1 multipathd: uevent trigger error
<27>Jul 25 03:50:10 node-1 multipathd: uevent trigger error
<27>Jul 25 03:50:44 node-1 multipathd: uevent trigger error
<27>Jul 25 03:50:44 node-1 multipathd: uevent trigger error
<27>Jul 25 03:50:44 node-1 multipathd: uevent trigger error
<27>Jul 25 03:50:44 node-1 multipathd: uevent trigger error
<27>Jul 25 03:50:44 node-1 multipathd: uevent trigger error
<129>Jul 25 03:50:46 node-1 haproxy[24404]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 110ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 03:50:46 node-1 haproxy[24404]: proxy odl-neutron-endpoint has no server available!
<129>Jul 25 03:50:47 node-1 haproxy[24409]: Server odl-jetty/node-1 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 03:50:47 node-1 haproxy[24409]: proxy odl-jetty has no server available!
<27>Jul 25 03:51:10 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:10 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:10 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:10 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:10 node-1 multipathd: uevent trigger error
<129>Jul 25 03:51:12 node-1 haproxy[27173]: 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 25 03:51:12 node-1 haproxy[27173]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:13 node-1 haproxy[27180]: 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 25 03:51:13 node-1 haproxy[27180]: proxy mysqld has no server available!
<27>Jul 25 03:51:15 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:15 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:15 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:15 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:15 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:15 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:19 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:19 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:19 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:19 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:19 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:19 node-1 multipathd: uevent trigger error
<129>Jul 25 03:51:21 node-1 haproxy[29827]: 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 25 03:51:21 node-1 haproxy[29827]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:22 node-1 haproxy[29836]: 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 25 03:51:22 node-1 haproxy[29836]: proxy mysqld has no server available!
<129>Jul 25 03:51:22 node-1 haproxy[29836]: 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 25 03:51:22 node-1 haproxy[29836]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:22 node-1 haproxy[29836]: 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 25 03:51:22 node-1 haproxy[29836]: proxy object-storage has no server available!
<27>Jul 25 03:51:24 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:24 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:24 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:24 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:24 node-1 multipathd: uevent trigger error
<129>Jul 25 03:51:26 node-1 haproxy[31410]: 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 25 03:51:27 node-1 haproxy[31415]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:27 node-1 haproxy[31415]: 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 25 03:51:27 node-1 haproxy[31415]: proxy neutron has no server available!
<129>Jul 25 03:51:27 node-1 haproxy[31415]: 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 25 03:51:27 node-1 haproxy[31415]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:27 node-1 haproxy[31415]: 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 25 03:51:27 node-1 haproxy[31415]: proxy mysqld has no server available!
<129>Jul 25 03:51:27 node-1 haproxy[31415]: 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 25 03:51:28 node-1 haproxy[31415]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:28 node-1 haproxy[31415]: 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 25 03:51:28 node-1 haproxy[31415]: proxy object-storage has no server available!
<27>Jul 25 03:51:30 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:30 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:30 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:30 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:30 node-1 multipathd: uevent trigger error
<129>Jul 25 03:51:32 node-1 haproxy[386]: 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 25 03:51:32 node-1 haproxy[386]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:32 node-1 haproxy[386]: 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 25 03:51:32 node-1 haproxy[386]: proxy keystone-1 has no server available!
<129>Jul 25 03:51:33 node-1 haproxy[390]: 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 25 03:51:33 node-1 haproxy[390]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:33 node-1 haproxy[390]: 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 25 03:51:33 node-1 haproxy[390]: proxy keystone-2 has no server available!
<129>Jul 25 03:51:33 node-1 haproxy[390]: 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 25 03:51:33 node-1 haproxy[390]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:33 node-1 haproxy[390]: 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 25 03:51:33 node-1 haproxy[390]: proxy neutron has no server available!
<129>Jul 25 03:51:33 node-1 haproxy[390]: 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 25 03:51:33 node-1 haproxy[390]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:33 node-1 haproxy[390]: 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 25 03:51:33 node-1 haproxy[390]: proxy mysqld has no server available!
<129>Jul 25 03:51:34 node-1 haproxy[390]: 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 25 03:51:34 node-1 haproxy[390]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:34 node-1 haproxy[390]: 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 25 03:51:34 node-1 haproxy[390]: proxy object-storage has no server available!
<27>Jul 25 03:51:35 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:35 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:35 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:35 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:35 node-1 multipathd: uevent trigger error
<129>Jul 25 03:51:38 node-1 haproxy[1824]: 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 25 03:51:38 node-1 haproxy[1824]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:38 node-1 haproxy[1824]: 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 25 03:51:38 node-1 haproxy[1824]: proxy keystone-1 has no server available!
<129>Jul 25 03:51:38 node-1 haproxy[1824]: 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 25 03:51:38 node-1 haproxy[1824]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:38 node-1 haproxy[1824]: 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 25 03:51:38 node-1 haproxy[1824]: proxy keystone-2 has no server available!
<129>Jul 25 03:51:38 node-1 haproxy[1824]: 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 25 03:51:38 node-1 haproxy[1824]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:38 node-1 haproxy[1824]: 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 25 03:51:38 node-1 haproxy[1824]: proxy neutron has no server available!
<129>Jul 25 03:51:38 node-1 haproxy[1824]: 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 25 03:51:39 node-1 haproxy[1828]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:39 node-1 haproxy[1828]: 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 25 03:51:39 node-1 haproxy[1828]: proxy mysqld has no server available!
<129>Jul 25 03:51:39 node-1 haproxy[1828]: 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 25 03:51:39 node-1 haproxy[1828]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:39 node-1 haproxy[1828]: 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 25 03:51:39 node-1 haproxy[1828]: proxy object-storage has no server available!
<129>Jul 25 03:51:39 node-1 haproxy[1828]: 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 25 03:51:39 node-1 haproxy[1828]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:39 node-1 haproxy[1828]: 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 25 03:51:39 node-1 haproxy[1828]: proxy aodh has no server available!
<27>Jul 25 03:51:41 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:41 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:41 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:41 node-1 multipathd: uevent trigger error
<129>Jul 25 03:51:43 node-1 haproxy[3212]: 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 25 03:51:43 node-1 haproxy[3212]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:43 node-1 haproxy[3212]: 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 25 03:51:43 node-1 haproxy[3212]: proxy keystone-1 has no server available!
<129>Jul 25 03:51:43 node-1 haproxy[3212]: 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 25 03:51:43 node-1 haproxy[3212]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:43 node-1 haproxy[3212]: 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 25 03:51:43 node-1 haproxy[3212]: proxy keystone-2 has no server available!
<129>Jul 25 03:51:43 node-1 haproxy[3212]: 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 25 03:51:44 node-1 haproxy[3216]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:44 node-1 haproxy[3216]: 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 25 03:51:44 node-1 haproxy[3216]: proxy neutron has no server available!
<129>Jul 25 03:51:44 node-1 haproxy[3216]: 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 25 03:51:44 node-1 haproxy[3216]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:44 node-1 haproxy[3216]: 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 25 03:51:44 node-1 haproxy[3216]: proxy mysqld has no server available!
<129>Jul 25 03:51:44 node-1 haproxy[3216]: 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 25 03:51:44 node-1 haproxy[3216]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:44 node-1 haproxy[3216]: 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 25 03:51:44 node-1 haproxy[3216]: proxy object-storage has no server available!
<129>Jul 25 03:51:44 node-1 haproxy[3216]: 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 25 03:51:44 node-1 haproxy[3216]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:44 node-1 haproxy[3216]: 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 25 03:51:44 node-1 haproxy[3216]: proxy aodh has no server available!
<129>Jul 25 03:51:44 node-1 haproxy[3216]: 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 25 03:51:45 node-1 haproxy[3216]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:45 node-1 haproxy[3216]: 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 25 03:51:45 node-1 haproxy[3216]: proxy ceilometer has no server available!
<27>Jul 25 03:51:46 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:46 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:46 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:46 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:46 node-1 multipathd: uevent trigger error
<129>Jul 25 03:51:48 node-1 haproxy[4596]: 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 25 03:51:48 node-1 haproxy[4596]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:48 node-1 haproxy[4596]: 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 25 03:51:48 node-1 haproxy[4596]: proxy keystone-1 has no server available!
<129>Jul 25 03:51:49 node-1 haproxy[4600]: 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 25 03:51:49 node-1 haproxy[4600]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:49 node-1 haproxy[4600]: 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 25 03:51:49 node-1 haproxy[4600]: proxy keystone-2 has no server available!
<129>Jul 25 03:51:49 node-1 haproxy[4600]: 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 25 03:51:49 node-1 haproxy[4600]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:49 node-1 haproxy[4600]: 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 25 03:51:49 node-1 haproxy[4600]: proxy neutron has no server available!
<129>Jul 25 03:51:49 node-1 haproxy[4600]: 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 25 03:51:49 node-1 haproxy[4600]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:49 node-1 haproxy[4600]: 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 25 03:51:49 node-1 haproxy[4600]: proxy mysqld has no server available!
<129>Jul 25 03:51:49 node-1 haproxy[4600]: 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 25 03:51:49 node-1 haproxy[4600]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:50 node-1 haproxy[4600]: 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 25 03:51:50 node-1 haproxy[4600]: proxy object-storage has no server available!
<129>Jul 25 03:51:50 node-1 haproxy[4600]: 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 25 03:51:50 node-1 haproxy[4600]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:50 node-1 haproxy[4600]: 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 25 03:51:50 node-1 haproxy[4600]: proxy aodh has no server available!
<129>Jul 25 03:51:50 node-1 haproxy[4600]: 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 25 03:51:50 node-1 haproxy[4600]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:50 node-1 haproxy[4600]: 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 25 03:51:50 node-1 haproxy[4600]: proxy ceilometer has no server available!
<27>Jul 25 03:51:51 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:51 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:51 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:51 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:51 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:51 node-1 multipathd: uevent trigger error
<129>Jul 25 03:51:54 node-1 haproxy[6000]: 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 25 03:51:54 node-1 haproxy[6000]: 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 25 03:51:54 node-1 haproxy[6000]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:54 node-1 haproxy[6000]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 03:51:54 node-1 haproxy[6000]: proxy keystone-1 has no server available!
<129>Jul 25 03:51:54 node-1 haproxy[6000]: 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 25 03:51:54 node-1 haproxy[6000]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:54 node-1 haproxy[6000]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 03:51:54 node-1 haproxy[6000]: proxy keystone-2 has no server available!
<129>Jul 25 03:51:54 node-1 haproxy[6000]: 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 25 03:51:54 node-1 haproxy[6000]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:55 node-1 haproxy[6009]: 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 25 03:51:55 node-1 haproxy[6009]: proxy neutron has no server available!
<129>Jul 25 03:51:55 node-1 haproxy[6009]: 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 25 03:51:55 node-1 haproxy[6009]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:55 node-1 haproxy[6009]: 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 25 03:51:55 node-1 haproxy[6009]: proxy mysqld has no server available!
<129>Jul 25 03:51:55 node-1 haproxy[6009]: 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 25 03:51:55 node-1 haproxy[6009]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:55 node-1 haproxy[6009]: 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 25 03:51:55 node-1 haproxy[6009]: proxy object-storage has no server available!
<129>Jul 25 03:51:55 node-1 haproxy[6009]: 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 25 03:51:55 node-1 haproxy[6009]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:55 node-1 haproxy[6009]: 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 25 03:51:55 node-1 haproxy[6009]: proxy aodh has no server available!
<129>Jul 25 03:51:55 node-1 haproxy[6009]: 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 25 03:51:55 node-1 haproxy[6009]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:51:55 node-1 haproxy[6009]: 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 25 03:51:55 node-1 haproxy[6009]: proxy ceilometer has no server available!
<27>Jul 25 03:51:57 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:57 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:57 node-1 multipathd: uevent trigger error
<27>Jul 25 03:51:57 node-1 multipathd: uevent trigger error
<129>Jul 25 03:52:00 node-1 haproxy[7511]: 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 25 03:52:00 node-1 haproxy[7511]: 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 25 03:52:00 node-1 haproxy[7511]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:00 node-1 haproxy[7511]: 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 25 03:52:00 node-1 haproxy[7511]: proxy keystone-1 has no server available!
<129>Jul 25 03:52:00 node-1 haproxy[7511]: 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 25 03:52:00 node-1 haproxy[7511]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:00 node-1 haproxy[7511]: 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 25 03:52:00 node-1 haproxy[7511]: proxy keystone-2 has no server available!
<129>Jul 25 03:52:00 node-1 haproxy[7511]: 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 25 03:52:00 node-1 haproxy[7511]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:00 node-1 haproxy[7511]: 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 25 03:52:00 node-1 haproxy[7511]: proxy glance-api has no server available!
<129>Jul 25 03:52:00 node-1 haproxy[7511]: 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 25 03:52:00 node-1 haproxy[7511]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:00 node-1 haproxy[7511]: 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 25 03:52:00 node-1 haproxy[7511]: proxy glance-glare has no server available!
<129>Jul 25 03:52:00 node-1 haproxy[7511]: 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 25 03:52:00 node-1 haproxy[7511]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:00 node-1 haproxy[7511]: 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 25 03:52:00 node-1 haproxy[7511]: proxy neutron has no server available!
<129>Jul 25 03:52:01 node-1 haproxy[7518]: 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 25 03:52:01 node-1 haproxy[7518]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:01 node-1 haproxy[7518]: 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 25 03:52:01 node-1 haproxy[7518]: proxy glance-registry has no server available!
<129>Jul 25 03:52:01 node-1 haproxy[7518]: 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 25 03:52:01 node-1 haproxy[7518]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:01 node-1 haproxy[7518]: 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 25 03:52:01 node-1 haproxy[7518]: proxy mysqld has no server available!
<129>Jul 25 03:52:01 node-1 haproxy[7518]: 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 25 03:52:01 node-1 haproxy[7518]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:01 node-1 haproxy[7518]: 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 25 03:52:01 node-1 haproxy[7518]: proxy object-storage has no server available!
<129>Jul 25 03:52:01 node-1 haproxy[7518]: 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 25 03:52:01 node-1 haproxy[7518]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:01 node-1 haproxy[7518]: 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 25 03:52:01 node-1 haproxy[7518]: proxy aodh has no server available!
<129>Jul 25 03:52:01 node-1 haproxy[7518]: 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 25 03:52:01 node-1 haproxy[7518]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:01 node-1 haproxy[7518]: 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 25 03:52:01 node-1 haproxy[7518]: proxy ceilometer has no server available!
<27>Jul 25 03:52:03 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:03 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:03 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:03 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:03 node-1 multipathd: uevent trigger error
<129>Jul 25 03:52:05 node-1 haproxy[9230]: 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 25 03:52:06 node-1 haproxy[9237]: 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 25 03:52:06 node-1 haproxy[9237]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:06 node-1 haproxy[9237]: 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 25 03:52:06 node-1 haproxy[9237]: proxy keystone-1 has no server available!
<129>Jul 25 03:52:06 node-1 haproxy[9237]: 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 25 03:52:06 node-1 haproxy[9237]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:06 node-1 haproxy[9237]: 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 25 03:52:06 node-1 haproxy[9237]: proxy keystone-2 has no server available!
<129>Jul 25 03:52:06 node-1 haproxy[9237]: 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 25 03:52:06 node-1 haproxy[9237]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:06 node-1 haproxy[9237]: 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 25 03:52:06 node-1 haproxy[9237]: proxy nova-api has no server available!
<129>Jul 25 03:52:06 node-1 haproxy[9237]: 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 25 03:52:06 node-1 haproxy[9237]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:06 node-1 haproxy[9237]: 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 25 03:52:06 node-1 haproxy[9237]: proxy nova-metadata-api has no server available!
<129>Jul 25 03:52:06 node-1 haproxy[9237]: 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 25 03:52:06 node-1 haproxy[9237]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:06 node-1 haproxy[9237]: 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 25 03:52:06 node-1 haproxy[9237]: proxy glance-api has no server available!
<129>Jul 25 03:52:06 node-1 haproxy[9237]: 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 25 03:52:06 node-1 haproxy[9237]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:06 node-1 haproxy[9237]: 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 25 03:52:06 node-1 haproxy[9237]: proxy glance-glare has no server available!
<129>Jul 25 03:52:06 node-1 haproxy[9237]: 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 25 03:52:06 node-1 haproxy[9237]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:07 node-1 haproxy[9237]: 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 25 03:52:07 node-1 haproxy[9237]: proxy neutron has no server available!
<129>Jul 25 03:52:07 node-1 haproxy[9237]: 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 25 03:52:07 node-1 haproxy[9237]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:07 node-1 haproxy[9237]: 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 25 03:52:07 node-1 haproxy[9237]: proxy glance-registry has no server available!
<129>Jul 25 03:52:07 node-1 haproxy[9237]: 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 25 03:52:07 node-1 haproxy[9237]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:07 node-1 haproxy[9237]: 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 25 03:52:07 node-1 haproxy[9237]: proxy mysqld has no server available!
<129>Jul 25 03:52:07 node-1 haproxy[9237]: 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 25 03:52:07 node-1 haproxy[9237]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:07 node-1 haproxy[9237]: 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 25 03:52:07 node-1 haproxy[9237]: proxy object-storage has no server available!
<129>Jul 25 03:52:07 node-1 haproxy[9237]: 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 25 03:52:07 node-1 haproxy[9237]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:07 node-1 haproxy[9237]: 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 25 03:52:07 node-1 haproxy[9237]: proxy aodh has no server available!
<129>Jul 25 03:52:07 node-1 haproxy[9237]: 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 25 03:52:07 node-1 haproxy[9237]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:07 node-1 haproxy[9237]: 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 25 03:52:07 node-1 haproxy[9237]: proxy ceilometer has no server available!
<129>Jul 25 03:52:07 node-1 haproxy[9237]: 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 25 03:52:07 node-1 haproxy[9237]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:07 node-1 haproxy[9237]: 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 25 03:52:07 node-1 haproxy[9237]: proxy nova-novncproxy has no server available!
<27>Jul 25 03:52:08 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 03:52:09 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:09 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:09 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:09 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:09 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:09 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:09 node-1 multipathd: uevent trigger error
<129>Jul 25 03:52:11 node-1 haproxy[10678]: 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 25 03:52:11 node-1 haproxy[10678]: 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 25 03:52:11 node-1 haproxy[10678]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:11 node-1 haproxy[10678]: 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 25 03:52:11 node-1 haproxy[10678]: proxy keystone-1 has no server available!
<129>Jul 25 03:52:11 node-1 haproxy[10678]: 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 25 03:52:11 node-1 haproxy[10678]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:11 node-1 haproxy[10678]: 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 25 03:52:11 node-1 haproxy[10678]: proxy keystone-2 has no server available!
<129>Jul 25 03:52:11 node-1 haproxy[10678]: 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 25 03:52:11 node-1 haproxy[10678]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:11 node-1 haproxy[10678]: 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 25 03:52:11 node-1 haproxy[10678]: proxy nova-api has no server available!
<129>Jul 25 03:52:11 node-1 haproxy[10678]: 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 25 03:52:11 node-1 haproxy[10678]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:11 node-1 haproxy[10678]: 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 25 03:52:11 node-1 haproxy[10678]: proxy nova-metadata-api has no server available!
<129>Jul 25 03:52:11 node-1 haproxy[10678]: 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 25 03:52:11 node-1 haproxy[10678]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:11 node-1 haproxy[10678]: 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 25 03:52:11 node-1 haproxy[10678]: proxy cinder-api has no server available!
<129>Jul 25 03:52:12 node-1 haproxy[10685]: 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 25 03:52:12 node-1 haproxy[10685]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:12 node-1 haproxy[10685]: 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 25 03:52:12 node-1 haproxy[10685]: proxy glance-api has no server available!
<129>Jul 25 03:52:12 node-1 haproxy[10685]: 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 25 03:52:12 node-1 haproxy[10685]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:12 node-1 haproxy[10685]: 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 25 03:52:12 node-1 haproxy[10685]: proxy glance-glare has no server available!
<129>Jul 25 03:52:12 node-1 haproxy[10685]: 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 25 03:52:12 node-1 haproxy[10685]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:12 node-1 haproxy[10685]: 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 25 03:52:12 node-1 haproxy[10685]: proxy neutron has no server available!
<129>Jul 25 03:52:12 node-1 haproxy[10685]: 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 25 03:52:12 node-1 haproxy[10685]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:12 node-1 haproxy[10685]: 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 25 03:52:12 node-1 haproxy[10685]: proxy glance-registry has no server available!
<129>Jul 25 03:52:12 node-1 haproxy[10685]: 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 25 03:52:12 node-1 haproxy[10685]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:12 node-1 haproxy[10685]: 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 25 03:52:12 node-1 haproxy[10685]: proxy mysqld has no server available!
<129>Jul 25 03:52:12 node-1 haproxy[10685]: 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 25 03:52:12 node-1 haproxy[10685]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:12 node-1 haproxy[10685]: 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 25 03:52:12 node-1 haproxy[10685]: proxy object-storage has no server available!
<129>Jul 25 03:52:12 node-1 haproxy[10685]: 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 25 03:52:12 node-1 haproxy[10685]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:12 node-1 haproxy[10685]: 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 25 03:52:12 node-1 haproxy[10685]: proxy aodh has no server available!
<129>Jul 25 03:52:12 node-1 haproxy[10685]: 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 25 03:52:12 node-1 haproxy[10685]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:13 node-1 haproxy[10685]: 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 25 03:52:13 node-1 haproxy[10685]: proxy ceilometer has no server available!
<129>Jul 25 03:52:13 node-1 haproxy[10685]: 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 25 03:52:13 node-1 haproxy[10685]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:13 node-1 haproxy[10685]: 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 25 03:52:13 node-1 haproxy[10685]: proxy nova-novncproxy has no server available!
<27>Jul 25 03:52:14 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:14 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:14 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:14 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:14 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:15 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: proxy keystone-1 has no server available!
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: proxy keystone-2 has no server available!
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: proxy nova-api has no server available!
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: proxy nova-metadata-api has no server available!
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: proxy cinder-api has no server available!
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: proxy glance-api has no server available!
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: proxy glance-glare has no server available!
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:17 node-1 haproxy[12257]: proxy neutron has no server available!
<129>Jul 25 03:52:17 node-1 haproxy[12257]: 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 25 03:52:18 node-1 haproxy[12261]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: proxy glance-registry has no server available!
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: proxy mysqld has no server available!
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: proxy object-storage has no server available!
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: proxy aodh has no server available!
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: proxy ceilometer has no server available!
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: proxy heat-api has no server available!
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: proxy heat-api-cfn has no server available!
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: proxy heat-api-cloudwatch has no server available!
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 03:52:18 node-1 haproxy[12261]: 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 25 03:52:18 node-1 haproxy[12261]: proxy nova-novncproxy has no server available!
<27>Jul 25 03:52:20 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:20 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:20 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:20 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:20 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:23 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:23 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:23 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:23 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:23 node-1 multipathd: uevent trigger error
<27>Jul 25 03:52:33 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 25 03:52:58 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 25 03:53:00 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 25 03:53:53 node-1 multipathd: uevent trigger error
<27>Jul 25 03:53:53 node-1 multipathd: uevent trigger error
<27>Jul 25 03:53:53 node-1 multipathd: uevent trigger error
<27>Jul 25 03:53:53 node-1 multipathd: uevent trigger error
<27>Jul 25 03:55:32 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 03:56:13 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:13 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:13 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:14 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:14 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:14 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:20 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:20 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:20 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:20 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:20 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:25 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:25 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:25 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:25 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:25 node-1 multipathd: uevent trigger error
<43>Jul 25 03:56:45 node-1 apache2_error [Mon Jul 25 03:56:38.390502 2016] [mpm_event:notice] [pid 25892:tid 140649865729920] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 25 03:56:45 node-1 apache2_error [Mon Jul 25 03:56:38.390655 2016] [core:notice] [pid 25892:tid 140649865729920] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 25 03:56:45 node-1 apache2_error [Mon Jul 25 03:56:41.601899 2016] [mpm_event:notice] [pid 25892:tid 140649865729920] AH00491: caught SIGTERM, shutting down
<43>Jul 25 03:56:45 node-1 apache2_error [Mon Jul 25 03:56:42.692424 2016] [mpm_worker:notice] [pid 26246:tid 140008652826496] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 25 03:56:45 node-1 apache2_error [Mon Jul 25 03:56:42.692481 2016] [core:notice] [pid 26246:tid 140008652826496] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 03:56:47 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:47 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:47 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:47 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:47 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:50 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:50 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:50 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:50 node-1 multipathd: uevent trigger error
<27>Jul 25 03:56:50 node-1 multipathd: uevent trigger error
<43>Jul 25 03:58:05 node-1 apache2_error [Mon Jul 25 03:57:59.723850 2016] [mpm_worker:notice] [pid 26246:tid 140008652826496] AH00295: caught SIGTERM, shutting down
<43>Jul 25 03:58:05 node-1 apache2_error [Mon Jul 25 03:58:00.491795 2016] [mpm_worker:notice] [pid 7275:tid 140055384287104] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 03:58:05 node-1 apache2_error [Mon Jul 25 03:58:00.491823 2016] [core:notice] [pid 7275:tid 140055384287104] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 03:58:33 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 25 03:58:45 node-1 apache2_error [Mon Jul 25 03:58:44.465140 2016] [mpm_worker:notice] [pid 7275:tid 140055384287104] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 03:58:45 node-1 apache2_error [Mon Jul 25 03:58:44.658581 2016] [mpm_worker:warn] [pid 7275:tid 140055384287104] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 03:58:45 node-1 apache2_error [Mon Jul 25 03:58:44.661595 2016] [mpm_worker:notice] [pid 7275:tid 140055384287104] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 03:58:45 node-1 apache2_error [Mon Jul 25 03:58:44.661610 2016] [core:notice] [pid 7275:tid 140055384287104] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 03:59:29 node-1 multipathd: uevent trigger error
<27>Jul 25 03:59:29 node-1 multipathd: uevent trigger error
<27>Jul 25 03:59:29 node-1 multipathd: uevent trigger error
<27>Jul 25 03:59:29 node-1 multipathd: uevent trigger error
<27>Jul 25 03:59:29 node-1 multipathd: uevent trigger error
<27>Jul 25 03:59:33 node-1 multipathd: uevent trigger error
<27>Jul 25 03:59:33 node-1 multipathd: uevent trigger error
<27>Jul 25 03:59:33 node-1 multipathd: uevent trigger error
<27>Jul 25 03:59:33 node-1 multipathd: uevent trigger error
<27>Jul 25 03:59:33 node-1 multipathd: uevent trigger error
<27>Jul 25 03:59:33 node-1 multipathd: uevent trigger error
<27>Jul 25 03:59:49 node-1 multipathd: uevent trigger error
<27>Jul 25 03:59:49 node-1 multipathd: uevent trigger error
<27>Jul 25 03:59:49 node-1 multipathd: uevent trigger error
<27>Jul 25 03:59:49 node-1 multipathd: uevent trigger error
<27>Jul 25 03:59:49 node-1 multipathd: uevent trigger error
<27>Jul 25 04:00:10 node-1 multipathd: uevent trigger error
<27>Jul 25 04:00:10 node-1 multipathd: uevent trigger error
<27>Jul 25 04:00:10 node-1 multipathd: uevent trigger error
<27>Jul 25 04:00:10 node-1 multipathd: uevent trigger error
<27>Jul 25 04:00:10 node-1 multipathd: uevent trigger error
<27>Jul 25 04:00:15 node-1 multipathd: uevent trigger error
<27>Jul 25 04:00:15 node-1 multipathd: uevent trigger error
<27>Jul 25 04:00:16 node-1 multipathd: uevent trigger error
<27>Jul 25 04:00:16 node-1 multipathd: uevent trigger error
<27>Jul 25 04:00:16 node-1 multipathd: uevent trigger error
<27>Jul 25 04:00:30 node-1 multipathd: uevent trigger error
<27>Jul 25 04:00:30 node-1 multipathd: uevent trigger error
<27>Jul 25 04:00:30 node-1 multipathd: uevent trigger error
<27>Jul 25 04:00:30 node-1 multipathd: uevent trigger error
<27>Jul 25 04:00:30 node-1 multipathd: uevent trigger error
<27>Jul 25 04:00:30 node-1 multipathd: uevent trigger error
<27>Jul 25 04:01:29 node-1 multipathd: uevent trigger error
<27>Jul 25 04:01:29 node-1 multipathd: uevent trigger error
<27>Jul 25 04:01:29 node-1 multipathd: uevent trigger error
<27>Jul 25 04:01:29 node-1 multipathd: uevent trigger error
<27>Jul 25 04:01:29 node-1 multipathd: uevent trigger error
<27>Jul 25 04:01:35 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 04:02:42 node-1 multipathd: uevent trigger error
<27>Jul 25 04:02:42 node-1 multipathd: uevent trigger error
<27>Jul 25 04:02:42 node-1 multipathd: uevent trigger error
<27>Jul 25 04:02:42 node-1 multipathd: uevent trigger error
<27>Jul 25 04:02:42 node-1 multipathd: uevent trigger error
<27>Jul 25 04:03:40 node-1 multipathd: uevent trigger error
<27>Jul 25 04:03:40 node-1 multipathd: uevent trigger error
<27>Jul 25 04:03:40 node-1 multipathd: uevent trigger error
<27>Jul 25 04:03:40 node-1 multipathd: uevent trigger error
<27>Jul 25 04:03:46 node-1 multipathd: uevent trigger error
<27>Jul 25 04:03:46 node-1 multipathd: uevent trigger error
<27>Jul 25 04:03:46 node-1 multipathd: uevent trigger error
<27>Jul 25 04:03:46 node-1 multipathd: uevent trigger error
<27>Jul 25 04:03:46 node-1 multipathd: uevent trigger error
<27>Jul 25 04:04:10 node-1 multipathd: uevent trigger error
<27>Jul 25 04:04:10 node-1 multipathd: uevent trigger error
<27>Jul 25 04:04:10 node-1 multipathd: uevent trigger error
<27>Jul 25 04:04:10 node-1 multipathd: uevent trigger error
<27>Jul 25 04:04:37 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 04:06:38 node-1 multipathd: uevent trigger error
<27>Jul 25 04:06:38 node-1 multipathd: uevent trigger error
<27>Jul 25 04:06:38 node-1 multipathd: uevent trigger error
<27>Jul 25 04:06:38 node-1 multipathd: uevent trigger error
<27>Jul 25 04:06:38 node-1 multipathd: uevent trigger error
<27>Jul 25 04:06:52 node-1 multipathd: uevent trigger error
<27>Jul 25 04:06:52 node-1 multipathd: uevent trigger error
<27>Jul 25 04:06:52 node-1 multipathd: uevent trigger error
<27>Jul 25 04:06:52 node-1 multipathd: uevent trigger error
<27>Jul 25 04:06:52 node-1 multipathd: uevent trigger error
<27>Jul 25 04:06:58 node-1 multipathd: uevent trigger error
<27>Jul 25 04:06:58 node-1 multipathd: uevent trigger error
<27>Jul 25 04:06:58 node-1 multipathd: uevent trigger error
<27>Jul 25 04:06:58 node-1 multipathd: uevent trigger error
<27>Jul 25 04:06:58 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:03 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:04 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:04 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:04 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:04 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:24 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:24 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:24 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:24 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:24 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:24 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:28 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:28 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:28 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:28 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:28 node-1 multipathd: uevent trigger error
<27>Jul 25 04:07:38 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 04:08:12 node-1 multipathd: uevent trigger error
<27>Jul 25 04:08:12 node-1 multipathd: uevent trigger error
<27>Jul 25 04:08:12 node-1 multipathd: uevent trigger error
<27>Jul 25 04:08:12 node-1 multipathd: uevent trigger error
<27>Jul 25 04:08:56 node-1 multipathd: uevent trigger error
<27>Jul 25 04:08:56 node-1 multipathd: uevent trigger error
<27>Jul 25 04:08:56 node-1 multipathd: uevent trigger error
<27>Jul 25 04:08:56 node-1 multipathd: uevent trigger error
<27>Jul 25 04:08:56 node-1 multipathd: uevent trigger error
<27>Jul 25 04:08:56 node-1 multipathd: uevent trigger error
<27>Jul 25 04:09:12 node-1 multipathd: uevent trigger error
<27>Jul 25 04:09:12 node-1 multipathd: uevent trigger error
<27>Jul 25 04:09:12 node-1 multipathd: uevent trigger error
<27>Jul 25 04:09:12 node-1 multipathd: uevent trigger error
<27>Jul 25 04:10:40 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 04:11:34 node-1 multipathd: uevent trigger error
<27>Jul 25 04:11:34 node-1 multipathd: uevent trigger error
<27>Jul 25 04:11:34 node-1 multipathd: uevent trigger error
<27>Jul 25 04:11:34 node-1 multipathd: uevent trigger error
<27>Jul 25 04:11:34 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:08 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:08 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:08 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:08 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:13 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:13 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:13 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:13 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:52 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:52 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:52 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:52 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:56 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:56 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:56 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:56 node-1 multipathd: uevent trigger error
<27>Jul 25 04:12:56 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:01 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:01 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:01 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:01 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:13 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:13 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:13 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:13 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:19 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:19 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:19 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:19 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:20 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:41 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 04:13:58 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:58 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:58 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:58 node-1 multipathd: uevent trigger error
<27>Jul 25 04:13:58 node-1 multipathd: uevent trigger error
<27>Jul 25 04:15:04 node-1 multipathd: uevent trigger error
<27>Jul 25 04:15:04 node-1 multipathd: uevent trigger error
<27>Jul 25 04:15:04 node-1 multipathd: uevent trigger error
<27>Jul 25 04:15:04 node-1 multipathd: uevent trigger error
<27>Jul 25 04:15:04 node-1 multipathd: uevent trigger error
<27>Jul 25 04:15:22 node-1 multipathd: uevent trigger error
<27>Jul 25 04:15:22 node-1 multipathd: uevent trigger error
<27>Jul 25 04:15:22 node-1 multipathd: uevent trigger error
<27>Jul 25 04:15:22 node-1 multipathd: uevent trigger error
<11>Jul 25 04:15:35 node-1 liberasurecode[21000]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:35 node-1 liberasurecode[21000]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:35 node-1 liberasurecode[21000]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:35 node-1 liberasurecode[21000]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:35 node-1 liberasurecode[21067]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:35 node-1 liberasurecode[21067]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:35 node-1 liberasurecode[21067]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:35 node-1 liberasurecode[21067]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:37 node-1 liberasurecode[21685]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:37 node-1 liberasurecode[21685]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:37 node-1 liberasurecode[21685]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:37 node-1 liberasurecode[21685]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22353]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22353]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22353]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22353]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22395]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22395]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22395]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22395]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22466]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22466]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22466]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22466]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22529]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22529]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22529]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22529]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22541]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22541]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22541]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22541]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22559]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22559]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22559]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:43 node-1 liberasurecode[22559]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:44 node-1 liberasurecode[22573]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:44 node-1 liberasurecode[22573]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:44 node-1 liberasurecode[22573]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:44 node-1 liberasurecode[22573]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:52 node-1 liberasurecode[23059]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:52 node-1 liberasurecode[23059]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:52 node-1 liberasurecode[23059]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:15:52 node-1 liberasurecode[23059]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 25 04:16:01 node-1 multipathd: uevent trigger error
<27>Jul 25 04:16:01 node-1 multipathd: uevent trigger error
<27>Jul 25 04:16:01 node-1 multipathd: uevent trigger error
<27>Jul 25 04:16:01 node-1 multipathd: uevent trigger error
<27>Jul 25 04:16:43 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 25 04:16:56 node-1 apache2_error [Mon Jul 25 04:16:48.831972 2016] [mpm_worker:notice] [pid 7275:tid 140055384287104] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 04:16:56 node-1 apache2_error [Mon Jul 25 04:16:49.215576 2016] [mpm_worker:warn] [pid 7275:tid 140055384287104] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 04:16:56 node-1 apache2_error [Mon Jul 25 04:16:49.221023 2016] [mpm_worker:notice] [pid 7275:tid 140055384287104] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 04:16:56 node-1 apache2_error [Mon Jul 25 04:16:49.221046 2016] [core:notice] [pid 7275:tid 140055384287104] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 25 04:17:26 node-1 apache2_error [Mon Jul 25 04:17:26.339430 2016] [mpm_worker:notice] [pid 7275:tid 140055384287104] AH00297: SIGUSR1 received.  Doing graceful restart
<27>Jul 25 04:17:30 node-1 multipathd: uevent trigger error
<27>Jul 25 04:17:30 node-1 multipathd: uevent trigger error
<27>Jul 25 04:17:30 node-1 multipathd: uevent trigger error
<27>Jul 25 04:17:30 node-1 multipathd: uevent trigger error
<27>Jul 25 04:17:30 node-1 multipathd: uevent trigger error
<43>Jul 25 04:17:36 node-1 apache2_error [Mon Jul 25 04:17:27.853792 2016] [mpm_worker:warn] [pid 7275:tid 140055384287104] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 04:17:36 node-1 apache2_error [Mon Jul 25 04:17:27.863973 2016] [mpm_worker:notice] [pid 7275:tid 140055384287104] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 04:17:36 node-1 apache2_error [Mon Jul 25 04:17:27.864000 2016] [core:notice] [pid 7275:tid 140055384287104] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 04:17:36 node-1 multipathd: uevent trigger error
<27>Jul 25 04:17:36 node-1 multipathd: uevent trigger error
<27>Jul 25 04:17:36 node-1 multipathd: uevent trigger error
<27>Jul 25 04:17:36 node-1 multipathd: uevent trigger error
<27>Jul 25 04:17:37 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:15 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:15 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:15 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:15 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:15 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:15 node-1 multipathd: uevent trigger error
<43>Jul 25 04:18:16 node-1 apache2_error [Mon Jul 25 04:18:11.455016 2016] [mpm_worker:notice] [pid 7275:tid 140055384287104] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 04:18:16 node-1 apache2_error [Mon Jul 25 04:18:11.650210 2016] [mpm_worker:warn] [pid 7275:tid 140055384287104] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 04:18:16 node-1 apache2_error [Mon Jul 25 04:18:11.660556 2016] [mpm_worker:notice] [pid 7275:tid 140055384287104] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 04:18:16 node-1 apache2_error [Mon Jul 25 04:18:11.660591 2016] [core:notice] [pid 7275:tid 140055384287104] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 04:18:22 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:22 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:22 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:22 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:28 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:28 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:28 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:28 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:28 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:37 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:37 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:37 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:37 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:37 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:52 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:53 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:53 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:53 node-1 multipathd: uevent trigger error
<27>Jul 25 04:18:53 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:13 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:21 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 25 04:19:30 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:30 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:30 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:30 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:30 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:35 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:35 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:35 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:35 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:41 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:41 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:41 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:41 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:41 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:54 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:54 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:54 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:54 node-1 multipathd: uevent trigger error
<27>Jul 25 04:19:54 node-1 multipathd: uevent trigger error
<11>Jul 25 04:20:01 node-1 liberasurecode[12690]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:20:01 node-1 liberasurecode[12690]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:20:01 node-1 liberasurecode[12690]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 04:20:01 node-1 liberasurecode[12690]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 25 04:20:15 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 04:20:21 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:21 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:21 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:21 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:21 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:25 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:25 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:25 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:25 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:25 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:38 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:38 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:38 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:38 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:46 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:46 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:46 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:46 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:51 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:51 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:51 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:51 node-1 multipathd: uevent trigger error
<27>Jul 25 04:20:51 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:03 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:03 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:03 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:03 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:03 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:32 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:32 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:32 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:32 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:36 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:36 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:36 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:36 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:36 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:41 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:41 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:41 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:41 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:41 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:46 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:46 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:46 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:46 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:46 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:51 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:51 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:51 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:51 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:51 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:55 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:55 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:55 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:55 node-1 multipathd: uevent trigger error
<27>Jul 25 04:21:55 node-1 multipathd: uevent trigger error
