Jul 27 03:51:01 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8403" x-info="http://www.rsyslog.com"] start
Jul 27 03:51:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 27 03:51:01 node-1 rsyslogd: rsyslogd's groupid changed to 104
Jul 27 03:51:01 node-1 rsyslogd: rsyslogd's userid changed to 101
Jul 27 03:51:01 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 27 03:51:01 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 27 03:51:01 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 27 03:51:01 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 27 03:51:01 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=669b3aed-3e94-4357-a92c-d3b4698d6016 nomdmonddf nomdmonisw
Jul 27 03:51:01 node-1 kernel: [    0.000000] KERNEL supported cpus:
Jul 27 03:51:01 node-1 kernel: [    0.000000]   Intel GenuineIntel
Jul 27 03:51:01 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Jul 27 03:51:01 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Jul 27 03:51:01 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 27 03:51:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 27 03:51:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 27 03:51:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 27 03:51:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 27 03:51:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 27 03:51:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 27 03:51:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 27 03:51:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 27 03:51:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 27 03:51:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 27 03:51:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 27 03:51:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 27 03:51:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 27 03:51:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 27 03:51:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 27 03:51:01 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 27 03:51:01 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 27 03:51:01 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 27 03:51:01 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 27 03:51:01 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 27 03:51:01 node-1 kernel: [    0.000000] No AGP bridge found
Jul 27 03:51:01 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 27 03:51:01 node-1 kernel: [    0.000000] MTRR default type: write-back
Jul 27 03:51:01 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 27 03:51:01 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Jul 27 03:51:01 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 27 03:51:01 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 27 03:51:01 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 27 03:51:01 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 27 03:51:01 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 27 03:51:01 node-1 kernel: [    0.000000]   2 disabled
Jul 27 03:51:01 node-1 kernel: [    0.000000]   3 disabled
Jul 27 03:51:01 node-1 kernel: [    0.000000]   4 disabled
Jul 27 03:51:01 node-1 kernel: [    0.000000]   5 disabled
Jul 27 03:51:01 node-1 kernel: [    0.000000]   6 disabled
Jul 27 03:51:01 node-1 kernel: [    0.000000]   7 disabled
Jul 27 03:51:01 node-1 kernel: [    0.000000]   8 disabled
Jul 27 03:51:01 node-1 kernel: [    0.000000]   9 disabled
Jul 27 03:51:01 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 27 03:51:01 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 27 03:51:01 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 27 03:51:01 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 27 03:51:01 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 27 03:51:01 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Jul 27 03:51:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 27 03:51:01 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 27 03:51:01 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 27 03:51:01 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 27 03:51:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 27 03:51:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 27 03:51:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 27 03:51:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 27 03:51:01 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 27 03:51:01 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 27 03:51:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 27 03:51:01 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 27 03:51:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 27 03:51:01 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 27 03:51:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 27 03:51:01 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 27 03:51:01 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 27 03:51:01 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 27 03:51:01 node-1 kernel: [    0.000000] Zone ranges:
Jul 27 03:51:01 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] Movable zone start for each node
Jul 27 03:51:01 node-1 kernel: [    0.000000] Early memory node ranges
Jul 27 03:51:01 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 27 03:51:01 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 27 03:51:01 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 27 03:51:01 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 27 03:51:01 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 27 03:51:01 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 27 03:51:01 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 27 03:51:01 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 27 03:51:01 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 27 03:51:01 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 27 03:51:01 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 27 03:51:01 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 27 03:51:01 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 27 03:51:01 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 27 03:51:01 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 27 03:51:01 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 27 03:51:01 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 27 03:51:01 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 27 03:51:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 27 03:51:01 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 27 03:51:01 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 27 03:51:01 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 27 03:51:01 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 27 03:51:01 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 27 03:51:01 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 27 03:51:01 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 27 03:51:01 node-1 kernel: [    0.000000] Policy zone: Normal
Jul 27 03:51:01 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=669b3aed-3e94-4357-a92c-d3b4698d6016 nomdmonddf nomdmonisw
Jul 27 03:51:01 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 27 03:51:01 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 27 03:51:01 node-1 kernel: [    0.000000] Checking aperture...
Jul 27 03:51:01 node-1 kernel: [    0.000000] No AGP bridge found
Jul 27 03:51:01 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 27 03:51:01 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 27 03:51:01 node-1 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 27 03:51:01 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 27 03:51:01 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 27 03:51:01 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 27 03:51:01 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 27 03:51:01 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 27 03:51:01 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 27 03:51:01 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 27 03:51:01 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 27 03:51:01 node-1 kernel: [    0.000000] console [tty0] enabled
Jul 27 03:51:01 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 27 03:51:01 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 27 03:51:01 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 27 03:51:01 node-1 kernel: [    0.000000] hpet clockevent registered
Jul 27 03:51:01 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 27 03:51:01 node-1 kernel: [    0.004000] tsc: Detected 3491.795 MHz processor
Jul 27 03:51:01 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.59 BogoMIPS (lpj=13967180)
Jul 27 03:51:01 node-1 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Jul 27 03:51:01 node-1 kernel: [    0.000042] Security Framework initialized
Jul 27 03:51:01 node-1 kernel: [    0.000061] AppArmor: AppArmor initialized
Jul 27 03:51:01 node-1 kernel: [    0.000062] Yama: becoming mindful.
Jul 27 03:51:01 node-1 kernel: [    0.001449] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 27 03:51:01 node-1 kernel: [    0.006343] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 27 03:51:01 node-1 kernel: [    0.008269] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 27 03:51:01 node-1 kernel: [    0.008298] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 27 03:51:01 node-1 kernel: [    0.008590] Initializing cgroup subsys memory
Jul 27 03:51:01 node-1 kernel: [    0.008598] Initializing cgroup subsys devices
Jul 27 03:51:01 node-1 kernel: [    0.008600] Initializing cgroup subsys freezer
Jul 27 03:51:01 node-1 kernel: [    0.008601] Initializing cgroup subsys blkio
Jul 27 03:51:01 node-1 kernel: [    0.008603] Initializing cgroup subsys perf_event
Jul 27 03:51:01 node-1 kernel: [    0.008605] Initializing cgroup subsys hugetlb
Jul 27 03:51:01 node-1 kernel: [    0.008625] CPU: Physical Processor ID: 0
Jul 27 03:51:01 node-1 kernel: [    0.008626] CPU: Processor Core ID: 0
Jul 27 03:51:01 node-1 kernel: [    0.008630] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 27 03:51:01 node-1 kernel: [    0.008630] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 27 03:51:01 node-1 kernel: [    0.009323] mce: CPU supports 22 MCE banks
Jul 27 03:51:01 node-1 kernel: [    0.009351] CPU0: Thermal monitoring enabled (TM1)
Jul 27 03:51:01 node-1 kernel: [    0.009371] process: using mwait in idle threads
Jul 27 03:51:01 node-1 kernel: [    0.009374] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 27 03:51:01 node-1 kernel: [    0.009374] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 27 03:51:01 node-1 kernel: [    0.009374] tlb_flushall_shift: 6
Jul 27 03:51:01 node-1 kernel: [    0.009463] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 27 03:51:01 node-1 kernel: [    0.010187] ACPI: Core revision 20131115
Jul 27 03:51:01 node-1 kernel: [    0.022851] ACPI: All ACPI Tables successfully acquired
Jul 27 03:51:01 node-1 kernel: [    0.023013] ftrace: allocating 28617 entries in 112 pages
Jul 27 03:51:01 node-1 kernel: [    0.031827] dmar: Host address width 46
Jul 27 03:51:01 node-1 kernel: [    0.031829] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 27 03:51:01 node-1 kernel: [    0.031835] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 27 03:51:01 node-1 kernel: [    0.031837] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 27 03:51:01 node-1 kernel: [    0.031841] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 27 03:51:01 node-1 kernel: [    0.031843] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 27 03:51:01 node-1 kernel: [    0.031844] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 27 03:51:01 node-1 kernel: [    0.031845] dmar: ATSR flags: 0x0
Jul 27 03:51:01 node-1 kernel: [    0.031846] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 27 03:51:01 node-1 kernel: [    0.031847] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 27 03:51:01 node-1 kernel: [    0.031962] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 27 03:51:01 node-1 kernel: [    0.031964] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 27 03:51:01 node-1 kernel: [    0.031965] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 27 03:51:01 node-1 kernel: [    0.031966] HPET id 0 under DRHD base 0xc7ffc000
Jul 27 03:51:01 node-1 kernel: [    0.031967] Your BIOS is broken and requested that x2apic be disabled.
Jul 27 03:51:01 node-1 kernel: [    0.031967] This will slightly decrease performance.
Jul 27 03:51:01 node-1 kernel: [    0.031967] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 27 03:51:01 node-1 kernel: [    0.032398] Enabled IRQ remapping in xapic mode
Jul 27 03:51:01 node-1 kernel: [    0.032399] x2apic not enabled, IRQ remapping is in xapic mode
Jul 27 03:51:01 node-1 kernel: [    0.032403] Switched APIC routing to physical flat.
Jul 27 03:51:01 node-1 kernel: [    0.033028] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 27 03:51:01 node-1 kernel: [    0.072676] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 27 03:51:01 node-1 kernel: [    0.072682] TSC deadline timer enabled
Jul 27 03:51:01 node-1 kernel: [    0.072689] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 27 03:51:01 node-1 kernel: [    0.072695] ... version:                3
Jul 27 03:51:01 node-1 kernel: [    0.072696] ... bit width:              48
Jul 27 03:51:01 node-1 kernel: [    0.072697] ... generic registers:      4
Jul 27 03:51:01 node-1 kernel: [    0.072698] ... value mask:             0000ffffffffffff
Jul 27 03:51:01 node-1 kernel: [    0.072699] ... max period:             0000ffffffffffff
Jul 27 03:51:01 node-1 kernel: [    0.072700] ... fixed-purpose events:   3
Jul 27 03:51:01 node-1 kernel: [    0.072701] ... event mask:             000000070000000f
Jul 27 03:51:01 node-1 kernel: [    0.074126] x86: Booting SMP configuration:
Jul 27 03:51:01 node-1 kernel: [    0.088230] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 27 03:51:01 node-1 kernel: [    0.074128] .... node  #0, CPUs:        #1  #2  #3
Jul 27 03:51:01 node-1 kernel: [    0.116135] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 27 03:51:01 node-1 kernel: [    0.270075] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 27 03:51:01 node-1 kernel: [    0.325686] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 27 03:51:01 node-1 kernel: [    0.382538] x86: Booted up 2 nodes, 16 CPUs
Jul 27 03:51:01 node-1 kernel: [    0.382542] smpboot: Total of 16 processors activated (111749.74 BogoMIPS)
Jul 27 03:51:01 node-1 kernel: [    0.406595] devtmpfs: initialized
Jul 27 03:51:01 node-1 kernel: [    0.409726] EVM: security.selinux
Jul 27 03:51:01 node-1 kernel: [    0.409728] EVM: security.SMACK64
Jul 27 03:51:01 node-1 kernel: [    0.409729] EVM: security.ima
Jul 27 03:51:01 node-1 kernel: [    0.409730] EVM: security.capability
Jul 27 03:51:01 node-1 kernel: [    0.409780] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 27 03:51:01 node-1 kernel: [    0.410463] pinctrl core: initialized pinctrl subsystem
Jul 27 03:51:01 node-1 kernel: [    0.410525] regulator-dummy: no parameters
Jul 27 03:51:01 node-1 kernel: [    0.410557] RTC time:  3:50:23, date: 07/27/16
Jul 27 03:51:01 node-1 kernel: [    0.410591] NET: Registered protocol family 16
Jul 27 03:51:01 node-1 kernel: [    0.410678] cpuidle: using governor ladder
Jul 27 03:51:01 node-1 kernel: [    0.410679] cpuidle: using governor menu
Jul 27 03:51:01 node-1 kernel: [    0.410712] ACPI: bus type PCI registered
Jul 27 03:51:01 node-1 kernel: [    0.410714] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 27 03:51:01 node-1 kernel: [    0.410760] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 27 03:51:01 node-1 kernel: [    0.410763] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 27 03:51:01 node-1 kernel: [    0.424496] PCI: Using configuration type 1 for base access
Jul 27 03:51:01 node-1 kernel: [    0.425497] bio: create slab <bio-0> at 0
Jul 27 03:51:01 node-1 kernel: [    0.425780] ACPI: Added _OSI(Module Device)
Jul 27 03:51:01 node-1 kernel: [    0.425782] ACPI: Added _OSI(Processor Device)
Jul 27 03:51:01 node-1 kernel: [    0.425783] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 27 03:51:01 node-1 kernel: [    0.425784] ACPI: Added _OSI(Processor Aggregator Device)
Jul 27 03:51:01 node-1 kernel: [    0.438443] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 27 03:51:01 node-1 kernel: [    0.448989] ACPI: Interpreter enabled
Jul 27 03:51:01 node-1 kernel: [    0.448995] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 27 03:51:01 node-1 kernel: [    0.448999] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 27 03:51:01 node-1 kernel: [    0.449001] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 27 03:51:01 node-1 kernel: [    0.449008] ACPI: (supports S0 S4 S5)
Jul 27 03:51:01 node-1 kernel: [    0.449009] ACPI: Using IOAPIC for interrupt routing
Jul 27 03:51:01 node-1 kernel: [    0.449049] HEST: Table parsing has been initialized.
Jul 27 03:51:01 node-1 kernel: [    0.449052] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 27 03:51:01 node-1 kernel: [    0.449602] ACPI: No dock devices found.
Jul 27 03:51:01 node-1 kernel: [    0.461234] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 27 03:51:01 node-1 kernel: [    0.461239] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 03:51:01 node-1 kernel: [    0.461243] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 27 03:51:01 node-1 kernel: [    0.461274] PCI host bridge to bus 0000:ff
Jul 27 03:51:01 node-1 kernel: [    0.461276] pci_bus 0000:ff: root bus resource [bus ff]
Jul 27 03:51:01 node-1 kernel: [    0.461284] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461322] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 27 03:51:01 node-1 kernel: [    0.461353] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461388] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461417] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 27 03:51:01 node-1 kernel: [    0.461447] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 27 03:51:01 node-1 kernel: [    0.461478] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461507] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461537] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461565] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461592] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461618] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461646] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461672] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461699] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461725] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461754] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461781] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461807] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 27 03:51:01 node-1 kernel: [    0.461835] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461861] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 27 03:51:01 node-1 kernel: [    0.461887] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461913] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.461943] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 27 03:51:01 node-1 kernel: [    0.461978] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462009] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462039] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462069] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462100] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462131] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462161] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462191] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462223] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462256] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462288] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462321] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462354] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462382] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462409] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462440] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462475] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462513] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462548] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462582] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462613] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462642] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462674] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462703] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462734] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462765] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462796] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462826] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462855] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462885] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462914] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462945] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.462976] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463032] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 27 03:51:01 node-1 kernel: [    0.463035] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 03:51:01 node-1 kernel: [    0.463038] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 27 03:51:01 node-1 kernel: [    0.463055] PCI host bridge to bus 0000:7f
Jul 27 03:51:01 node-1 kernel: [    0.463057] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 27 03:51:01 node-1 kernel: [    0.463062] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463088] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 27 03:51:01 node-1 kernel: [    0.463115] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463143] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463164] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 27 03:51:01 node-1 kernel: [    0.463189] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 27 03:51:01 node-1 kernel: [    0.463215] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463246] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463271] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463296] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463320] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463345] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463372] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463396] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463421] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463451] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463473] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463496] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463518] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 27 03:51:01 node-1 kernel: [    0.463542] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463564] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 27 03:51:01 node-1 kernel: [    0.463587] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463610] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463636] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 27 03:51:01 node-1 kernel: [    0.463670] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463696] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463722] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463748] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463773] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463802] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463830] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463860] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463884] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463911] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463939] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463966] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.463994] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464018] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464043] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464071] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464096] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464123] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464153] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464181] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464205] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464230] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464255] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464282] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464308] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464334] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464363] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464387] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464409] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464434] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464458] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464487] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.464512] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.465752] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 27 03:51:01 node-1 kernel: [    0.465756] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 03:51:01 node-1 kernel: [    0.466873] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 27 03:51:01 node-1 kernel: [    0.467382] PCI host bridge to bus 0000:00
Jul 27 03:51:01 node-1 kernel: [    0.467385] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 27 03:51:01 node-1 kernel: [    0.467386] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 27 03:51:01 node-1 kernel: [    0.467388] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 27 03:51:01 node-1 kernel: [    0.467389] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 27 03:51:01 node-1 kernel: [    0.467390] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 27 03:51:01 node-1 kernel: [    0.467392] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 27 03:51:01 node-1 kernel: [    0.467393] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 27 03:51:01 node-1 kernel: [    0.467399] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 27 03:51:01 node-1 kernel: [    0.467481] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 27 03:51:01 node-1 kernel: [    0.467512] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 27 03:51:01 node-1 kernel: [    0.467553] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 27 03:51:01 node-1 kernel: [    0.467572] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 27 03:51:01 node-1 kernel: [    0.467601] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 27 03:51:01 node-1 kernel: [    0.467641] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 27 03:51:01 node-1 kernel: [    0.467659] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 27 03:51:01 node-1 kernel: [    0.467688] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 27 03:51:01 node-1 kernel: [    0.467731] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 27 03:51:01 node-1 kernel: [    0.467747] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.467817] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.467892] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.467969] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 27 03:51:01 node-1 kernel: [    0.467974] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 27 03:51:01 node-1 kernel: [    0.468058] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 27 03:51:01 node-1 kernel: [    0.468206] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 27 03:51:01 node-1 kernel: [    0.468224] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 27 03:51:01 node-1 kernel: [    0.468302] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 27 03:51:01 node-1 kernel: [    0.468356] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 27 03:51:01 node-1 kernel: [    0.468377] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 27 03:51:01 node-1 kernel: [    0.468432] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 27 03:51:01 node-1 kernel: [    0.468475] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 27 03:51:01 node-1 kernel: [    0.468502] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 27 03:51:01 node-1 kernel: [    0.468557] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 27 03:51:01 node-1 kernel: [    0.468600] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 27 03:51:01 node-1 kernel: [    0.468624] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 27 03:51:01 node-1 kernel: [    0.468641] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 27 03:51:01 node-1 kernel: [    0.468719] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 27 03:51:01 node-1 kernel: [    0.468769] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 27 03:51:01 node-1 kernel: [    0.468794] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 27 03:51:01 node-1 kernel: [    0.469040] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 27 03:51:01 node-1 kernel: [    0.469046] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 27 03:51:01 node-1 kernel: [    0.469052] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 27 03:51:01 node-1 kernel: [    0.469057] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 27 03:51:01 node-1 kernel: [    0.469065] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 27 03:51:01 node-1 kernel: [    0.469095] pci 0000:01:00.0: supports D1 D2
Jul 27 03:51:01 node-1 kernel: [    0.475236] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 27 03:51:01 node-1 kernel: [    0.475239] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 27 03:51:01 node-1 kernel: [    0.475240] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 27 03:51:01 node-1 kernel: [    0.475346] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 27 03:51:01 node-1 kernel: [    0.475379] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 27 03:51:01 node-1 kernel: [    0.483241] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 27 03:51:01 node-1 kernel: [    0.483247] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:51:01 node-1 kernel: [    0.483251] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 03:51:01 node-1 kernel: [    0.483335] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 27 03:51:01 node-1 kernel: [    0.483417] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 27 03:51:01 node-1 kernel: [    0.483513] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 27 03:51:01 node-1 kernel: [    0.483559] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 27 03:51:01 node-1 kernel: [    0.483562] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:51:01 node-1 kernel: [    0.483564] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 03:51:01 node-1 kernel: [    0.483617] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 27 03:51:01 node-1 kernel: [    0.483739] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 27 03:51:01 node-1 kernel: [    0.483793] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 27 03:51:01 node-1 kernel: [    0.483795] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:51:01 node-1 kernel: [    0.483797] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 03:51:01 node-1 kernel: [    0.483846] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 27 03:51:01 node-1 kernel: [    0.483967] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 27 03:51:01 node-1 kernel: [    0.484009] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 27 03:51:01 node-1 kernel: [    0.484128] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 27 03:51:01 node-1 kernel: [    0.484167] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 27 03:51:01 node-1 kernel: [    0.484286] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 27 03:51:01 node-1 kernel: [    0.484343] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 27 03:51:01 node-1 kernel: [    0.484468] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 27 03:51:01 node-1 kernel: [    0.484512] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 27 03:51:01 node-1 kernel: [    0.484515] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:51:01 node-1 kernel: [    0.484517] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 03:51:01 node-1 kernel: [    0.484582] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 27 03:51:01 node-1 kernel: [    0.484647] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 27 03:51:01 node-1 kernel: [    0.484698] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 27 03:51:01 node-1 kernel: [    0.484738] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 27 03:51:01 node-1 kernel: [    0.484817] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 27 03:51:01 node-1 kernel: [    0.484929] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 27 03:51:01 node-1 kernel: [    0.484932] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:51:01 node-1 kernel: [    0.484934] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 27 03:51:01 node-1 kernel: [    0.484994] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 27 03:51:01 node-1 kernel: [    0.485050] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 27 03:51:01 node-1 kernel: [    0.485097] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 27 03:51:01 node-1 kernel: [    0.485339] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 27 03:51:01 node-1 kernel: [    0.485342] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 27 03:51:01 node-1 kernel: [    0.485407] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 27 03:51:01 node-1 kernel: [    0.485467] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 27 03:51:01 node-1 kernel: [    0.485516] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 27 03:51:01 node-1 kernel: [    0.485726] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 27 03:51:01 node-1 kernel: [    0.485730] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 27 03:51:01 node-1 kernel: [    0.485788] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 27 03:51:01 node-1 kernel: [    0.485848] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 27 03:51:01 node-1 kernel: [    0.485900] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 27 03:51:01 node-1 kernel: [    0.486130] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 27 03:51:01 node-1 kernel: [    0.486134] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 27 03:51:01 node-1 kernel: [    0.486309] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 27 03:51:01 node-1 kernel: [    0.486347] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 27 03:51:01 node-1 kernel: [    0.486421] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 27 03:51:01 node-1 kernel: [    0.486440] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 27 03:51:01 node-1 kernel: [    0.486453] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 27 03:51:01 node-1 kernel: [    0.486467] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 27 03:51:01 node-1 kernel: [    0.486516] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 27 03:51:01 node-1 kernel: [    0.491244] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 27 03:51:01 node-1 kernel: [    0.491249] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 27 03:51:01 node-1 kernel: [    0.491281] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 27 03:51:01 node-1 kernel: [    0.491769] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 27 03:51:01 node-1 kernel: [    0.491772] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 03:51:01 node-1 kernel: [    0.491896] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 27 03:51:01 node-1 kernel: [    0.492005] PCI host bridge to bus 0000:80
Jul 27 03:51:01 node-1 kernel: [    0.492007] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 27 03:51:01 node-1 kernel: [    0.492009] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 27 03:51:01 node-1 kernel: [    0.492010] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 27 03:51:01 node-1 kernel: [    0.492018] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.492082] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.492150] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 27 03:51:01 node-1 kernel: [    0.492213] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 27 03:51:01 node-1 kernel: [    0.492218] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 27 03:51:01 node-1 kernel: [    0.492291] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 27 03:51:01 node-1 kernel: [    0.492591] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 27 03:51:01 node-1 kernel: [    0.492622] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 27 03:51:01 node-1 kernel: [    0.492652] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 27 03:51:01 node-1 kernel: [    0.492681] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 27 03:51:01 node-1 kernel: [    0.492710] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 03:51:01 node-1 kernel: [    0.492740] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 03:51:01 node-1 kernel: [    0.492769] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 03:51:01 node-1 kernel: [    0.492798] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 03:51:01 node-1 kernel: [    0.492884] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 27 03:51:01 node-1 kernel: [    0.492888] ACPI: \_SB_.UNC1: notify handler is installed
Jul 27 03:51:01 node-1 kernel: [    0.492889] ACPI: \_SB_.UNC0: notify handler is installed
Jul 27 03:51:01 node-1 kernel: [    0.492904] ACPI: \_SB_.PCI0: notify handler is installed
Jul 27 03:51:01 node-1 kernel: [    0.492957] ACPI: \_SB_.PCI1: notify handler is installed
Jul 27 03:51:01 node-1 kernel: [    0.493036] Found 4 acpi root devices
Jul 27 03:51:01 node-1 kernel: [    0.493145] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 27 03:51:01 node-1 kernel: [    0.493147] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 27 03:51:01 node-1 kernel: [    0.493149] vgaarb: loaded
Jul 27 03:51:01 node-1 kernel: [    0.493150] vgaarb: bridge control possible 0000:0c:00.0
Jul 27 03:51:01 node-1 kernel: [    0.493269] SCSI subsystem initialized
Jul 27 03:51:01 node-1 kernel: [    0.493332] libata version 3.00 loaded.
Jul 27 03:51:01 node-1 kernel: [    0.493348] ACPI: bus type USB registered
Jul 27 03:51:01 node-1 kernel: [    0.493358] usbcore: registered new interface driver usbfs
Jul 27 03:51:01 node-1 kernel: [    0.493363] usbcore: registered new interface driver hub
Jul 27 03:51:01 node-1 kernel: [    0.493387] usbcore: registered new device driver usb
Jul 27 03:51:01 node-1 kernel: [    0.493552] PCI: Using ACPI for IRQ routing
Jul 27 03:51:01 node-1 kernel: [    0.497136] PCI: pci_cache_line_size set to 64 bytes
Jul 27 03:51:01 node-1 kernel: [    0.497362] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 27 03:51:01 node-1 kernel: [    0.497363] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 27 03:51:01 node-1 kernel: [    0.497364] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 27 03:51:01 node-1 kernel: [    0.497430] NetLabel: Initializing
Jul 27 03:51:01 node-1 kernel: [    0.497432] NetLabel:  domain hash size = 128
Jul 27 03:51:01 node-1 kernel: [    0.497432] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 27 03:51:01 node-1 kernel: [    0.497442] NetLabel:  unlabeled traffic allowed by default
Jul 27 03:51:01 node-1 kernel: [    0.497499] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 27 03:51:01 node-1 kernel: [    0.497503] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 27 03:51:01 node-1 kernel: [    0.499559] Switched to clocksource hpet
Jul 27 03:51:01 node-1 kernel: [    0.503555] AppArmor: AppArmor Filesystem Enabled
Jul 27 03:51:01 node-1 kernel: [    0.503570] pnp: PnP ACPI init
Jul 27 03:51:01 node-1 kernel: [    0.503576] ACPI: bus type PNP registered
Jul 27 03:51:01 node-1 kernel: [    0.503685] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 27 03:51:01 node-1 kernel: [    0.503693] pnp 00:01: [dma 4]
Jul 27 03:51:01 node-1 kernel: [    0.503705] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 27 03:51:01 node-1 kernel: [    0.503730] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 27 03:51:01 node-1 kernel: [    0.503749] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 27 03:51:01 node-1 kernel: [    0.503767] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 27 03:51:01 node-1 kernel: [    0.503799] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 27 03:51:01 node-1 kernel: [    0.503853] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 27 03:51:01 node-1 kernel: [    0.503855] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 27 03:51:01 node-1 kernel: [    0.503857] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 27 03:51:01 node-1 kernel: [    0.503858] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 27 03:51:01 node-1 kernel: [    0.503860] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 27 03:51:01 node-1 kernel: [    0.503864] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 27 03:51:01 node-1 kernel: [    0.503866] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 27 03:51:01 node-1 kernel: [    0.503867] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 27 03:51:01 node-1 kernel: [    0.503869] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 27 03:51:01 node-1 kernel: [    0.503870] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 27 03:51:01 node-1 kernel: [    0.503872] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 27 03:51:01 node-1 kernel: [    0.503873] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 27 03:51:01 node-1 kernel: [    0.503875] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 27 03:51:01 node-1 kernel: [    0.503877] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 27 03:51:01 node-1 kernel: [    0.503959] pnp 00:07: [dma 0 disabled]
Jul 27 03:51:01 node-1 kernel: [    0.503988] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 27 03:51:01 node-1 kernel: [    0.504062] pnp 00:08: [dma 0 disabled]
Jul 27 03:51:01 node-1 kernel: [    0.504093] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 27 03:51:01 node-1 kernel: [    0.504144] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 27 03:51:01 node-1 kernel: [    0.504488] pnp: PnP ACPI: found 10 devices
Jul 27 03:51:01 node-1 kernel: [    0.504490] ACPI: bus type PNP unregistered
Jul 27 03:51:01 node-1 kernel: [    0.510860] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 27 03:51:01 node-1 kernel: [    0.510863] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 27 03:51:01 node-1 kernel: [    0.510866] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 27 03:51:01 node-1 kernel: [    0.510870] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 27 03:51:01 node-1 kernel: [    0.510872] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:51:01 node-1 kernel: [    0.510886] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 27 03:51:01 node-1 kernel: [    0.510916] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 27 03:51:01 node-1 kernel: [    0.510930] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 27 03:51:01 node-1 kernel: [    0.510959] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 27 03:51:01 node-1 kernel: [    0.510973] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 27 03:51:01 node-1 kernel: [    0.511002] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 27 03:51:01 node-1 kernel: [    0.511016] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 27 03:51:01 node-1 kernel: [    0.511048] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 27 03:51:01 node-1 kernel: [    0.511050] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:51:01 node-1 kernel: [    0.511065] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 03:51:01 node-1 kernel: [    0.511094] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 27 03:51:01 node-1 kernel: [    0.511095] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:51:01 node-1 kernel: [    0.511110] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 03:51:01 node-1 kernel: [    0.511139] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 27 03:51:01 node-1 kernel: [    0.511141] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:51:01 node-1 kernel: [    0.511143] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 03:51:01 node-1 kernel: [    0.511148] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 27 03:51:01 node-1 kernel: [    0.511149] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:51:01 node-1 kernel: [    0.511152] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 03:51:01 node-1 kernel: [    0.511155] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 27 03:51:01 node-1 kernel: [    0.511160] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 27 03:51:01 node-1 kernel: [    0.511168] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 27 03:51:01 node-1 kernel: [    0.511171] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 27 03:51:01 node-1 kernel: [    0.511178] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 27 03:51:01 node-1 kernel: [    0.511178] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 27 03:51:01 node-1 kernel: [    0.511179] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 27 03:51:01 node-1 kernel: [    0.511180] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 27 03:51:01 node-1 kernel: [    0.511181] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 27 03:51:01 node-1 kernel: [    0.511182] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 27 03:51:01 node-1 kernel: [    0.511183] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 27 03:51:01 node-1 kernel: [    0.511184] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 27 03:51:01 node-1 kernel: [    0.511185] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 27 03:51:01 node-1 kernel: [    0.511186] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 27 03:51:01 node-1 kernel: [    0.511186] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 27 03:51:01 node-1 kernel: [    0.511187] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 27 03:51:01 node-1 kernel: [    0.511188] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 27 03:51:01 node-1 kernel: [    0.511189] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 27 03:51:01 node-1 kernel: [    0.511190] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 27 03:51:01 node-1 kernel: [    0.511191] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 27 03:51:01 node-1 kernel: [    0.511192] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 27 03:51:01 node-1 kernel: [    0.511193] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 27 03:51:01 node-1 kernel: [    0.511194] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 27 03:51:01 node-1 kernel: [    0.511195] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 27 03:51:01 node-1 kernel: [    0.511196] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 27 03:51:01 node-1 kernel: [    0.511197] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 27 03:51:01 node-1 kernel: [    0.511199] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 27 03:51:01 node-1 kernel: [    0.511199] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 27 03:51:01 node-1 kernel: [    0.511239] NET: Registered protocol family 2
Jul 27 03:51:01 node-1 kernel: [    0.511494] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 27 03:51:01 node-1 kernel: [    0.511827] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 27 03:51:01 node-1 kernel: [    0.511971] TCP: Hash tables configured (established 262144 bind 65536)
Jul 27 03:51:01 node-1 kernel: [    0.512013] TCP: reno registered
Jul 27 03:51:01 node-1 kernel: [    0.512040] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 27 03:51:01 node-1 kernel: [    0.512135] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 27 03:51:01 node-1 kernel: [    0.512281] NET: Registered protocol family 1
Jul 27 03:51:01 node-1 kernel: [    0.551654] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 27 03:51:01 node-1 kernel: [    0.551668] PCI: CLS 64 bytes, default 64
Jul 27 03:51:01 node-1 kernel: [    0.551727] Trying to unpack rootfs image as initramfs...
Jul 27 03:51:01 node-1 kernel: [    0.770830] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 27 03:51:01 node-1 kernel: [    0.770871] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 27 03:51:01 node-1 kernel: [    0.770873] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 27 03:51:01 node-1 kernel: [    0.771300] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:51:01 node-1 kernel: [    0.771306] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:51:01 node-1 kernel: [    0.771311] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:51:01 node-1 kernel: [    0.771317] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:51:01 node-1 kernel: [    0.771326] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:51:01 node-1 kernel: [    0.771341] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:51:01 node-1 kernel: [    0.771352] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:51:01 node-1 kernel: [    0.771361] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:51:01 node-1 kernel: [    0.771369] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:51:01 node-1 kernel: [    0.771379] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:51:01 node-1 kernel: [    0.771386] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:51:01 node-1 kernel: [    0.771392] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:51:01 node-1 kernel: [    0.771402] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:51:01 node-1 kernel: [    0.771424] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:51:01 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 27 03:51:01 node-1 kernel: [    0.771432] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:51:01 node-1 kernel: [    0.771439] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:51:01 node-1 kernel: [    0.771516] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 27 03:51:01 node-1 kernel: [    0.771519] Scanning for low memory corruption every 60 seconds
Jul 27 03:51:01 node-1 kernel: [    0.771897] Initialise system trusted keyring
Jul 27 03:51:01 node-1 kernel: [    0.771951] audit: initializing netlink socket (disabled)
Jul 27 03:51:01 node-1 kernel: [    0.771967] type=2000 audit(1469591423.724:1): initialized
Jul 27 03:51:01 node-1 kernel: [    0.789997] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 27 03:51:01 node-1 kernel: [    0.791531] zbud: loaded
Jul 27 03:51:01 node-1 kernel: [    0.791656] VFS: Disk quotas dquot_6.5.2
Jul 27 03:51:01 node-1 kernel: [    0.791693] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 27 03:51:01 node-1 kernel: [    0.792073] fuse init (API version 7.22)
Jul 27 03:51:01 node-1 kernel: [    0.792136] msgmni has been set to 32768
Jul 27 03:51:01 node-1 kernel: [    0.792186] Key type big_key registered
Jul 27 03:51:01 node-1 kernel: [    0.792694] Key type asymmetric registered
Jul 27 03:51:01 node-1 kernel: [    0.792696] Asymmetric key parser 'x509' registered
Jul 27 03:51:01 node-1 kernel: [    0.792718] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 27 03:51:01 node-1 kernel: [    0.792788] io scheduler noop registered
Jul 27 03:51:01 node-1 kernel: [    0.792790] io scheduler deadline registered (default)
Jul 27 03:51:01 node-1 kernel: [    0.792811] io scheduler cfq registered
Jul 27 03:51:01 node-1 kernel: [    0.793317] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    0.793512] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    0.793623] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    0.793757] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    0.793867] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    0.793985] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    0.794418] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 27 03:51:01 node-1 kernel: [    0.794457] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 27 03:51:01 node-1 kernel: [    0.794484] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 27 03:51:01 node-1 kernel: [    0.794503] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794508] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794514] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 27 03:51:01 node-1 kernel: [    0.794524] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794528] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794532] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794535] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794539] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794543] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794547] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794551] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794554] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794558] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794562] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794565] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794571] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 27 03:51:01 node-1 kernel: [    0.794581] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794587] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 27 03:51:01 node-1 kernel: [    0.794611] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794617] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 27 03:51:01 node-1 kernel: [    0.794636] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794640] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:51:01 node-1 kernel: [    0.794646] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 27 03:51:01 node-1 kernel: [    0.794705] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 27 03:51:01 node-1 kernel: [    0.794711] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 27 03:51:01 node-1 kernel: [    0.794715] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 27 03:51:01 node-1 kernel: [    0.794725] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 27 03:51:01 node-1 kernel: [    0.794765] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 27 03:51:01 node-1 kernel: [    0.794766] vesafb: scrolling: redraw
Jul 27 03:51:01 node-1 kernel: [    0.794768] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 27 03:51:01 node-1 kernel: [    0.815443] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 27 03:51:01 node-1 kernel: [    0.824005] Console: switching to colour frame buffer device 80x30
Jul 27 03:51:01 node-1 kernel: [    0.832685] fb0: VESA VGA frame buffer device
Jul 27 03:51:01 node-1 kernel: [    0.832883] intel_idle: MWAIT substates: 0x2120
Jul 27 03:51:01 node-1 kernel: [    0.832884] intel_idle: v0.4 model 0x3F
Jul 27 03:51:01 node-1 kernel: [    0.832884] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 27 03:51:01 node-1 kernel: [    0.833103] ipmi message handler version 39.2
Jul 27 03:51:01 node-1 kernel: [    0.833381] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 27 03:51:01 node-1 kernel: [    0.833819] ACPI: AC Adapter [P111] (on-line)
Jul 27 03:51:01 node-1 kernel: [    0.839064] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 27 03:51:01 node-1 kernel: [    0.850070] ACPI: Power Button [PWRB]
Jul 27 03:51:01 node-1 kernel: [    0.855838] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 27 03:51:01 node-1 kernel: [    0.867471] ACPI: Power Button [PWRF]
Jul 27 03:51:01 node-1 kernel: [    0.885094] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 27 03:51:01 node-1 kernel: [    0.896743] pstore: Registered erst as persistent store backend
Jul 27 03:51:01 node-1 kernel: [    0.902917] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 27 03:51:01 node-1 kernel: [    0.914844] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 27 03:51:01 node-1 kernel: [    0.941578] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 27 03:51:01 node-1 kernel: [    0.974847] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 27 03:51:01 node-1 kernel: [    0.988928] Linux agpgart interface v0.103
Jul 27 03:51:01 node-1 kernel: [    0.996565] brd: module loaded
Jul 27 03:51:01 node-1 kernel: [    1.003585] loop: module loaded
Jul 27 03:51:01 node-1 kernel: [    1.010294] libphy: Fixed MDIO Bus: probed
Jul 27 03:51:01 node-1 kernel: [    1.016767] tun: Universal TUN/TAP device driver, 1.6
Jul 27 03:51:01 node-1 kernel: [    1.023260] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 27 03:51:01 node-1 kernel: [    1.029781] PPP generic driver version 2.4.2
Jul 27 03:51:01 node-1 kernel: [    1.036179] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 27 03:51:01 node-1 kernel: [    1.042610] ehci-pci: EHCI PCI platform driver
Jul 27 03:51:01 node-1 kernel: [    1.049133] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 27 03:51:01 node-1 kernel: [    1.055554] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 27 03:51:01 node-1 kernel: [    1.068096] ehci-pci 0000:00:1a.0: debug port 2
Jul 27 03:51:01 node-1 kernel: [    1.078280] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 27 03:51:01 node-1 kernel: [    1.078298] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 27 03:51:01 node-1 kernel: [    1.095058] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 27 03:51:01 node-1 kernel: [    1.101191] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 27 03:51:01 node-1 kernel: [    1.107427] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 27 03:51:01 node-1 kernel: [    1.119454] usb usb1: Product: EHCI Host Controller
Jul 27 03:51:01 node-1 kernel: [    1.125536] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 27 03:51:01 node-1 kernel: [    1.131652] usb usb1: SerialNumber: 0000:00:1a.0
Jul 27 03:51:01 node-1 kernel: [    1.137667] hub 1-0:1.0: USB hub found
Jul 27 03:51:01 node-1 kernel: [    1.143500] hub 1-0:1.0: 2 ports detected
Jul 27 03:51:01 node-1 kernel: [    1.149358] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 27 03:51:01 node-1 kernel: [    1.154995] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 27 03:51:01 node-1 kernel: [    1.166002] ehci-pci 0000:00:1d.0: debug port 2
Jul 27 03:51:01 node-1 kernel: [    1.175359] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 27 03:51:01 node-1 kernel: [    1.175362] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 27 03:51:01 node-1 kernel: [    1.190976] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 27 03:51:01 node-1 kernel: [    1.196247] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 27 03:51:01 node-1 kernel: [    1.201640] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 27 03:51:01 node-1 kernel: [    1.212405] usb usb2: Product: EHCI Host Controller
Jul 27 03:51:01 node-1 kernel: [    1.217958] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 27 03:51:01 node-1 kernel: [    1.223566] usb usb2: SerialNumber: 0000:00:1d.0
Jul 27 03:51:01 node-1 kernel: [    1.229139] hub 2-0:1.0: USB hub found
Jul 27 03:51:01 node-1 kernel: [    1.234554] hub 2-0:1.0: 2 ports detected
Jul 27 03:51:01 node-1 kernel: [    1.239921] ehci-platform: EHCI generic platform driver
Jul 27 03:51:01 node-1 kernel: [    1.245199] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 27 03:51:01 node-1 kernel: [    1.250583] ohci-pci: OHCI PCI platform driver
Jul 27 03:51:01 node-1 kernel: [    1.255938] ohci-platform: OHCI generic platform driver
Jul 27 03:51:01 node-1 kernel: [    1.261187] uhci_hcd: USB Universal Host Controller Interface driver
Jul 27 03:51:01 node-1 kernel: [    1.266589] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 27 03:51:01 node-1 kernel: [    1.466739] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 27 03:51:01 node-1 kernel: [    1.766498] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 27 03:51:01 node-1 kernel: [    1.782823] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 27 03:51:01 node-1 kernel: [    1.788464] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 27 03:51:01 node-1 kernel: [    1.794216] hub 1-1:1.0: USB hub found
Jul 27 03:51:01 node-1 kernel: [    1.799809] hub 1-1:1.0: 6 ports detected
Jul 27 03:51:01 node-1 kernel: [    1.918383] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 27 03:51:01 node-1 kernel: [    2.305255] i8042: No controller found
Jul 27 03:51:01 node-1 kernel: [    2.310789] mousedev: PS/2 mouse device common for all mice
Jul 27 03:51:01 node-1 kernel: [    2.316517] rtc_cmos 00:02: RTC can wake from S4
Jul 27 03:51:01 node-1 kernel: [    2.318811] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 27 03:51:01 node-1 kernel: [    2.318812] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 27 03:51:01 node-1 kernel: [    2.319443] hub 2-1:1.0: USB hub found
Jul 27 03:51:01 node-1 kernel: [    2.319687] hub 2-1:1.0: 8 ports detected
Jul 27 03:51:01 node-1 kernel: [    2.344735] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 27 03:51:01 node-1 kernel: [    2.350481] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 27 03:51:01 node-1 kernel: [    2.361784] device-mapper: uevent: version 1.0.3
Jul 27 03:51:01 node-1 kernel: [    2.367478] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 27 03:51:01 node-1 kernel: [    2.378837] ledtrig-cpu: registered to indicate activity on CPUs
Jul 27 03:51:01 node-1 kernel: [    2.384801] TCP: cubic registered
Jul 27 03:51:01 node-1 kernel: [    2.390661] NET: Registered protocol family 10
Jul 27 03:51:01 node-1 kernel: [    2.396683] NET: Registered protocol family 17
Jul 27 03:51:01 node-1 kernel: [    2.402446] Key type dns_resolver registered
Jul 27 03:51:01 node-1 kernel: [    2.408504] Loading compiled-in X.509 certificates
Jul 27 03:51:01 node-1 kernel: [    2.414706] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 27 03:51:01 node-1 kernel: [    2.426294] registered taskstats version 1
Jul 27 03:51:01 node-1 kernel: [    2.434388] Key type trusted registered
Jul 27 03:51:01 node-1 kernel: [    2.441997] Key type encrypted registered
Jul 27 03:51:01 node-1 kernel: [    2.447497] AppArmor: AppArmor sha1 policy hashing enabled
Jul 27 03:51:01 node-1 kernel: [    2.453005] IMA: No TPM chip found, activating TPM-bypass!
Jul 27 03:51:01 node-1 kernel: [    2.459079] regulator-dummy: disabling
Jul 27 03:51:01 node-1 kernel: [    2.464598]   Magic number: 8:139:817
Jul 27 03:51:01 node-1 kernel: [    2.470050]   hash matches /build/linux-ZqOzIB/linux-3.13.0/drivers/base/power/main.c:504
Jul 27 03:51:01 node-1 kernel: [    2.481166] acpi device:a6: hash matches
Jul 27 03:51:01 node-1 kernel: [    2.486866] rtc_cmos 00:02: setting system clock to 2016-07-27 03:50:25 UTC (1469591425)
Jul 27 03:51:01 node-1 kernel: [    2.499498] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 27 03:51:01 node-1 kernel: [    2.505244] EDD information not available.
Jul 27 03:51:01 node-1 kernel: [    2.510953] PM: Hibernation image not present or could not be loaded.
Jul 27 03:51:01 node-1 kernel: [    2.511814] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 27 03:51:01 node-1 kernel: [    2.523504] Write protecting the kernel read-only data: 12288k
Jul 27 03:51:01 node-1 kernel: [    2.529969] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 27 03:51:01 node-1 kernel: [    2.542932] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 27 03:51:01 node-1 kernel: [    2.575562] device-mapper: multipath: version 1.6.0 loaded
Jul 27 03:51:01 node-1 kernel: [    2.583435] systemd-udevd[216]: starting version 204
Jul 27 03:51:01 node-1 kernel: [    2.597815] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 27 03:51:01 node-1 kernel: [    2.606113] md: linear personality registered for level -1
Jul 27 03:51:01 node-1 kernel: [    2.621395] md: multipath personality registered for level -4
Jul 27 03:51:01 node-1 kernel: [    2.629501] md: raid0 personality registered for level 0
Jul 27 03:51:01 node-1 kernel: [    2.638147] md: raid1 personality registered for level 1
Jul 27 03:51:01 node-1 kernel: [    2.648415] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 27 03:51:01 node-1 kernel: [    2.654830] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 27 03:51:01 node-1 kernel: [    2.655043] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 27 03:51:01 node-1 kernel: [    2.667956] megasas: FW now in Ready state
Jul 27 03:51:01 node-1 kernel: [    2.668438] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 27 03:51:01 node-1 kernel: [    2.668453] 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 27 03:51:01 node-1 kernel: [    2.668495] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 03:51:01 node-1 kernel: [    2.669139] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.669235] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.669343] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.669464] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.669901] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.688427] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 27 03:51:01 node-1 kernel: [    2.688466] 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 27 03:51:01 node-1 kernel: [    2.688502] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 03:51:01 node-1 kernel: [    2.688809] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.688923] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.689065] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.689265] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.689624] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.706624] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 27 03:51:01 node-1 kernel: [    2.706625] 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 27 03:51:01 node-1 kernel: [    2.706628] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 03:51:01 node-1 kernel: [    2.707071] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.707237] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.707379] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.707475] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.707903] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.713747] raid6: sse2x1   11264 MB/s
Jul 27 03:51:01 node-1 kernel: [    2.723113] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 27 03:51:01 node-1 kernel: [    2.723115] 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 27 03:51:01 node-1 kernel: [    2.723116] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 03:51:01 node-1 kernel: [    2.723644] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.723783] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.723897] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.724098] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.724447] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 03:51:01 node-1 kernel: [    2.742584] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 27 03:51:01 node-1 kernel: [    2.742585] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 27 03:51:01 node-1 kernel: [    2.742599] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 27 03:51:01 node-1 kernel: [    2.742609] usb 2-1.4: Manufacturer: Avocent
Jul 27 03:51:01 node-1 kernel: [    2.742609] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 27 03:51:01 node-1 kernel: [    2.781818] raid6: sse2x2   13217 MB/s
Jul 27 03:51:01 node-1 kernel: [    2.849843] raid6: sse2x4    9618 MB/s
Jul 27 03:51:01 node-1 kernel: [    2.917693] raid6: avx2x1   14077 MB/s
Jul 27 03:51:01 node-1 kernel: [    2.985474] raid6: avx2x2   18766 MB/s
Jul 27 03:51:01 node-1 kernel: [    3.057410] raid6: avx2x4   21178 MB/s
Jul 27 03:51:01 node-1 kernel: [    3.063133] raid6: using algorithm avx2x4 (21178 MB/s)
Jul 27 03:51:01 node-1 kernel: [    3.068816] raid6: using avx2x2 recovery algorithm
Jul 27 03:51:01 node-1 kernel: [    3.074564] Switched to clocksource tsc
Jul 27 03:51:01 node-1 kernel: [    3.074622] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    3.074661] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    3.074702] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    3.074728] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    3.074765] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    3.074791] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    3.074830] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    3.074865] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    3.074899] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    3.074936] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    3.074971] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    3.075006] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    3.075044] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    3.075079] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    3.075117] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    3.075133] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Jul 27 03:51:01 node-1 kernel: [    3.075293] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 27 03:51:01 node-1 kernel: [    3.092212] xor: automatically using best checksumming function:
Jul 27 03:51:01 node-1 kernel: [    3.097880] hidraw: raw HID events driver (C) Jiri Kosina
Jul 27 03:51:01 node-1 kernel: [    3.106496] usbcore: registered new interface driver usbhid
Jul 27 03:51:01 node-1 kernel: [    3.111933] usbhid: USB HID core driver
Jul 27 03:51:01 node-1 kernel: [    3.118333] 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 27 03:51:01 node-1 kernel: [    3.129689] 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 27 03:51:01 node-1 kernel: [    3.137346]    avx       : 35882.000 MB/sec
Jul 27 03:51:01 node-1 kernel: [    3.147011] 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 27 03:51:01 node-1 kernel: [    3.158557] async_tx: api initialized (async)
Jul 27 03:51:01 node-1 kernel: [    3.159092] 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 27 03:51:01 node-1 kernel: [    3.160296] 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 27 03:51:01 node-1 kernel: [    3.161010] 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 27 03:51:01 node-1 kernel: [    3.204611] md: raid6 personality registered for level 6
Jul 27 03:51:01 node-1 kernel: [    3.211012] md: raid5 personality registered for level 5
Jul 27 03:51:01 node-1 kernel: [    3.217262] md: raid4 personality registered for level 4
Jul 27 03:51:01 node-1 kernel: [    3.226471] md: raid10 personality registered for level 10
Jul 27 03:51:01 node-1 kernel: [    3.282186] multipathd (354): /proc/354/oom_adj is deprecated, please use /proc/354/oom_score_adj instead.
Jul 27 03:51:01 node-1 kernel: [    3.461102] megasas:IOC Init cmd success
Jul 27 03:51:01 node-1 kernel: [    3.513069] megasas: INIT adapter done
Jul 27 03:51:01 node-1 kernel: [    3.612966] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 27 03:51:01 node-1 kernel: [    3.619889] scsi0 : LSI SAS based MegaRAID driver
Jul 27 03:51:01 node-1 kernel: [    3.627278] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 27 03:51:01 node-1 kernel: [    3.646458] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 27 03:51:01 node-1 kernel: [    3.661833] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 27 03:51:01 node-1 kernel: [    3.668402] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 27 03:51:01 node-1 kernel: [    3.681366] sd 0:2:0:0: [sda] Write Protect is off
Jul 27 03:51:01 node-1 kernel: [    3.687752] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 27 03:51:01 node-1 kernel: [    3.687774] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 27 03:51:01 node-1 kernel: [    3.728272]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 27 03:51:01 node-1 kernel: [    3.734889] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 27 03:51:01 node-1 kernel: [    3.854105] random: lvm urandom read with 26 bits of entropy available
Jul 27 03:51:01 node-1 kernel: [    3.980852] bio: create slab <bio-1> at 1
Jul 27 03:51:01 node-1 kernel: [    4.875100] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 03:51:01 node-1 kernel: [    5.531221] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 27 03:51:01 node-1 kernel: [    5.555957] random: nonblocking pool is initialized
Jul 27 03:51:01 node-1 kernel: [    5.576651] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 27 03:51:01 node-1 kernel: [    5.683084] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 27 03:51:01 node-1 kernel: [    5.742954] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 27 03:51:01 node-1 kernel: [    5.818538] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 03:51:01 node-1 kernel: [    6.056570] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 27 03:51:01 node-1 kernel: [    6.089096] XFS (dm-1): Mounting Filesystem
Jul 27 03:51:01 node-1 kernel: [    6.305098] XFS (dm-1): Ending clean mount
Jul 27 03:51:01 node-1 kernel: [    6.363700] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 03:51:01 node-1 kernel: [    6.422622] XFS (dm-2): Mounting Filesystem
Jul 27 03:51:01 node-1 kernel: [    6.502906] XFS (dm-2): Ending clean mount
Jul 27 03:51:01 node-1 kernel: [    6.672284] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 03:51:01 node-1 kernel: [    8.430189] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 27 03:51:01 node-1 kernel: [    8.458710] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 27 03:51:01 node-1 kernel: [    8.611811] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 27 03:51:01 node-1 kernel: [    8.611816] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 27 03:51:01 node-1 kernel: [    8.611820] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 27 03:51:01 node-1 kernel: [    8.611823] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 27 03:51:01 node-1 kernel: [    8.651113] systemd-udevd[804]: starting version 204
Jul 27 03:51:01 node-1 kernel: [    8.948476] power_meter ACPI000D:00: Found ACPI power meter.
Jul 27 03:51:01 node-1 kernel: [    8.948499] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 27 03:51:01 node-1 kernel: [    8.955347] IPMI System Interface driver.
Jul 27 03:51:01 node-1 kernel: [    8.955429] ipmi_si: probing via ACPI
Jul 27 03:51:01 node-1 kernel: [    8.955443] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 27 03:51:01 node-1 kernel: [    8.955444] ipmi_si: Adding ACPI-specified kcs state machine
Jul 27 03:51:01 node-1 kernel: [    8.955460] ipmi_si: probing via SMBIOS
Jul 27 03:51:01 node-1 kernel: [    8.955462] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 27 03:51:01 node-1 kernel: [    8.955463] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 27 03:51:01 node-1 kernel: [    8.955464] ipmi_si: probing via SPMI
Jul 27 03:51:01 node-1 kernel: [    8.955466] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 27 03:51:01 node-1 kernel: [    8.955467] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 27 03:51:01 node-1 kernel: [    8.955468] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 27 03:51:01 node-1 kernel: [    8.956748] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 27 03:51:01 node-1 kernel: [    8.959721] wmi: Mapper loaded
Jul 27 03:51:01 node-1 kernel: [    8.968563] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 27 03:51:01 node-1 kernel: [    8.968568] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 27 03:51:01 node-1 kernel: [    8.968571] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 27 03:51:01 node-1 kernel: [    8.968573] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 27 03:51:01 node-1 kernel: [    8.968584] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 27 03:51:01 node-1 kernel: [    9.032871] systemd-udevd[825]: renamed network interface eth0 to enp6s0
Jul 27 03:51:01 node-1 kernel: [    9.056718] systemd-udevd[859]: renamed network interface eth1 to enp7s0
Jul 27 03:51:01 node-1 kernel: [    9.080702] systemd-udevd[822]: renamed network interface eth2 to enp8s0
Jul 27 03:51:01 node-1 kernel: [    9.093010] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 27 03:51:01 node-1 kernel: [    9.093019] ipmi_si 00:09: IPMI kcs interface initialized
Jul 27 03:51:01 node-1 kernel: [    9.108765] systemd-udevd[821]: renamed network interface eth3 to enp9s0
Jul 27 03:51:01 node-1 kernel: [    9.405653] type=1400 audit(1469591432.419:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1080 comm="apparmor_parser"
Jul 27 03:51:01 node-1 kernel: [    9.405807] type=1400 audit(1469591432.419:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1080 comm="apparmor_parser"
Jul 27 03:51:01 node-1 kernel: [    9.405938] type=1400 audit(1469591432.419:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1080 comm="apparmor_parser"
Jul 27 03:51:01 node-1 kernel: [    9.410522] type=1400 audit(1469591432.423:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1079 comm="apparmor_parser"
Jul 27 03:51:01 node-1 kernel: [    9.410664] type=1400 audit(1469591432.423:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1079 comm="apparmor_parser"
Jul 27 03:51:01 node-1 kernel: [    9.410790] type=1400 audit(1469591432.423:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1079 comm="apparmor_parser"
Jul 27 03:51:01 node-1 kernel: [    9.419691] type=1400 audit(1469591432.431:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1075 comm="apparmor_parser"
Jul 27 03:51:01 node-1 kernel: [    9.419829] type=1400 audit(1469591432.431:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1075 comm="apparmor_parser"
Jul 27 03:51:01 node-1 kernel: [    9.419953] type=1400 audit(1469591432.431:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1075 comm="apparmor_parser"
Jul 27 03:51:01 node-1 kernel: [    9.426837] type=1400 audit(1469591432.439:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1083 comm="apparmor_parser"
Jul 27 03:51:01 node-1 kernel: [   10.038943] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 27 03:51:01 node-1 kernel: [   10.054436] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 27 03:51:01 node-1 kernel: [   10.331982] enic 0000:06:00.0 enp6s0: Link UP
Jul 27 03:51:01 node-1 kernel: [   10.333240] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 27 03:51:01 node-1 kernel: [   10.333250] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 27 03:51:01 node-1 kernel: [   20.617710] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 27 03:51:02 node-1 failsafe: Failsafe of 120 seconds reached.
Jul 27 03:51:02 node-1 kernel: [   39.423903] init: failsafe main process (8430) killed by TERM signal
Jul 27 03:51:03 node-1 dbus[8497]: [system] AppArmor D-Bus mediation is enabled
Jul 27 03:51:03 node-1 kernel: [   39.596475] audit_printk_skb: 30 callbacks suppressed
Jul 27 03:51:03 node-1 kernel: [   39.596477] type=1400 audit(1469591463.164:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8548 comm="apparmor_parser"
Jul 27 03:51:03 node-1 kernel: [   39.596741] type=1400 audit(1469591463.164:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8547 comm="apparmor_parser"
Jul 27 03:51:03 node-1 kernel: [   39.596746] type=1400 audit(1469591463.164:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8547 comm="apparmor_parser"
Jul 27 03:51:03 node-1 kernel: [   39.596750] type=1400 audit(1469591463.164:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8547 comm="apparmor_parser"
Jul 27 03:51:03 node-1 kernel: [   39.596983] type=1400 audit(1469591463.164:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8547 comm="apparmor_parser"
Jul 27 03:51:03 node-1 kernel: [   39.596986] type=1400 audit(1469591463.164:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8547 comm="apparmor_parser"
Jul 27 03:51:03 node-1 kernel: [   39.597102] type=1400 audit(1469591463.164:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8547 comm="apparmor_parser"
Jul 27 03:51:03 node-1 kernel: [   39.682644] type=1400 audit(1469591463.252:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8550 comm="apparmor_parser"
Jul 27 03:51:03 node-1 cron[8588]: (CRON) INFO (pidfile fd = 3)
Jul 27 03:51:03 node-1 anacron[8625]: Anacron 2.3 started on 2016-07-27
Jul 27 03:51:03 node-1 cron[8627]: (CRON) STARTUP (fork ok)
Jul 27 03:51:03 node-1 anacron[8625]: Will run job `cron.daily' in 5 min.
Jul 27 03:51:03 node-1 anacron[8625]: Will run job `cron.weekly' in 10 min.
Jul 27 03:51:03 node-1 anacron[8625]: Will run job `cron.monthly' in 15 min.
Jul 27 03:51:03 node-1 anacron[8625]: Jobs will be executed sequentially
Jul 27 03:51:03 node-1 multipathd: path checkers start up
Jul 27 03:51:03 node-1 cron[8627]: (CRON) INFO (Running @reboot jobs)
Jul 27 03:51:03 node-1 postfix/master[8767]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 27 03:51:07 node-1 puppet-agent[9067]: Reopening log files
Jul 27 03:51:08 node-1 puppet-agent[9067]: Could not request certificate: Connection refused - connect(2)
Jul 27 03:51:17 node-1 puppet-user[9160]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 27 03:51:17 node-1 puppet-user[9160]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 27 03:51:18 node-1 puppet-user[9160]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 27 03:51:18 node-1 puppet-user[9160]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 27 03:51:18 node-1 puppet-user[9160]: Finished catalog run in 0.95 seconds
Jul 27 03:51:19 node-1 multipathd: uevent trigger error
Jul 27 03:51:20 node-1 puppet-user[9590]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 27 03:51:20 node-1 puppet-user[9590]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Jul 27 03:51:20 node-1 puppet-user[9590]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 27 03:51:20 node-1 puppet-user[9590]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 27 03:51:20 node-1 puppet-user[9590]: (/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 27 03:51:20 node-1 puppet-user[9590]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 27 03:51:20 node-1 puppet-user[9590]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 27 03:51:20 node-1 puppet-user[9590]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 27 03:51:20 node-1 puppet-user[9590]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 27 03:51:20 node-1 puppet-user[9590]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 27 03:51:20 node-1 puppet-user[9590]: Finished catalog run in 0.07 seconds
Jul 27 03:51:21 node-1 puppet-user[10235]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 27 03:51:21 node-1 puppet-user[10235]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Jul 27 03:51:21 node-1 puppet-user[10235]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 27 03:51:21 node-1 puppet-user[10235]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 27 03:51:21 node-1 puppet-user[10235]: Finished catalog run in 0.03 seconds
Jul 27 03:51:23 node-1 puppet-user[10700]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 27 03:51:23 node-1 puppet-user[10700]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 27 03:51:23 node-1 puppet-user[10700]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 27 03:51:23 node-1 puppet-user[10700]: Finished catalog run in 0.04 seconds
Jul 27 03:51:24 node-1 puppet-user[11154]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 27 03:51:25 node-1 puppet-user[11154]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Jul 27 03:51:25 node-1 puppet-user[11154]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 27 03:51:25 node-1 puppet-user[11154]: (/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 27 03:51:25 node-1 puppet-user[11154]: Finished catalog run in 0.42 seconds
Jul 27 03:51:26 node-1 puppet-user[11630]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 27 03:51:27 node-1 puppet-user[11630]: Compiled catalog for node-1.domain.tld in environment production in 0.21 seconds
Jul 27 03:51:27 node-1 puppet-user[11630]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 27 03:51:27 node-1 puppet-user[11630]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 27 03:51:27 node-1 puppet-user[11630]: (/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 27 03:51:27 node-1 puppet-user[11630]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 27 03:51:27 node-1 puppet-user[11630]: Finished catalog run in 0.22 seconds
Jul 27 03:51:28 node-1 puppet-user[12110]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 27 03:51:28 node-1 puppet-user[12110]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Jul 27 03:51:29 node-1 puppet-user[12110]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 27 03:51:29 node-1 kernel: [   65.548888] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 27 03:51:29 node-1 kernel: [   65.548935] 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 27 03:51:29 node-1 puppet-user[12110]: (/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 27 03:51:29 node-1 puppet-user[12110]: Finished catalog run in 0.05 seconds
Jul 27 03:51:30 node-1 puppet-user[12569]: (Scope(Class[main])) MODULAR: sync_time
Jul 27 03:51:30 node-1 puppet-user[12569]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Jul 27 03:51:30 node-1 ntpdate[12987]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 27 03:51:32 node-1 kernel: [   68.859240] init: plymouth-upstart-bridge main process ended, respawning
Jul 27 03:51:32 node-1 puppet-agent[9067]: Could not run: SIGTERM
Jul 27 03:51:32 node-1 kernel: [   69.141625] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 27 03:51:32 node-1 ec2: 
Jul 27 03:51:32 node-1 ec2: #############################################################
Jul 27 03:51:32 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 27 03:51:32 node-1 ec2: 1024 d9:69:ba:c4:1b:e6:3b:5f:38:55:44:c7:18:27:68:7e  root@node-1.domain.tld (DSA)
Jul 27 03:51:32 node-1 ec2: 256 17:15:76:65:fd:c7:26:94:ea:57:a5:f2:07:97:9d:f6  root@node-1.domain.tld (ECDSA)
Jul 27 03:51:32 node-1 ec2: 256 97:3b:33:fa:3d:be:f8:3f:c0:d0:c1:40:34:77:8a:aa  root@node-1.domain.tld (ED25519)
Jul 27 03:51:32 node-1 ec2: 2048 d9:18:92:9e:94:29:67:8c:46:1c:d2:91:67:b6:bb:98  root@node-1.domain.tld (RSA)
Jul 27 03:51:32 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 27 03:51:32 node-1 ec2: #############################################################
Jul 27 03:51:37 node-1 ntpdate[12987]: adjust time server 10.20.0.2 offset 0.002879 sec
Jul 27 03:51:37 node-1 puppet-user[12569]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 27 03:51:37 node-1 puppet-user[12569]: Finished catalog run in 6.17 seconds
Jul 27 03:51:42 node-1 puppet-user[13349]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 27 03:51:42 node-1 puppet-user[13349]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Jul 27 03:51:42 node-1 puppet-user[13349]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 27 03:51:42 node-1 puppet-user[13349]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Jul 27 03:51:42 node-1 puppet-user[13349]: Finished catalog run in 0.06 seconds
Jul 27 03:51:44 node-1 puppet-user[13809]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 27 03:51:45 node-1 puppet-user[13809]: Compiled catalog for node-1.domain.tld in environment production in 1.26 seconds
Jul 27 03:51:45 node-1 puppet-user[13809]: (/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 27 03:51:45 node-1 puppet-user[13809]: (/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 27 03:51:45 node-1 puppet-user[13809]: (/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 27 03:51:45 node-1 puppet-user[13809]: (/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 27 03:51:45 node-1 puppet-user[13809]: (/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 27 03:51:45 node-1 puppet-user[13809]: (/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 27 03:51:45 node-1 puppet-user[13809]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 27 03:51:45 node-1 puppet-user[13809]: (/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 27 03:51:45 node-1 puppet-user[13809]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 27 03:51:45 node-1 puppet-user[13809]: (/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 27 03:51:45 node-1 puppet-user[13809]: (/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 27 03:51:45 node-1 puppet-user[13809]: (/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 27 03:51:45 node-1 puppet-user[13809]: (/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 27 03:51:45 node-1 puppet-user[13809]: (/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 27 03:51:45 node-1 puppet-user[13809]: (/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 27 03:51:45 node-1 puppet-user[13809]: (/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 27 03:51:55 node-1 puppet-user[13809]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 27 03:51:55 node-1 puppet-user[13809]: Finished catalog run in 9.91 seconds
Jul 27 03:51:56 node-1 puppet-user[14678]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 27 03:51:57 node-1 puppet-user[14678]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Jul 27 03:52:01 node-1 puppet-user[14678]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 27 03:52:01 node-1 CRON[15675]: (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 27 03:52:25 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 03:52:25 node-1 nailgun-agent: I, [2016-07-27T03:52:25.695662 #15678]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 27 03:52:33 node-1 puppet-user[14678]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 27 03:52:33 node-1 puppet-user[14678]: Finished catalog run in 35.99 seconds
Jul 27 03:52:34 node-1 puppet-user[17342]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 27 03:52:35 node-1 puppet-user[17342]: Compiled catalog for node-1.domain.tld in environment production in 0.52 seconds
Jul 27 03:52:35 node-1 puppet-user[17342]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 27 03:52:35 node-1 puppet-user[17342]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 27 03:52:35 node-1 puppet-user[17342]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 27 03:52:35 node-1 puppet-user[17342]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 27 03:52:35 node-1 puppet-user[17342]: Finished catalog run in 0.09 seconds
Jul 27 03:52:37 node-1 puppet-user[17810]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 27 03:52:38 node-1 puppet-user[17810]: Compiled catalog for node-1.domain.tld in environment production in 0.82 seconds
Jul 27 03:52:38 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 27 03:52:38 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 27 03:52:38 node-1 crontab[18421]: (root) LIST (root)
Jul 27 03:52:38 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 27 03:52:38 node-1 crontab[18424]: (root) REPLACE (root)
Jul 27 03:52:38 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 03:52:38 node-1 nailgun-agent: I, [2016-07-27T03:52:38.784862 #15678]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Jul 27 03:52:40 node-1 puppet-user[17810]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 27 03:52:42 node-1 puppet-user[17810]: (/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 27 03:52:42 node-1 puppet-user[17810]: (/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 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 27 03:52:42 node-1 puppet-user[17810]: (/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 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 27 03:52:42 node-1 puppet-user[17810]: (/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 27 03:52:42 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 27 03:52:43 node-1 puppet-user[17810]: (/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 27 03:52:43 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 27 03:52:43 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 27 03:52:43 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 27 03:52:43 node-1 puppet-user[17810]: (/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 27 03:52:43 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 27 03:52:43 node-1 puppet-user[17810]: (/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 27 03:52:43 node-1 puppet-user[17810]: (/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 27 03:52:43 node-1 puppet-user[17810]: (/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 27 03:52:43 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 27 03:52:43 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 27 03:52:43 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 27 03:52:43 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 27 03:52:43 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 27 03:52:43 node-1 puppet-user[17810]: (/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 27 03:52:43 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 27 03:52:43 node-1 puppet-user[17810]: (/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 27 03:52:43 node-1 puppet-user[17810]: (/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 27 03:52:43 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 27 03:52:43 node-1 puppet-user[17810]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 27 03:52:43 node-1 puppet-user[17810]: (/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 27 03:52:43 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8403" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:43 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 27 03:52:45 node-1 multipathd: uevent trigger error
<27>Jul 27 03:52:45 node-1 multipathd: uevent trigger error
<27>Jul 27 03:52:45 node-1 multipathd: uevent trigger error
<27>Jul 27 03:52:45 node-1 multipathd: uevent trigger error
<27>Jul 27 03:53:04 node-1 multipathd: uevent trigger error
<27>Jul 27 03:53:04 node-1 multipathd: uevent trigger error
<27>Jul 27 03:53:04 node-1 multipathd: uevent trigger error
<27>Jul 27 03:53:04 node-1 multipathd: uevent trigger error
<27>Jul 27 03:53:04 node-1 multipathd: uevent trigger error
<27>Jul 27 03:53:04 node-1 multipathd: uevent trigger error
<27>Jul 27 03:53:08 node-1 multipathd: uevent trigger error
<27>Jul 27 03:53:08 node-1 multipathd: uevent trigger error
<27>Jul 27 03:53:08 node-1 multipathd: uevent trigger error
<27>Jul 27 03:53:08 node-1 multipathd: uevent trigger error
<27>Jul 27 03:53:08 node-1 multipathd: uevent trigger error
<27>Jul 27 03:53:08 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:08 node-1 ntpdate[29381]: no servers can be used, exiting
<27>Jul 27 03:54:08 node-1 ntpdate[29628]: no servers can be used, exiting
<27>Jul 27 03:54:40 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:40 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:40 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:40 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:40 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:40 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:44 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:44 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:44 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:44 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:44 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:56 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:56 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:56 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:56 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:59 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:59 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:59 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:59 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:59 node-1 multipathd: uevent trigger error
<27>Jul 27 03:54:59 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:00 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:00 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:00 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:00 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:00 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:09 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:09 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:09 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:09 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:09 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:09 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:12 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 03:56:12 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 03:56:18 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 03:56:18 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 03:56:23 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 03:56:29 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 03:56:29 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 27 03:56:36 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:36 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:36 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:36 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:36 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:49 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:49 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:49 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:49 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:49 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:54 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:54 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:54 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:54 node-1 multipathd: uevent trigger error
<27>Jul 27 03:56:54 node-1 multipathd: uevent trigger error
<129>Jul 27 03:56:57 node-1 haproxy[18216]: 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 27 03:56:57 node-1 haproxy[18216]: 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 27 03:56:58 node-1 haproxy[18222]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:56:58 node-1 haproxy[18222]: proxy mysqld has no server available!
<27>Jul 27 03:57:00 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:00 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:00 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:00 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:00 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:00 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:03 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:03 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:03 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:03 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:03 node-1 multipathd: uevent trigger error
<129>Jul 27 03:57:06 node-1 haproxy[20807]: 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 27 03:57:06 node-1 haproxy[20807]: 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 27 03:57:06 node-1 haproxy[20807]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:06 node-1 haproxy[20807]: proxy mysqld has no server available!
<129>Jul 27 03:57:07 node-1 haproxy[20811]: 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 27 03:57:07 node-1 haproxy[20811]: 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 27 03:57:07 node-1 haproxy[20811]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:07 node-1 haproxy[20811]: proxy object-storage has no server available!
<27>Jul 27 03:57:09 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:09 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:09 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:09 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:09 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:09 node-1 multipathd: uevent trigger error
<129>Jul 27 03:57:11 node-1 haproxy[22237]: 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 27 03:57:11 node-1 haproxy[22237]: 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 27 03:57:12 node-1 haproxy[22241]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:12 node-1 haproxy[22241]: proxy neutron has no server available!
<129>Jul 27 03:57:12 node-1 haproxy[22241]: 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 27 03:57:12 node-1 haproxy[22241]: 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 27 03:57:12 node-1 haproxy[22241]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:12 node-1 haproxy[22241]: proxy mysqld has no server available!
<129>Jul 27 03:57:12 node-1 haproxy[22241]: 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 27 03:57:13 node-1 haproxy[22241]: 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 27 03:57:13 node-1 haproxy[22241]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:13 node-1 haproxy[22241]: proxy object-storage has no server available!
<27>Jul 27 03:57:14 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:14 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:14 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:14 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:14 node-1 multipathd: uevent trigger error
<129>Jul 27 03:57:17 node-1 haproxy[23696]: 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 27 03:57:17 node-1 haproxy[23696]: 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 27 03:57:17 node-1 haproxy[23696]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:17 node-1 haproxy[23696]: proxy keystone-1 has no server available!
<129>Jul 27 03:57:17 node-1 haproxy[23696]: 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 27 03:57:17 node-1 haproxy[23696]: 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 27 03:57:18 node-1 haproxy[23703]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:18 node-1 haproxy[23703]: proxy keystone-2 has no server available!
<129>Jul 27 03:57:18 node-1 haproxy[23703]: 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 27 03:57:18 node-1 haproxy[23703]: 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 27 03:57:18 node-1 haproxy[23703]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:18 node-1 haproxy[23703]: proxy neutron has no server available!
<129>Jul 27 03:57:18 node-1 haproxy[23703]: 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 27 03:57:18 node-1 haproxy[23703]: 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 27 03:57:18 node-1 haproxy[23703]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:18 node-1 haproxy[23703]: proxy mysqld has no server available!
<129>Jul 27 03:57:18 node-1 haproxy[23703]: 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 27 03:57:18 node-1 haproxy[23703]: 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 27 03:57:19 node-1 haproxy[23703]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:19 node-1 haproxy[23703]: proxy object-storage has no server available!
<27>Jul 27 03:57:20 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:20 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:20 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:20 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:20 node-1 multipathd: uevent trigger error
<129>Jul 27 03:57:22 node-1 haproxy[25119]: 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 27 03:57:23 node-1 haproxy[25123]: Server keystone-1/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 27 03:57:23 node-1 haproxy[25123]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:23 node-1 haproxy[25123]: proxy keystone-1 has no server available!
<129>Jul 27 03:57:23 node-1 haproxy[25123]: 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 27 03:57:23 node-1 haproxy[25123]: 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 27 03:57:23 node-1 haproxy[25123]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:23 node-1 haproxy[25123]: proxy keystone-2 has no server available!
<129>Jul 27 03:57:23 node-1 haproxy[25123]: 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 27 03:57:23 node-1 haproxy[25123]: 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 27 03:57:23 node-1 haproxy[25123]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:23 node-1 haproxy[25123]: proxy neutron has no server available!
<129>Jul 27 03:57:23 node-1 haproxy[25123]: 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 27 03:57:23 node-1 haproxy[25123]: 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 27 03:57:24 node-1 haproxy[25123]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:24 node-1 haproxy[25123]: proxy mysqld has no server available!
<129>Jul 27 03:57:24 node-1 haproxy[25123]: 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 27 03:57:24 node-1 haproxy[25123]: 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 27 03:57:24 node-1 haproxy[25123]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:24 node-1 haproxy[25123]: proxy object-storage has no server available!
<129>Jul 27 03:57:24 node-1 haproxy[25123]: 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 27 03:57:24 node-1 haproxy[25123]: 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 27 03:57:24 node-1 haproxy[25123]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:24 node-1 haproxy[25123]: proxy aodh has no server available!
<27>Jul 27 03:57:26 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:26 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:26 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:26 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:26 node-1 multipathd: uevent trigger error
<129>Jul 27 03:57:28 node-1 haproxy[26664]: 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 27 03:57:28 node-1 haproxy[26664]: Server keystone-1/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 27 03:57:28 node-1 haproxy[26664]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:28 node-1 haproxy[26664]: proxy keystone-1 has no server available!
<129>Jul 27 03:57:28 node-1 haproxy[26664]: 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 27 03:57:28 node-1 haproxy[26664]: 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 27 03:57:28 node-1 haproxy[26664]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:28 node-1 haproxy[26664]: proxy keystone-2 has no server available!
<129>Jul 27 03:57:28 node-1 haproxy[26664]: 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 27 03:57:28 node-1 haproxy[26664]: 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 27 03:57:29 node-1 haproxy[26671]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:29 node-1 haproxy[26671]: proxy neutron has no server available!
<129>Jul 27 03:57:29 node-1 haproxy[26671]: 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 27 03:57:29 node-1 haproxy[26671]: 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 27 03:57:29 node-1 haproxy[26671]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:29 node-1 haproxy[26671]: proxy mysqld has no server available!
<129>Jul 27 03:57:29 node-1 haproxy[26671]: 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 27 03:57:29 node-1 haproxy[26671]: 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 27 03:57:29 node-1 haproxy[26671]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:29 node-1 haproxy[26671]: proxy object-storage has no server available!
<129>Jul 27 03:57:29 node-1 haproxy[26671]: 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 27 03:57:29 node-1 haproxy[26671]: 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 27 03:57:29 node-1 haproxy[26671]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:29 node-1 haproxy[26671]: proxy aodh has no server available!
<129>Jul 27 03:57:29 node-1 haproxy[26671]: 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 27 03:57:30 node-1 haproxy[26671]: 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 27 03:57:30 node-1 haproxy[26671]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:30 node-1 haproxy[26671]: proxy ceilometer has no server available!
<27>Jul 27 03:57:31 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:31 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:31 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:31 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:31 node-1 multipathd: uevent trigger error
<129>Jul 27 03:57:33 node-1 haproxy[28085]: 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 27 03:57:33 node-1 haproxy[28085]: 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 27 03:57:33 node-1 haproxy[28085]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:33 node-1 haproxy[28085]: proxy keystone-1 has no server available!
<129>Jul 27 03:57:34 node-1 haproxy[28089]: 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 27 03:57:34 node-1 haproxy[28089]: 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 27 03:57:34 node-1 haproxy[28089]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:34 node-1 haproxy[28089]: proxy keystone-2 has no server available!
<129>Jul 27 03:57:34 node-1 haproxy[28089]: 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 27 03:57:34 node-1 haproxy[28089]: 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 27 03:57:34 node-1 haproxy[28089]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:34 node-1 haproxy[28089]: proxy neutron has no server available!
<129>Jul 27 03:57:34 node-1 haproxy[28089]: 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 27 03:57:34 node-1 haproxy[28089]: 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 27 03:57:34 node-1 haproxy[28089]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:34 node-1 haproxy[28089]: proxy mysqld has no server available!
<129>Jul 27 03:57:34 node-1 haproxy[28089]: 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 27 03:57:34 node-1 haproxy[28089]: 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 27 03:57:34 node-1 haproxy[28089]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:34 node-1 haproxy[28089]: proxy object-storage has no server available!
<129>Jul 27 03:57:35 node-1 haproxy[28089]: 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 27 03:57:35 node-1 haproxy[28089]: 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 27 03:57:35 node-1 haproxy[28089]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:35 node-1 haproxy[28089]: proxy aodh has no server available!
<129>Jul 27 03:57:35 node-1 haproxy[28089]: 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 27 03:57:35 node-1 haproxy[28089]: 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 27 03:57:35 node-1 haproxy[28089]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:35 node-1 haproxy[28089]: proxy ceilometer has no server available!
<27>Jul 27 03:57:36 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:36 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:36 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:36 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:36 node-1 multipathd: uevent trigger error
<129>Jul 27 03:57:39 node-1 haproxy[29654]: 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 27 03:57:39 node-1 haproxy[29654]: 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 27 03:57:39 node-1 haproxy[29654]: 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 27 03:57:39 node-1 haproxy[29654]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:39 node-1 haproxy[29654]: proxy keystone-1 has no server available!
<129>Jul 27 03:57:39 node-1 haproxy[29654]: 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 27 03:57:39 node-1 haproxy[29654]: 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 27 03:57:39 node-1 haproxy[29654]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:39 node-1 haproxy[29654]: proxy keystone-2 has no server available!
<129>Jul 27 03:57:39 node-1 haproxy[29654]: 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 27 03:57:39 node-1 haproxy[29654]: 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 27 03:57:39 node-1 haproxy[29654]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:39 node-1 haproxy[29654]: proxy neutron has no server available!
<129>Jul 27 03:57:39 node-1 haproxy[29654]: 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 27 03:57:40 node-1 haproxy[29661]: 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 27 03:57:40 node-1 haproxy[29661]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:40 node-1 haproxy[29661]: proxy mysqld has no server available!
<129>Jul 27 03:57:40 node-1 haproxy[29661]: 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 27 03:57:40 node-1 haproxy[29661]: 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 27 03:57:40 node-1 haproxy[29661]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:40 node-1 haproxy[29661]: proxy object-storage has no server available!
<129>Jul 27 03:57:40 node-1 haproxy[29661]: 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 27 03:57:40 node-1 haproxy[29661]: 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 27 03:57:40 node-1 haproxy[29661]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:40 node-1 haproxy[29661]: proxy aodh has no server available!
<129>Jul 27 03:57:40 node-1 haproxy[29661]: 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 27 03:57:40 node-1 haproxy[29661]: 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 27 03:57:40 node-1 haproxy[29661]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:40 node-1 haproxy[29661]: proxy ceilometer has no server available!
<27>Jul 27 03:57:42 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:42 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:42 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:42 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:42 node-1 multipathd: uevent trigger error
<129>Jul 27 03:57:44 node-1 haproxy[31140]: 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 27 03:57:44 node-1 haproxy[31140]: 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 27 03:57:45 node-1 haproxy[31144]: 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 27 03:57:45 node-1 haproxy[31144]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:45 node-1 haproxy[31144]: proxy keystone-1 has no server available!
<129>Jul 27 03:57:45 node-1 haproxy[31144]: 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 27 03:57:45 node-1 haproxy[31144]: 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 27 03:57:45 node-1 haproxy[31144]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:45 node-1 haproxy[31144]: proxy keystone-2 has no server available!
<129>Jul 27 03:57:45 node-1 haproxy[31144]: 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 27 03:57:45 node-1 haproxy[31144]: 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 27 03:57:45 node-1 haproxy[31144]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:45 node-1 haproxy[31144]: proxy glance-api has no server available!
<129>Jul 27 03:57:45 node-1 haproxy[31144]: 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 27 03:57:45 node-1 haproxy[31144]: 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 27 03:57:45 node-1 haproxy[31144]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:45 node-1 haproxy[31144]: proxy glance-glare has no server available!
<129>Jul 27 03:57:45 node-1 haproxy[31144]: 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 27 03:57:45 node-1 haproxy[31144]: 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 27 03:57:45 node-1 haproxy[31144]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:45 node-1 haproxy[31144]: proxy neutron has no server available!
<129>Jul 27 03:57:45 node-1 haproxy[31144]: 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 27 03:57:45 node-1 haproxy[31144]: 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 27 03:57:45 node-1 haproxy[31144]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:45 node-1 haproxy[31144]: proxy glance-registry has no server available!
<129>Jul 27 03:57:45 node-1 haproxy[31144]: 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 27 03:57:46 node-1 haproxy[31144]: 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 27 03:57:46 node-1 haproxy[31144]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:46 node-1 haproxy[31144]: proxy mysqld has no server available!
<129>Jul 27 03:57:46 node-1 haproxy[31144]: 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 27 03:57:46 node-1 haproxy[31144]: 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 27 03:57:46 node-1 haproxy[31144]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:46 node-1 haproxy[31144]: proxy object-storage has no server available!
<129>Jul 27 03:57:46 node-1 haproxy[31144]: 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 27 03:57:46 node-1 haproxy[31144]: 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 27 03:57:46 node-1 haproxy[31144]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:46 node-1 haproxy[31144]: proxy aodh has no server available!
<129>Jul 27 03:57:46 node-1 haproxy[31144]: 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 27 03:57:46 node-1 haproxy[31144]: 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 27 03:57:46 node-1 haproxy[31144]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:46 node-1 haproxy[31144]: proxy ceilometer has no server available!
<27>Jul 27 03:57:48 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:48 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:48 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:48 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:48 node-1 multipathd: uevent trigger error
<129>Jul 27 03:57:50 node-1 haproxy[32605]: 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 27 03:57:50 node-1 haproxy[32605]: 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 27 03:57:50 node-1 haproxy[32605]: 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 27 03:57:51 node-1 haproxy[32609]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:51 node-1 haproxy[32609]: proxy keystone-1 has no server available!
<129>Jul 27 03:57:51 node-1 haproxy[32609]: 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 27 03:57:51 node-1 haproxy[32609]: 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 27 03:57:51 node-1 haproxy[32609]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:51 node-1 haproxy[32609]: proxy keystone-2 has no server available!
<129>Jul 27 03:57:51 node-1 haproxy[32609]: 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 27 03:57:51 node-1 haproxy[32609]: 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 27 03:57:51 node-1 haproxy[32609]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:51 node-1 haproxy[32609]: proxy nova-api has no server available!
<129>Jul 27 03:57:51 node-1 haproxy[32609]: 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 27 03:57:51 node-1 haproxy[32609]: 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 27 03:57:51 node-1 haproxy[32609]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:51 node-1 haproxy[32609]: proxy nova-metadata-api has no server available!
<129>Jul 27 03:57:51 node-1 haproxy[32609]: 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 27 03:57:51 node-1 haproxy[32609]: 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 27 03:57:51 node-1 haproxy[32609]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:51 node-1 haproxy[32609]: proxy glance-api has no server available!
<129>Jul 27 03:57:51 node-1 haproxy[32609]: 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 27 03:57:51 node-1 haproxy[32609]: 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 27 03:57:51 node-1 haproxy[32609]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:51 node-1 haproxy[32609]: proxy glance-glare has no server available!
<129>Jul 27 03:57:51 node-1 haproxy[32609]: 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 27 03:57:51 node-1 haproxy[32609]: 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 27 03:57:51 node-1 haproxy[32609]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:51 node-1 haproxy[32609]: proxy neutron has no server available!
<129>Jul 27 03:57:51 node-1 haproxy[32609]: 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 27 03:57:51 node-1 haproxy[32609]: 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 27 03:57:51 node-1 haproxy[32609]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:51 node-1 haproxy[32609]: proxy glance-registry has no server available!
<129>Jul 27 03:57:52 node-1 haproxy[32609]: 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 27 03:57:52 node-1 haproxy[32609]: 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 27 03:57:52 node-1 haproxy[32609]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:52 node-1 haproxy[32609]: proxy mysqld has no server available!
<129>Jul 27 03:57:52 node-1 haproxy[32609]: 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 27 03:57:52 node-1 haproxy[32609]: 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 27 03:57:52 node-1 haproxy[32609]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:52 node-1 haproxy[32609]: proxy object-storage has no server available!
<129>Jul 27 03:57:52 node-1 haproxy[32609]: 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 27 03:57:52 node-1 haproxy[32609]: 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 27 03:57:52 node-1 haproxy[32609]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:52 node-1 haproxy[32609]: proxy aodh has no server available!
<129>Jul 27 03:57:52 node-1 haproxy[32609]: 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 27 03:57:52 node-1 haproxy[32609]: 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 27 03:57:52 node-1 haproxy[32609]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:52 node-1 haproxy[32609]: proxy ceilometer has no server available!
<129>Jul 27 03:57:52 node-1 haproxy[32609]: 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 27 03:57:52 node-1 haproxy[32609]: 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 27 03:57:52 node-1 haproxy[32609]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:52 node-1 haproxy[32609]: proxy nova-novncproxy has no server available!
<27>Jul 27 03:57:53 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:53 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:54 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:54 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:54 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:54 node-1 multipathd: uevent trigger error
<129>Jul 27 03:57:56 node-1 haproxy[1589]: 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 27 03:57:56 node-1 haproxy[1589]: 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 27 03:57:56 node-1 haproxy[1589]: 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 27 03:57:56 node-1 haproxy[1589]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:56 node-1 haproxy[1589]: proxy keystone-1 has no server available!
<129>Jul 27 03:57:56 node-1 haproxy[1589]: 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 27 03:57:56 node-1 haproxy[1589]: 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 27 03:57:56 node-1 haproxy[1589]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:56 node-1 haproxy[1589]: proxy keystone-2 has no server available!
<129>Jul 27 03:57:56 node-1 haproxy[1589]: 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 27 03:57:56 node-1 haproxy[1589]: 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 27 03:57:56 node-1 haproxy[1589]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:56 node-1 haproxy[1589]: proxy nova-api has no server available!
<129>Jul 27 03:57:56 node-1 haproxy[1589]: 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 27 03:57:56 node-1 haproxy[1589]: 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 27 03:57:57 node-1 haproxy[1595]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:57 node-1 haproxy[1595]: proxy nova-metadata-api has no server available!
<129>Jul 27 03:57:57 node-1 haproxy[1595]: 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 27 03:57:57 node-1 haproxy[1595]: 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 27 03:57:57 node-1 haproxy[1595]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:57 node-1 haproxy[1595]: proxy cinder-api has no server available!
<129>Jul 27 03:57:57 node-1 haproxy[1595]: 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 27 03:57:57 node-1 haproxy[1595]: 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 27 03:57:57 node-1 haproxy[1595]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:57 node-1 haproxy[1595]: proxy glance-api has no server available!
<129>Jul 27 03:57:57 node-1 haproxy[1595]: 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 27 03:57:57 node-1 haproxy[1595]: 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 27 03:57:57 node-1 haproxy[1595]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:57 node-1 haproxy[1595]: proxy glance-glare has no server available!
<129>Jul 27 03:57:57 node-1 haproxy[1595]: 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 27 03:57:57 node-1 haproxy[1595]: 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 27 03:57:57 node-1 haproxy[1595]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:57 node-1 haproxy[1595]: proxy neutron has no server available!
<129>Jul 27 03:57:57 node-1 haproxy[1595]: 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 27 03:57:57 node-1 haproxy[1595]: 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 27 03:57:57 node-1 haproxy[1595]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:57 node-1 haproxy[1595]: proxy glance-registry has no server available!
<129>Jul 27 03:57:57 node-1 haproxy[1595]: 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 27 03:57:57 node-1 haproxy[1595]: 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 27 03:57:57 node-1 haproxy[1595]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:57 node-1 haproxy[1595]: proxy mysqld has no server available!
<129>Jul 27 03:57:57 node-1 haproxy[1595]: 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 27 03:57:57 node-1 haproxy[1595]: 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 27 03:57:57 node-1 haproxy[1595]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:57 node-1 haproxy[1595]: proxy object-storage has no server available!
<129>Jul 27 03:57:57 node-1 haproxy[1595]: 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 27 03:57:58 node-1 haproxy[1595]: 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 27 03:57:58 node-1 haproxy[1595]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:58 node-1 haproxy[1595]: proxy aodh has no server available!
<129>Jul 27 03:57:58 node-1 haproxy[1595]: 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 27 03:57:58 node-1 haproxy[1595]: 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 27 03:57:58 node-1 haproxy[1595]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:58 node-1 haproxy[1595]: proxy ceilometer has no server available!
<129>Jul 27 03:57:58 node-1 haproxy[1595]: 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 27 03:57:58 node-1 haproxy[1595]: 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 27 03:57:58 node-1 haproxy[1595]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:57:58 node-1 haproxy[1595]: proxy nova-novncproxy has no server available!
<27>Jul 27 03:57:59 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:59 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:59 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:59 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:59 node-1 multipathd: uevent trigger error
<27>Jul 27 03:57:59 node-1 multipathd: uevent trigger error
<129>Jul 27 03:58:02 node-1 haproxy[3058]: 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 27 03:58:02 node-1 haproxy[3058]: 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 27 03:58:02 node-1 haproxy[3058]: 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 27 03:58:02 node-1 haproxy[3058]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:02 node-1 haproxy[3058]: proxy keystone-1 has no server available!
<129>Jul 27 03:58:02 node-1 haproxy[3058]: 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 27 03:58:02 node-1 haproxy[3058]: 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 27 03:58:02 node-1 haproxy[3058]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:02 node-1 haproxy[3058]: proxy keystone-2 has no server available!
<129>Jul 27 03:58:02 node-1 haproxy[3058]: 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 27 03:58:02 node-1 haproxy[3058]: 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 27 03:58:02 node-1 haproxy[3058]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:02 node-1 haproxy[3058]: proxy nova-api has no server available!
<129>Jul 27 03:58:02 node-1 haproxy[3058]: 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 27 03:58:02 node-1 haproxy[3058]: 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 27 03:58:02 node-1 haproxy[3058]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:02 node-1 haproxy[3058]: proxy nova-metadata-api has no server available!
<129>Jul 27 03:58:02 node-1 haproxy[3058]: 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 27 03:58:02 node-1 haproxy[3058]: 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 27 03:58:02 node-1 haproxy[3058]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:02 node-1 haproxy[3058]: proxy cinder-api has no server available!
<129>Jul 27 03:58:02 node-1 haproxy[3058]: 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 27 03:58:02 node-1 haproxy[3058]: 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 27 03:58:02 node-1 haproxy[3058]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:02 node-1 haproxy[3058]: proxy glance-api has no server available!
<129>Jul 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:03 node-1 haproxy[3065]: proxy glance-glare has no server available!
<129>Jul 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:03 node-1 haproxy[3065]: proxy neutron has no server available!
<129>Jul 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:03 node-1 haproxy[3065]: proxy glance-registry has no server available!
<129>Jul 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:03 node-1 haproxy[3065]: proxy mysqld has no server available!
<129>Jul 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:03 node-1 haproxy[3065]: proxy object-storage has no server available!
<129>Jul 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:03 node-1 haproxy[3065]: proxy aodh has no server available!
<129>Jul 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:03 node-1 haproxy[3065]: proxy ceilometer has no server available!
<129>Jul 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:03 node-1 haproxy[3065]: proxy heat-api has no server available!
<129>Jul 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:03 node-1 haproxy[3065]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:03 node-1 haproxy[3065]: proxy heat-api-cfn has no server available!
<129>Jul 27 03:58:03 node-1 haproxy[3065]: 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 27 03:58:04 node-1 haproxy[3065]: 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 27 03:58:04 node-1 haproxy[3065]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:04 node-1 haproxy[3065]: proxy heat-api-cloudwatch has no server available!
<129>Jul 27 03:58:04 node-1 haproxy[3065]: 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 27 03:58:04 node-1 haproxy[3065]: 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 27 03:58:04 node-1 haproxy[3065]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:04 node-1 haproxy[3065]: proxy nova-novncproxy has no server available!
<27>Jul 27 03:58:05 node-1 multipathd: uevent trigger error
<27>Jul 27 03:58:05 node-1 multipathd: uevent trigger error
<27>Jul 27 03:58:05 node-1 multipathd: uevent trigger error
<27>Jul 27 03:58:05 node-1 multipathd: uevent trigger error
<27>Jul 27 03:58:05 node-1 multipathd: uevent trigger error
<27>Jul 27 03:58:08 node-1 multipathd: uevent trigger error
<27>Jul 27 03:58:08 node-1 multipathd: uevent trigger error
<27>Jul 27 03:58:08 node-1 multipathd: uevent trigger error
<27>Jul 27 03:58:08 node-1 multipathd: uevent trigger error
<27>Jul 27 03:58:08 node-1 multipathd: uevent trigger error
<27>Jul 27 03:58:22 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 27 03:58:47 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 27 03:58:49 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 27 03:59:19 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 03:59:26 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 03:59:47 node-1 multipathd: uevent trigger error
<27>Jul 27 03:59:47 node-1 multipathd: uevent trigger error
<27>Jul 27 03:59:47 node-1 multipathd: uevent trigger error
<27>Jul 27 03:59:47 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:04 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:04 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:04 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:04 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:04 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:04 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:11 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:11 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:11 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:11 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:11 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:21 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 04:02:33 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:33 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:33 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:33 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:33 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:33 node-1 multipathd: uevent trigger error
<43>Jul 27 04:02:34 node-1 apache2_error [Wed Jul 27 04:02:24.495572 2016] [mpm_event:notice] [pid 14329:tid 139791193651072] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 27 04:02:34 node-1 apache2_error [Wed Jul 27 04:02:24.495643 2016] [core:notice] [pid 14329:tid 139791193651072] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 27 04:02:34 node-1 apache2_error [Wed Jul 27 04:02:27.743550 2016] [mpm_event:notice] [pid 14329:tid 139791193651072] AH00491: caught SIGTERM, shutting down
<43>Jul 27 04:02:34 node-1 apache2_error [Wed Jul 27 04:02:28.830755 2016] [mpm_worker:notice] [pid 14831:tid 140084831414144] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 27 04:02:34 node-1 apache2_error [Wed Jul 27 04:02:28.830809 2016] [core:notice] [pid 14831:tid 140084831414144] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 04:02:38 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:38 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:38 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:38 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:38 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:38 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:41 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:41 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:41 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:41 node-1 multipathd: uevent trigger error
<27>Jul 27 04:02:41 node-1 multipathd: uevent trigger error
<43>Jul 27 04:03:54 node-1 apache2_error [Wed Jul 27 04:03:54.378124 2016] [mpm_worker:notice] [pid 14831:tid 140084831414144] AH00295: caught SIGTERM, shutting down
<43>Jul 27 04:04:04 node-1 apache2_error [Wed Jul 27 04:03:55.139941 2016] [mpm_worker:notice] [pid 30696:tid 140318835189632] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 04:04:04 node-1 apache2_error [Wed Jul 27 04:03:55.140004 2016] [core:notice] [pid 30696:tid 140318835189632] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 27 04:04:44 node-1 apache2_error [Wed Jul 27 04:04:39.908641 2016] [mpm_worker:notice] [pid 30696:tid 140318835189632] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 04:04:44 node-1 apache2_error [Wed Jul 27 04:04:40.101355 2016] [mpm_worker:warn] [pid 30696:tid 140318835189632] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 04:04:44 node-1 apache2_error [Wed Jul 27 04:04:40.105639 2016] [mpm_worker:notice] [pid 30696:tid 140318835189632] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 04:04:44 node-1 apache2_error [Wed Jul 27 04:04:40.105653 2016] [core:notice] [pid 30696:tid 140318835189632] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 04:05:22 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 04:05:25 node-1 multipathd: uevent trigger error
<27>Jul 27 04:05:25 node-1 multipathd: uevent trigger error
<27>Jul 27 04:05:25 node-1 multipathd: uevent trigger error
<27>Jul 27 04:05:25 node-1 multipathd: uevent trigger error
<27>Jul 27 04:05:25 node-1 multipathd: uevent trigger error
<27>Jul 27 04:05:29 node-1 multipathd: uevent trigger error
<27>Jul 27 04:05:29 node-1 multipathd: uevent trigger error
<27>Jul 27 04:05:29 node-1 multipathd: uevent trigger error
<27>Jul 27 04:05:29 node-1 multipathd: uevent trigger error
<27>Jul 27 04:05:29 node-1 multipathd: uevent trigger error
<27>Jul 27 04:05:45 node-1 multipathd: uevent trigger error
<27>Jul 27 04:05:45 node-1 multipathd: uevent trigger error
<27>Jul 27 04:05:45 node-1 multipathd: uevent trigger error
<27>Jul 27 04:05:45 node-1 multipathd: uevent trigger error
<27>Jul 27 04:05:45 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:07 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:07 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:07 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:07 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:07 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:07 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:07 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:12 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:12 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:12 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:12 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:12 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:06:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:07:10 node-1 multipathd: uevent trigger error
<27>Jul 27 04:07:10 node-1 multipathd: uevent trigger error
<27>Jul 27 04:07:10 node-1 multipathd: uevent trigger error
<27>Jul 27 04:07:10 node-1 multipathd: uevent trigger error
<27>Jul 27 04:07:10 node-1 multipathd: uevent trigger error
<27>Jul 27 04:08:09 node-1 multipathd: uevent trigger error
<27>Jul 27 04:08:09 node-1 multipathd: uevent trigger error
<27>Jul 27 04:08:09 node-1 multipathd: uevent trigger error
<27>Jul 27 04:08:09 node-1 multipathd: uevent trigger error
<27>Jul 27 04:08:09 node-1 multipathd: uevent trigger error
<27>Jul 27 04:08:09 node-1 multipathd: uevent trigger error
<27>Jul 27 04:08:24 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 04:09:22 node-1 multipathd: uevent trigger error
<27>Jul 27 04:09:22 node-1 multipathd: uevent trigger error
<27>Jul 27 04:09:22 node-1 multipathd: uevent trigger error
<27>Jul 27 04:09:22 node-1 multipathd: uevent trigger error
<27>Jul 27 04:09:22 node-1 multipathd: uevent trigger error
<27>Jul 27 04:09:22 node-1 multipathd: uevent trigger error
<27>Jul 27 04:09:22 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:23 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:23 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:23 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:23 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:23 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:23 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:49 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:49 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:49 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:10:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:11:25 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 04:13:27 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:27 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:27 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:27 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:27 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:27 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:42 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:42 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:42 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:42 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:42 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:42 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:54 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:54 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:54 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:54 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:54 node-1 multipathd: uevent trigger error
<27>Jul 27 04:13:54 node-1 multipathd: uevent trigger error
<27>Jul 27 04:14:15 node-1 multipathd: uevent trigger error
<27>Jul 27 04:14:15 node-1 multipathd: uevent trigger error
<27>Jul 27 04:14:15 node-1 multipathd: uevent trigger error
<27>Jul 27 04:14:15 node-1 multipathd: uevent trigger error
<27>Jul 27 04:14:15 node-1 multipathd: uevent trigger error
<27>Jul 27 04:14:15 node-1 multipathd: uevent trigger error
<27>Jul 27 04:14:18 node-1 multipathd: uevent trigger error
<27>Jul 27 04:14:18 node-1 multipathd: uevent trigger error
<27>Jul 27 04:14:18 node-1 multipathd: uevent trigger error
<27>Jul 27 04:14:18 node-1 multipathd: uevent trigger error
<27>Jul 27 04:14:18 node-1 multipathd: uevent trigger error
<27>Jul 27 04:14:27 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 04:15:03 node-1 multipathd: uevent trigger error
<27>Jul 27 04:15:03 node-1 multipathd: uevent trigger error
<27>Jul 27 04:15:03 node-1 multipathd: uevent trigger error
<27>Jul 27 04:15:03 node-1 multipathd: uevent trigger error
<27>Jul 27 04:15:03 node-1 multipathd: uevent trigger error
<27>Jul 27 04:15:51 node-1 multipathd: uevent trigger error
<27>Jul 27 04:15:51 node-1 multipathd: uevent trigger error
<27>Jul 27 04:15:51 node-1 multipathd: uevent trigger error
<27>Jul 27 04:15:51 node-1 multipathd: uevent trigger error
<27>Jul 27 04:15:51 node-1 multipathd: uevent trigger error
<27>Jul 27 04:15:51 node-1 multipathd: uevent trigger error
<27>Jul 27 04:16:06 node-1 multipathd: uevent trigger error
<27>Jul 27 04:16:06 node-1 multipathd: uevent trigger error
<27>Jul 27 04:16:06 node-1 multipathd: uevent trigger error
<27>Jul 27 04:16:06 node-1 multipathd: uevent trigger error
<27>Jul 27 04:16:06 node-1 multipathd: uevent trigger error
<27>Jul 27 04:17:28 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 04:18:32 node-1 multipathd: uevent trigger error
<27>Jul 27 04:18:32 node-1 multipathd: uevent trigger error
<27>Jul 27 04:18:32 node-1 multipathd: uevent trigger error
<27>Jul 27 04:18:32 node-1 multipathd: uevent trigger error
<27>Jul 27 04:18:32 node-1 multipathd: uevent trigger error
<27>Jul 27 04:18:58 node-1 multipathd: uevent trigger error
<27>Jul 27 04:18:58 node-1 multipathd: uevent trigger error
<27>Jul 27 04:18:58 node-1 multipathd: uevent trigger error
<27>Jul 27 04:18:58 node-1 multipathd: uevent trigger error
<27>Jul 27 04:18:58 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:03 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:03 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:03 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:03 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:03 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:03 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:40 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:40 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:40 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:40 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:44 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:44 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:44 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:44 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:44 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:49 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:49 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:49 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:49 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:49 node-1 multipathd: uevent trigger error
<27>Jul 27 04:19:49 node-1 multipathd: uevent trigger error
<27>Jul 27 04:20:01 node-1 multipathd: uevent trigger error
<27>Jul 27 04:20:01 node-1 multipathd: uevent trigger error
<27>Jul 27 04:20:01 node-1 multipathd: uevent trigger error
<27>Jul 27 04:20:01 node-1 multipathd: uevent trigger error
<27>Jul 27 04:20:01 node-1 multipathd: uevent trigger error
<27>Jul 27 04:20:07 node-1 multipathd: uevent trigger error
<27>Jul 27 04:20:07 node-1 multipathd: uevent trigger error
<27>Jul 27 04:20:07 node-1 multipathd: uevent trigger error
<27>Jul 27 04:20:07 node-1 multipathd: uevent trigger error
<27>Jul 27 04:20:07 node-1 multipathd: uevent trigger error
<27>Jul 27 04:20:30 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 27 04:20:44 node-1 multipathd: uevent trigger error
<27>Jul 27 04:20:44 node-1 multipathd: uevent trigger error
<27>Jul 27 04:20:44 node-1 multipathd: uevent trigger error
<27>Jul 27 04:20:44 node-1 multipathd: uevent trigger error
<27>Jul 27 04:20:44 node-1 multipathd: uevent trigger error
<27>Jul 27 04:21:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:21:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:21:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:21:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:21:55 node-1 multipathd: uevent trigger error
<27>Jul 27 04:22:13 node-1 multipathd: uevent trigger error
<27>Jul 27 04:22:13 node-1 multipathd: uevent trigger error
<27>Jul 27 04:22:13 node-1 multipathd: uevent trigger error
<27>Jul 27 04:22:13 node-1 multipathd: uevent trigger error
<27>Jul 27 04:22:13 node-1 multipathd: uevent trigger error
<11>Jul 27 04:22:27 node-1 liberasurecode[17275]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:27 node-1 liberasurecode[17275]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:27 node-1 liberasurecode[17275]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:27 node-1 liberasurecode[17275]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:27 node-1 liberasurecode[17318]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:27 node-1 liberasurecode[17318]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:27 node-1 liberasurecode[17318]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:27 node-1 liberasurecode[17318]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:30 node-1 liberasurecode[17750]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:30 node-1 liberasurecode[17750]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:30 node-1 liberasurecode[17750]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:30 node-1 liberasurecode[17750]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18585]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18585]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18585]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18585]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18621]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18621]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18621]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18621]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18671]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18671]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18671]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18671]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18748]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18748]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18748]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18748]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18762]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18762]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18762]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18762]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18774]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18774]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18774]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18774]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18790]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18790]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18790]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:36 node-1 liberasurecode[18790]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:45 node-1 liberasurecode[20118]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:45 node-1 liberasurecode[20118]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:45 node-1 liberasurecode[20118]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:22:45 node-1 liberasurecode[20118]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 27 04:22:53 node-1 multipathd: uevent trigger error
<27>Jul 27 04:22:53 node-1 multipathd: uevent trigger error
<27>Jul 27 04:22:53 node-1 multipathd: uevent trigger error
<27>Jul 27 04:22:53 node-1 multipathd: uevent trigger error
<27>Jul 27 04:22:53 node-1 multipathd: uevent trigger error
<27>Jul 27 04:23:32 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 27 04:23:46 node-1 apache2_error [Wed Jul 27 04:23:43.423163 2016] [mpm_worker:notice] [pid 30696:tid 140318835189632] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 04:23:46 node-1 apache2_error [Wed Jul 27 04:23:43.807758 2016] [mpm_worker:warn] [pid 30696:tid 140318835189632] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 04:23:46 node-1 apache2_error [Wed Jul 27 04:23:43.811877 2016] [mpm_worker:notice] [pid 30696:tid 140318835189632] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 04:23:46 node-1 apache2_error [Wed Jul 27 04:23:43.811924 2016] [core:notice] [pid 30696:tid 140318835189632] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 04:24:25 node-1 multipathd: uevent trigger error
<27>Jul 27 04:24:25 node-1 multipathd: uevent trigger error
<27>Jul 27 04:24:25 node-1 multipathd: uevent trigger error
<27>Jul 27 04:24:25 node-1 multipathd: uevent trigger error
<27>Jul 27 04:24:25 node-1 multipathd: uevent trigger error
<27>Jul 27 04:24:25 node-1 multipathd: uevent trigger error
<43>Jul 27 04:24:26 node-1 apache2_error [Wed Jul 27 04:24:21.005041 2016] [mpm_worker:notice] [pid 30696:tid 140318835189632] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 04:24:26 node-1 apache2_error [Wed Jul 27 04:24:21.199245 2016] [mpm_worker:warn] [pid 30696:tid 140318835189632] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 04:24:26 node-1 apache2_error [Wed Jul 27 04:24:21.207414 2016] [mpm_worker:notice] [pid 30696:tid 140318835189632] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 04:24:26 node-1 apache2_error [Wed Jul 27 04:24:21.207448 2016] [core:notice] [pid 30696:tid 140318835189632] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 04:24:32 node-1 multipathd: uevent trigger error
<27>Jul 27 04:24:32 node-1 multipathd: uevent trigger error
<27>Jul 27 04:24:32 node-1 multipathd: uevent trigger error
<27>Jul 27 04:24:32 node-1 multipathd: uevent trigger error
<27>Jul 27 04:24:32 node-1 multipathd: uevent trigger error
<11>Jul 27 04:25:02 node-1 liberasurecode[8947]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:25:02 node-1 liberasurecode[8947]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:25:02 node-1 liberasurecode[8947]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:25:02 node-1 liberasurecode[8947]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 27 04:25:10 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:10 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:10 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:10 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:10 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:10 node-1 multipathd: uevent trigger error
<43>Jul 27 04:25:16 node-1 apache2_error [Wed Jul 27 04:25:06.606733 2016] [mpm_worker:notice] [pid 30696:tid 140318835189632] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 04:25:16 node-1 apache2_error [Wed Jul 27 04:25:06.802813 2016] [mpm_worker:warn] [pid 30696:tid 140318835189632] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 04:25:16 node-1 apache2_error [Wed Jul 27 04:25:06.810373 2016] [mpm_worker:notice] [pid 30696:tid 140318835189632] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 04:25:16 node-1 apache2_error [Wed Jul 27 04:25:06.810404 2016] [core:notice] [pid 30696:tid 140318835189632] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 04:25:17 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:17 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:17 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:17 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:17 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:22 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:22 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:22 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:22 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:22 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:22 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:30 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:30 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:30 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:30 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:30 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:30 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:25:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:12 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:12 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:21 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 27 04:26:29 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:29 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:29 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:29 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:34 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:34 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:34 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:34 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:34 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:38 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:39 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:39 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:39 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:44 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:44 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:44 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:44 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:44 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:56 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 04:26:57 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:57 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:57 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:57 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:57 node-1 multipathd: uevent trigger error
<27>Jul 27 04:26:57 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:23 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:23 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:23 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:24 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:24 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:24 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:28 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:28 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:28 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:28 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:28 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:28 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:41 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:41 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:41 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:41 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:41 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:48 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:53 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:53 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:53 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:53 node-1 multipathd: uevent trigger error
<27>Jul 27 04:27:53 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:10 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:10 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:10 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:10 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:10 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:24 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:24 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:24 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:24 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:24 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:29 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:29 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:29 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:29 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:29 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:33 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:33 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:33 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:33 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:33 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:33 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:37 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:37 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:37 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:37 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:37 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:42 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:42 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:42 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:42 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:42 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:46 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:46 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:46 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:46 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:46 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:46 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:51 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:51 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:51 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:51 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:51 node-1 multipathd: uevent trigger error
<27>Jul 27 04:29:51 node-1 multipathd: uevent trigger error
<11>Jul 27 04:30:01 node-1 liberasurecode[22316]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:30:01 node-1 liberasurecode[22316]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:30:01 node-1 liberasurecode[22316]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:30:01 node-1 liberasurecode[22316]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
