Jul 27 03:50:58 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8362" x-info="http://www.rsyslog.com"] start
Jul 27 03:50:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 27 03:50:58 node-4 rsyslogd: rsyslogd's groupid changed to 104
Jul 27 03:50:58 node-4 rsyslogd: rsyslogd's userid changed to 101
Jul 27 03:50:58 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 27 03:50:58 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 27 03:50:58 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 27 03:50:58 node-4 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:50:58 node-4 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:50:58 node-4 kernel: [    0.000000] KERNEL supported cpus:
Jul 27 03:50:58 node-4 kernel: [    0.000000]   Intel GenuineIntel
Jul 27 03:50:58 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Jul 27 03:50:58 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Jul 27 03:50:58 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 27 03:50:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 27 03:50:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 27 03:50:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 27 03:50:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 27 03:50:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 27 03:50:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 27 03:50:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 27 03:50:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 27 03:50:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 27 03:50:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 27 03:50:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 27 03:50:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 27 03:50:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 27 03:50:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 27 03:50:58 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 27 03:50:58 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 27 03:50:58 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 27 03:50:58 node-4 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:50:58 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 27 03:50:58 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 27 03:50:58 node-4 kernel: [    0.000000] No AGP bridge found
Jul 27 03:50:58 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 27 03:50:58 node-4 kernel: [    0.000000] MTRR default type: write-back
Jul 27 03:50:58 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 27 03:50:58 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Jul 27 03:50:58 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 27 03:50:58 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 27 03:50:58 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 27 03:50:58 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 27 03:50:58 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 27 03:50:58 node-4 kernel: [    0.000000]   2 disabled
Jul 27 03:50:58 node-4 kernel: [    0.000000]   3 disabled
Jul 27 03:50:58 node-4 kernel: [    0.000000]   4 disabled
Jul 27 03:50:58 node-4 kernel: [    0.000000]   5 disabled
Jul 27 03:50:58 node-4 kernel: [    0.000000]   6 disabled
Jul 27 03:50:58 node-4 kernel: [    0.000000]   7 disabled
Jul 27 03:50:58 node-4 kernel: [    0.000000]   8 disabled
Jul 27 03:50:58 node-4 kernel: [    0.000000]   9 disabled
Jul 27 03:50:58 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 27 03:50:58 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 27 03:50:58 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 27 03:50:58 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 27 03:50:58 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 27 03:50:58 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Jul 27 03:50:58 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 27 03:50:58 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 27 03:50:58 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 27 03:50:58 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 27 03:50:58 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 27 03:50:58 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 27 03:50:58 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 27 03:50:58 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 27 03:50:58 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 27 03:50:58 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 27 03:50:58 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 27 03:50:58 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 27 03:50:58 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 27 03:50:58 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 27 03:50:58 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 27 03:50:58 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 27 03:50:58 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 27 03:50:58 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 27 03:50:58 node-4 kernel: [    0.000000] Zone ranges:
Jul 27 03:50:58 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] Movable zone start for each node
Jul 27 03:50:58 node-4 kernel: [    0.000000] Early memory node ranges
Jul 27 03:50:58 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 27 03:50:58 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 27 03:50:58 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 27 03:50:58 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 27 03:50:58 node-4 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 27 03:50:58 node-4 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 27 03:50:58 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 27 03:50:58 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 27 03:50:58 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 27 03:50:58 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 27 03:50:58 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 27 03:50:58 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 27 03:50:58 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 27 03:50:58 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 27 03:50:58 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 27 03:50:58 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 27 03:50:58 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 27 03:50:58 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 27 03:50:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 27 03:50:58 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 27 03:50:58 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 27 03:50:58 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 27 03:50:58 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 27 03:50:58 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 27 03:50:58 node-4 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:50:58 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 27 03:50:58 node-4 kernel: [    0.000000] Policy zone: Normal
Jul 27 03:50:58 node-4 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:50:58 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 27 03:50:58 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 27 03:50:58 node-4 kernel: [    0.000000] Checking aperture...
Jul 27 03:50:58 node-4 kernel: [    0.000000] No AGP bridge found
Jul 27 03:50:58 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 27 03:50:58 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 27 03:50:58 node-4 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 27 03:50:58 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 27 03:50:58 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 27 03:50:58 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 27 03:50:58 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 27 03:50:58 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 27 03:50:58 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 27 03:50:58 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 27 03:50:58 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 27 03:50:58 node-4 kernel: [    0.000000] console [tty0] enabled
Jul 27 03:50:58 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 27 03:50:58 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 27 03:50:58 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 27 03:50:58 node-4 kernel: [    0.000000] hpet clockevent registered
Jul 27 03:50:58 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 27 03:50:58 node-4 kernel: [    0.004000] tsc: Detected 3491.902 MHz processor
Jul 27 03:50:58 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.80 BogoMIPS (lpj=13967608)
Jul 27 03:50:58 node-4 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 27 03:50:58 node-4 kernel: [    0.000044] Security Framework initialized
Jul 27 03:50:58 node-4 kernel: [    0.000063] AppArmor: AppArmor initialized
Jul 27 03:50:58 node-4 kernel: [    0.000064] Yama: becoming mindful.
Jul 27 03:50:58 node-4 kernel: [    0.001455] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 27 03:50:58 node-4 kernel: [    0.006260] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 27 03:50:58 node-4 kernel: [    0.008186] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 27 03:50:58 node-4 kernel: [    0.008214] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 27 03:50:58 node-4 kernel: [    0.008504] Initializing cgroup subsys memory
Jul 27 03:50:58 node-4 kernel: [    0.008512] Initializing cgroup subsys devices
Jul 27 03:50:58 node-4 kernel: [    0.008514] Initializing cgroup subsys freezer
Jul 27 03:50:58 node-4 kernel: [    0.008516] Initializing cgroup subsys blkio
Jul 27 03:50:58 node-4 kernel: [    0.008517] Initializing cgroup subsys perf_event
Jul 27 03:50:58 node-4 kernel: [    0.008520] Initializing cgroup subsys hugetlb
Jul 27 03:50:58 node-4 kernel: [    0.008539] CPU: Physical Processor ID: 0
Jul 27 03:50:58 node-4 kernel: [    0.008540] CPU: Processor Core ID: 0
Jul 27 03:50:58 node-4 kernel: [    0.008544] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 27 03:50:58 node-4 kernel: [    0.008544] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 27 03:50:58 node-4 kernel: [    0.009237] mce: CPU supports 22 MCE banks
Jul 27 03:50:58 node-4 kernel: [    0.009265] CPU0: Thermal monitoring enabled (TM1)
Jul 27 03:50:58 node-4 kernel: [    0.009286] process: using mwait in idle threads
Jul 27 03:50:58 node-4 kernel: [    0.009289] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 27 03:50:58 node-4 kernel: [    0.009289] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 27 03:50:58 node-4 kernel: [    0.009289] tlb_flushall_shift: 6
Jul 27 03:50:58 node-4 kernel: [    0.009378] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 27 03:50:58 node-4 kernel: [    0.010101] ACPI: Core revision 20131115
Jul 27 03:50:58 node-4 kernel: [    0.022758] ACPI: All ACPI Tables successfully acquired
Jul 27 03:50:58 node-4 kernel: [    0.022928] ftrace: allocating 28617 entries in 112 pages
Jul 27 03:50:58 node-4 kernel: [    0.031739] dmar: Host address width 46
Jul 27 03:50:58 node-4 kernel: [    0.031741] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 27 03:50:58 node-4 kernel: [    0.031747] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 27 03:50:58 node-4 kernel: [    0.031749] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 27 03:50:58 node-4 kernel: [    0.031753] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 27 03:50:58 node-4 kernel: [    0.031754] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 27 03:50:58 node-4 kernel: [    0.031755] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 27 03:50:58 node-4 kernel: [    0.031756] dmar: ATSR flags: 0x0
Jul 27 03:50:58 node-4 kernel: [    0.031758] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 27 03:50:58 node-4 kernel: [    0.031759] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 27 03:50:58 node-4 kernel: [    0.031874] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 27 03:50:58 node-4 kernel: [    0.031875] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 27 03:50:58 node-4 kernel: [    0.031876] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 27 03:50:58 node-4 kernel: [    0.031877] HPET id 0 under DRHD base 0xc7ffc000
Jul 27 03:50:58 node-4 kernel: [    0.031878] Your BIOS is broken and requested that x2apic be disabled.
Jul 27 03:50:58 node-4 kernel: [    0.031878] This will slightly decrease performance.
Jul 27 03:50:58 node-4 kernel: [    0.031878] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 27 03:50:58 node-4 kernel: [    0.032310] Enabled IRQ remapping in xapic mode
Jul 27 03:50:58 node-4 kernel: [    0.032311] x2apic not enabled, IRQ remapping is in xapic mode
Jul 27 03:50:58 node-4 kernel: [    0.032315] Switched APIC routing to physical flat.
Jul 27 03:50:58 node-4 kernel: [    0.032946] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 27 03:50:58 node-4 kernel: [    0.072595] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 27 03:50:58 node-4 kernel: [    0.072601] TSC deadline timer enabled
Jul 27 03:50:58 node-4 kernel: [    0.072608] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 27 03:50:58 node-4 kernel: [    0.072614] ... version:                3
Jul 27 03:50:58 node-4 kernel: [    0.072615] ... bit width:              48
Jul 27 03:50:58 node-4 kernel: [    0.072616] ... generic registers:      4
Jul 27 03:50:58 node-4 kernel: [    0.072617] ... value mask:             0000ffffffffffff
Jul 27 03:50:58 node-4 kernel: [    0.072618] ... max period:             0000ffffffffffff
Jul 27 03:50:58 node-4 kernel: [    0.072619] ... fixed-purpose events:   3
Jul 27 03:50:58 node-4 kernel: [    0.072620] ... event mask:             000000070000000f
Jul 27 03:50:58 node-4 kernel: [    0.074051] x86: Booting SMP configuration:
Jul 27 03:50:58 node-4 kernel: [    0.088177] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 27 03:50:58 node-4 kernel: [    0.074053] .... node  #0, CPUs:        #1  #2  #3
Jul 27 03:50:58 node-4 kernel: [    0.116086] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 27 03:50:58 node-4 kernel: [    0.270239] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 27 03:50:58 node-4 kernel: [    0.325858] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 27 03:50:58 node-4 kernel: [    0.382906] x86: Booted up 2 nodes, 16 CPUs
Jul 27 03:50:58 node-4 kernel: [    0.382909] smpboot: Total of 16 processors activated (111753.19 BogoMIPS)
Jul 27 03:50:58 node-4 kernel: [    0.407287] devtmpfs: initialized
Jul 27 03:50:58 node-4 kernel: [    0.410396] EVM: security.selinux
Jul 27 03:50:58 node-4 kernel: [    0.410398] EVM: security.SMACK64
Jul 27 03:50:58 node-4 kernel: [    0.410399] EVM: security.ima
Jul 27 03:50:58 node-4 kernel: [    0.410399] EVM: security.capability
Jul 27 03:50:58 node-4 kernel: [    0.410450] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 27 03:50:58 node-4 kernel: [    0.411121] pinctrl core: initialized pinctrl subsystem
Jul 27 03:50:58 node-4 kernel: [    0.411185] regulator-dummy: no parameters
Jul 27 03:50:58 node-4 kernel: [    0.411216] RTC time:  3:50:20, date: 07/27/16
Jul 27 03:50:58 node-4 kernel: [    0.411250] NET: Registered protocol family 16
Jul 27 03:50:58 node-4 kernel: [    0.411335] cpuidle: using governor ladder
Jul 27 03:50:58 node-4 kernel: [    0.411337] cpuidle: using governor menu
Jul 27 03:50:58 node-4 kernel: [    0.411371] ACPI: bus type PCI registered
Jul 27 03:50:58 node-4 kernel: [    0.411373] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 27 03:50:58 node-4 kernel: [    0.411420] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 27 03:50:58 node-4 kernel: [    0.411422] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 27 03:50:58 node-4 kernel: [    0.425157] PCI: Using configuration type 1 for base access
Jul 27 03:50:58 node-4 kernel: [    0.426153] bio: create slab <bio-0> at 0
Jul 27 03:50:58 node-4 kernel: [    0.426433] ACPI: Added _OSI(Module Device)
Jul 27 03:50:58 node-4 kernel: [    0.426435] ACPI: Added _OSI(Processor Device)
Jul 27 03:50:58 node-4 kernel: [    0.426436] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 27 03:50:58 node-4 kernel: [    0.426437] ACPI: Added _OSI(Processor Aggregator Device)
Jul 27 03:50:58 node-4 kernel: [    0.439079] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 27 03:50:58 node-4 kernel: [    0.450592] ACPI: Interpreter enabled
Jul 27 03:50:58 node-4 kernel: [    0.450597] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 27 03:50:58 node-4 kernel: [    0.450601] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 27 03:50:58 node-4 kernel: [    0.450604] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 27 03:50:58 node-4 kernel: [    0.450611] ACPI: (supports S0 S4 S5)
Jul 27 03:50:58 node-4 kernel: [    0.450612] ACPI: Using IOAPIC for interrupt routing
Jul 27 03:50:58 node-4 kernel: [    0.450654] HEST: Table parsing has been initialized.
Jul 27 03:50:58 node-4 kernel: [    0.450657] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 27 03:50:58 node-4 kernel: [    0.451208] ACPI: No dock devices found.
Jul 27 03:50:58 node-4 kernel: [    0.462852] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 27 03:50:58 node-4 kernel: [    0.462857] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 03:50:58 node-4 kernel: [    0.462860] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 27 03:50:58 node-4 kernel: [    0.462889] PCI host bridge to bus 0000:ff
Jul 27 03:50:58 node-4 kernel: [    0.462891] pci_bus 0000:ff: root bus resource [bus ff]
Jul 27 03:50:58 node-4 kernel: [    0.462899] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.462939] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 27 03:50:58 node-4 kernel: [    0.462970] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463006] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463035] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 27 03:50:58 node-4 kernel: [    0.463065] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 27 03:50:58 node-4 kernel: [    0.463097] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463127] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463158] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463186] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463213] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463241] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463271] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463299] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463326] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463353] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463381] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463408] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463435] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 27 03:50:58 node-4 kernel: [    0.463463] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463489] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 27 03:50:58 node-4 kernel: [    0.463515] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463541] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463572] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 27 03:50:58 node-4 kernel: [    0.463607] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463639] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463669] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463700] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463733] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463764] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463795] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463825] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463856] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463888] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463919] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463950] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.463982] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464011] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464039] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464071] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464105] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464145] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464181] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464215] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464244] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464274] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464306] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464336] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464367] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464399] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464431] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464461] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464490] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464519] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464549] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464582] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464614] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464672] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 27 03:50:58 node-4 kernel: [    0.464674] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 03:50:58 node-4 kernel: [    0.464677] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 27 03:50:58 node-4 kernel: [    0.464695] PCI host bridge to bus 0000:7f
Jul 27 03:50:58 node-4 kernel: [    0.464697] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 27 03:50:58 node-4 kernel: [    0.464702] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464730] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 27 03:50:58 node-4 kernel: [    0.464758] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464792] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464814] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 27 03:50:58 node-4 kernel: [    0.464840] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 27 03:50:58 node-4 kernel: [    0.464866] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464895] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464920] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464945] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464969] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.464994] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465020] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465042] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465065] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465091] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465112] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465135] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465158] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 27 03:50:58 node-4 kernel: [    0.465182] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465204] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 27 03:50:58 node-4 kernel: [    0.465226] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465248] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465274] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 27 03:50:58 node-4 kernel: [    0.465308] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465335] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465361] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465387] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465412] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465439] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465466] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465494] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465518] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465545] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465573] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465600] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465627] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465651] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465675] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465704] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465729] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465755] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465782] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465810] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465836] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465861] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465887] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465913] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465939] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465965] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.465994] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.466019] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.466041] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.466068] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.466092] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.466121] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.466147] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.467390] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 27 03:50:58 node-4 kernel: [    0.467394] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 03:50:58 node-4 kernel: [    0.468521] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 27 03:50:58 node-4 kernel: [    0.469033] PCI host bridge to bus 0000:00
Jul 27 03:50:58 node-4 kernel: [    0.469036] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 27 03:50:58 node-4 kernel: [    0.469037] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 27 03:50:58 node-4 kernel: [    0.469039] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 27 03:50:58 node-4 kernel: [    0.469040] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 27 03:50:58 node-4 kernel: [    0.469041] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 27 03:50:58 node-4 kernel: [    0.469043] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 27 03:50:58 node-4 kernel: [    0.469044] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 27 03:50:58 node-4 kernel: [    0.469050] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 27 03:50:58 node-4 kernel: [    0.469132] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 27 03:50:58 node-4 kernel: [    0.469163] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 27 03:50:58 node-4 kernel: [    0.469204] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 27 03:50:58 node-4 kernel: [    0.469223] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 27 03:50:58 node-4 kernel: [    0.469252] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 27 03:50:58 node-4 kernel: [    0.469292] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 27 03:50:58 node-4 kernel: [    0.469310] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 27 03:50:58 node-4 kernel: [    0.469340] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 27 03:50:58 node-4 kernel: [    0.469380] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 27 03:50:58 node-4 kernel: [    0.469396] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.469466] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.469542] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.469619] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 27 03:50:58 node-4 kernel: [    0.469624] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 27 03:50:58 node-4 kernel: [    0.469709] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 27 03:50:58 node-4 kernel: [    0.469852] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 27 03:50:58 node-4 kernel: [    0.469869] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 27 03:50:58 node-4 kernel: [    0.469947] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 27 03:50:58 node-4 kernel: [    0.470002] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 27 03:50:58 node-4 kernel: [    0.470025] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 27 03:50:58 node-4 kernel: [    0.470080] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 27 03:50:58 node-4 kernel: [    0.470124] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 27 03:50:58 node-4 kernel: [    0.470152] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 27 03:50:58 node-4 kernel: [    0.470208] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 27 03:50:58 node-4 kernel: [    0.470250] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 27 03:50:58 node-4 kernel: [    0.470275] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 27 03:50:58 node-4 kernel: [    0.470293] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 27 03:50:58 node-4 kernel: [    0.470371] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 27 03:50:58 node-4 kernel: [    0.470420] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 27 03:50:58 node-4 kernel: [    0.470450] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 27 03:50:58 node-4 kernel: [    0.470699] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 27 03:50:58 node-4 kernel: [    0.470705] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 27 03:50:58 node-4 kernel: [    0.470711] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 27 03:50:58 node-4 kernel: [    0.470717] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 27 03:50:58 node-4 kernel: [    0.470724] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 27 03:50:58 node-4 kernel: [    0.470754] pci 0000:01:00.0: supports D1 D2
Jul 27 03:50:58 node-4 kernel: [    0.480906] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 27 03:50:58 node-4 kernel: [    0.480912] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 27 03:50:58 node-4 kernel: [    0.480916] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 27 03:50:58 node-4 kernel: [    0.481178] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 27 03:50:58 node-4 kernel: [    0.481238] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 27 03:50:58 node-4 kernel: [    0.488904] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 27 03:50:58 node-4 kernel: [    0.488906] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:50:58 node-4 kernel: [    0.488908] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 03:50:58 node-4 kernel: [    0.488962] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 27 03:50:58 node-4 kernel: [    0.489030] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 27 03:50:58 node-4 kernel: [    0.489107] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 27 03:50:58 node-4 kernel: [    0.489152] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 27 03:50:58 node-4 kernel: [    0.489155] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:50:58 node-4 kernel: [    0.489157] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 03:50:58 node-4 kernel: [    0.489210] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 27 03:50:58 node-4 kernel: [    0.489332] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 27 03:50:58 node-4 kernel: [    0.489386] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 27 03:50:58 node-4 kernel: [    0.489388] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:50:58 node-4 kernel: [    0.489390] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 03:50:58 node-4 kernel: [    0.489440] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 27 03:50:58 node-4 kernel: [    0.489559] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 27 03:50:58 node-4 kernel: [    0.489601] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 27 03:50:58 node-4 kernel: [    0.489738] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 27 03:50:58 node-4 kernel: [    0.489775] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 27 03:50:58 node-4 kernel: [    0.489897] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 27 03:50:58 node-4 kernel: [    0.489933] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 27 03:50:58 node-4 kernel: [    0.490052] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 27 03:50:58 node-4 kernel: [    0.490092] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 27 03:50:58 node-4 kernel: [    0.490095] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:50:58 node-4 kernel: [    0.490097] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 03:50:58 node-4 kernel: [    0.490155] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 27 03:50:58 node-4 kernel: [    0.490218] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 27 03:50:58 node-4 kernel: [    0.490270] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 27 03:50:58 node-4 kernel: [    0.490311] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 27 03:50:58 node-4 kernel: [    0.490395] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 27 03:50:58 node-4 kernel: [    0.490501] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 27 03:50:58 node-4 kernel: [    0.490503] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:50:58 node-4 kernel: [    0.490505] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 27 03:50:58 node-4 kernel: [    0.490561] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 27 03:50:58 node-4 kernel: [    0.490614] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 27 03:50:58 node-4 kernel: [    0.490663] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 27 03:50:58 node-4 kernel: [    0.490905] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 27 03:50:58 node-4 kernel: [    0.490908] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 27 03:50:58 node-4 kernel: [    0.490971] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 27 03:50:58 node-4 kernel: [    0.491024] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 27 03:50:58 node-4 kernel: [    0.491073] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 27 03:50:58 node-4 kernel: [    0.491282] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 27 03:50:58 node-4 kernel: [    0.491286] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 27 03:50:58 node-4 kernel: [    0.491344] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 27 03:50:58 node-4 kernel: [    0.491404] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 27 03:50:58 node-4 kernel: [    0.491458] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 27 03:50:58 node-4 kernel: [    0.491678] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 27 03:50:58 node-4 kernel: [    0.491681] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 27 03:50:58 node-4 kernel: [    0.491875] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 27 03:50:58 node-4 kernel: [    0.491913] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 27 03:50:58 node-4 kernel: [    0.491989] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 27 03:50:58 node-4 kernel: [    0.492008] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 27 03:50:58 node-4 kernel: [    0.492021] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 27 03:50:58 node-4 kernel: [    0.492034] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 27 03:50:58 node-4 kernel: [    0.492085] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 27 03:50:58 node-4 kernel: [    0.496924] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 27 03:50:58 node-4 kernel: [    0.496928] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 27 03:50:58 node-4 kernel: [    0.496960] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 27 03:50:58 node-4 kernel: [    0.497449] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 27 03:50:58 node-4 kernel: [    0.497452] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 27 03:50:58 node-4 kernel: [    0.497571] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 27 03:50:58 node-4 kernel: [    0.497677] PCI host bridge to bus 0000:80
Jul 27 03:50:58 node-4 kernel: [    0.497679] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 27 03:50:58 node-4 kernel: [    0.497681] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 27 03:50:58 node-4 kernel: [    0.497682] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 27 03:50:58 node-4 kernel: [    0.497690] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.497752] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.497819] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 27 03:50:58 node-4 kernel: [    0.497880] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 27 03:50:58 node-4 kernel: [    0.497885] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 27 03:50:58 node-4 kernel: [    0.497957] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 27 03:50:58 node-4 kernel: [    0.498253] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 27 03:50:58 node-4 kernel: [    0.498285] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 27 03:50:58 node-4 kernel: [    0.498314] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 27 03:50:58 node-4 kernel: [    0.498343] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 27 03:50:58 node-4 kernel: [    0.498372] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 03:50:58 node-4 kernel: [    0.498402] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 03:50:58 node-4 kernel: [    0.498432] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 03:50:58 node-4 kernel: [    0.498461] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 27 03:50:58 node-4 kernel: [    0.498545] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 27 03:50:58 node-4 kernel: [    0.498550] ACPI: \_SB_.UNC1: notify handler is installed
Jul 27 03:50:58 node-4 kernel: [    0.498551] ACPI: \_SB_.UNC0: notify handler is installed
Jul 27 03:50:58 node-4 kernel: [    0.498566] ACPI: \_SB_.PCI0: notify handler is installed
Jul 27 03:50:58 node-4 kernel: [    0.498618] ACPI: \_SB_.PCI1: notify handler is installed
Jul 27 03:50:58 node-4 kernel: [    0.498697] Found 4 acpi root devices
Jul 27 03:50:58 node-4 kernel: [    0.498813] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 27 03:50:58 node-4 kernel: [    0.498815] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 27 03:50:58 node-4 kernel: [    0.498817] vgaarb: loaded
Jul 27 03:50:58 node-4 kernel: [    0.498818] vgaarb: bridge control possible 0000:0c:00.0
Jul 27 03:50:58 node-4 kernel: [    0.498931] SCSI subsystem initialized
Jul 27 03:50:58 node-4 kernel: [    0.498991] libata version 3.00 loaded.
Jul 27 03:50:58 node-4 kernel: [    0.499007] ACPI: bus type USB registered
Jul 27 03:50:58 node-4 kernel: [    0.499017] usbcore: registered new interface driver usbfs
Jul 27 03:50:58 node-4 kernel: [    0.499022] usbcore: registered new interface driver hub
Jul 27 03:50:58 node-4 kernel: [    0.499046] usbcore: registered new device driver usb
Jul 27 03:50:58 node-4 kernel: [    0.499212] PCI: Using ACPI for IRQ routing
Jul 27 03:50:58 node-4 kernel: [    0.502816] PCI: pci_cache_line_size set to 64 bytes
Jul 27 03:50:58 node-4 kernel: [    0.503027] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 27 03:50:58 node-4 kernel: [    0.503028] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 27 03:50:58 node-4 kernel: [    0.503029] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 27 03:50:58 node-4 kernel: [    0.503093] NetLabel: Initializing
Jul 27 03:50:58 node-4 kernel: [    0.503095] NetLabel:  domain hash size = 128
Jul 27 03:50:58 node-4 kernel: [    0.503096] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 27 03:50:58 node-4 kernel: [    0.503106] NetLabel:  unlabeled traffic allowed by default
Jul 27 03:50:58 node-4 kernel: [    0.503161] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 27 03:50:58 node-4 kernel: [    0.503166] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 27 03:50:58 node-4 kernel: [    0.505221] Switched to clocksource hpet
Jul 27 03:50:58 node-4 kernel: [    0.509231] AppArmor: AppArmor Filesystem Enabled
Jul 27 03:50:58 node-4 kernel: [    0.509246] pnp: PnP ACPI init
Jul 27 03:50:58 node-4 kernel: [    0.509252] ACPI: bus type PNP registered
Jul 27 03:50:58 node-4 kernel: [    0.509359] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 27 03:50:58 node-4 kernel: [    0.509367] pnp 00:01: [dma 4]
Jul 27 03:50:58 node-4 kernel: [    0.509378] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 27 03:50:58 node-4 kernel: [    0.509404] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 27 03:50:58 node-4 kernel: [    0.509423] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 27 03:50:58 node-4 kernel: [    0.509440] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 27 03:50:58 node-4 kernel: [    0.509473] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 27 03:50:58 node-4 kernel: [    0.509524] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 27 03:50:58 node-4 kernel: [    0.509527] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 27 03:50:58 node-4 kernel: [    0.509528] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 27 03:50:58 node-4 kernel: [    0.509530] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 27 03:50:58 node-4 kernel: [    0.509531] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 27 03:50:58 node-4 kernel: [    0.509535] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 27 03:50:58 node-4 kernel: [    0.509538] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 27 03:50:58 node-4 kernel: [    0.509539] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 27 03:50:58 node-4 kernel: [    0.509541] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 27 03:50:58 node-4 kernel: [    0.509542] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 27 03:50:58 node-4 kernel: [    0.509544] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 27 03:50:58 node-4 kernel: [    0.509545] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 27 03:50:58 node-4 kernel: [    0.509547] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 27 03:50:58 node-4 kernel: [    0.509549] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 27 03:50:58 node-4 kernel: [    0.509632] pnp 00:07: [dma 0 disabled]
Jul 27 03:50:58 node-4 kernel: [    0.509660] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 27 03:50:58 node-4 kernel: [    0.509734] pnp 00:08: [dma 0 disabled]
Jul 27 03:50:58 node-4 kernel: [    0.509767] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 27 03:50:58 node-4 kernel: [    0.509818] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 27 03:50:58 node-4 kernel: [    0.510161] pnp: PnP ACPI: found 10 devices
Jul 27 03:50:58 node-4 kernel: [    0.510163] ACPI: bus type PNP unregistered
Jul 27 03:50:58 node-4 kernel: [    0.516438] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 27 03:50:58 node-4 kernel: [    0.516441] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 27 03:50:58 node-4 kernel: [    0.516443] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 27 03:50:58 node-4 kernel: [    0.516448] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 27 03:50:58 node-4 kernel: [    0.516449] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:50:58 node-4 kernel: [    0.516464] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 27 03:50:58 node-4 kernel: [    0.516493] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 27 03:50:58 node-4 kernel: [    0.516507] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 27 03:50:58 node-4 kernel: [    0.516536] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 27 03:50:58 node-4 kernel: [    0.516551] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 27 03:50:58 node-4 kernel: [    0.516582] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 27 03:50:58 node-4 kernel: [    0.516597] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 27 03:50:58 node-4 kernel: [    0.516626] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 27 03:50:58 node-4 kernel: [    0.516627] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:50:58 node-4 kernel: [    0.516642] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 03:50:58 node-4 kernel: [    0.516671] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 27 03:50:58 node-4 kernel: [    0.516673] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:50:58 node-4 kernel: [    0.516687] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 27 03:50:58 node-4 kernel: [    0.516731] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 27 03:50:58 node-4 kernel: [    0.516733] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:50:58 node-4 kernel: [    0.516735] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 03:50:58 node-4 kernel: [    0.516739] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 27 03:50:58 node-4 kernel: [    0.516741] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 27 03:50:58 node-4 kernel: [    0.516743] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 27 03:50:58 node-4 kernel: [    0.516747] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 27 03:50:58 node-4 kernel: [    0.516752] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 27 03:50:58 node-4 kernel: [    0.516760] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 27 03:50:58 node-4 kernel: [    0.516763] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 27 03:50:58 node-4 kernel: [    0.516769] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 27 03:50:58 node-4 kernel: [    0.516770] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 27 03:50:58 node-4 kernel: [    0.516771] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 27 03:50:58 node-4 kernel: [    0.516772] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 27 03:50:58 node-4 kernel: [    0.516773] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 27 03:50:58 node-4 kernel: [    0.516774] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 27 03:50:58 node-4 kernel: [    0.516775] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 27 03:50:58 node-4 kernel: [    0.516776] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 27 03:50:58 node-4 kernel: [    0.516777] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 27 03:50:58 node-4 kernel: [    0.516778] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 27 03:50:58 node-4 kernel: [    0.516778] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 27 03:50:58 node-4 kernel: [    0.516779] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 27 03:50:58 node-4 kernel: [    0.516780] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 27 03:50:58 node-4 kernel: [    0.516781] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 27 03:50:58 node-4 kernel: [    0.516782] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 27 03:50:58 node-4 kernel: [    0.516783] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 27 03:50:58 node-4 kernel: [    0.516784] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 27 03:50:58 node-4 kernel: [    0.516785] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 27 03:50:58 node-4 kernel: [    0.516786] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 27 03:50:58 node-4 kernel: [    0.516787] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 27 03:50:58 node-4 kernel: [    0.516787] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 27 03:50:58 node-4 kernel: [    0.516789] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 27 03:50:58 node-4 kernel: [    0.516790] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 27 03:50:58 node-4 kernel: [    0.516791] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 27 03:50:58 node-4 kernel: [    0.516827] NET: Registered protocol family 2
Jul 27 03:50:58 node-4 kernel: [    0.517083] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 27 03:50:58 node-4 kernel: [    0.517418] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 27 03:50:58 node-4 kernel: [    0.517562] TCP: Hash tables configured (established 262144 bind 65536)
Jul 27 03:50:58 node-4 kernel: [    0.517598] TCP: reno registered
Jul 27 03:50:58 node-4 kernel: [    0.517626] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 27 03:50:58 node-4 kernel: [    0.517719] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 27 03:50:58 node-4 kernel: [    0.517864] NET: Registered protocol family 1
Jul 27 03:50:58 node-4 kernel: [    0.553319] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 27 03:50:58 node-4 kernel: [    0.553333] PCI: CLS 64 bytes, default 64
Jul 27 03:50:58 node-4 kernel: [    0.553417] Trying to unpack rootfs image as initramfs...
Jul 27 03:50:58 node-4 kernel: [    0.772598] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 27 03:50:58 node-4 kernel: [    0.772638] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 27 03:50:58 node-4 kernel: [    0.772640] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 27 03:50:58 node-4 kernel: [    0.773067] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:50:58 node-4 kernel: [    0.773074] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:50:58 node-4 kernel: [    0.773078] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:50:58 node-4 kernel: [    0.773084] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:50:58 node-4 kernel: [    0.773094] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:50:58 node-4 kernel: [    0.773105] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:50:58 node-4 kernel: [    0.773115] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:50:58 node-4 kernel: [    0.773124] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:50:58 node-4 kernel: [    0.773132] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:50:58 node-4 kernel: [    0.773141] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:50:58 node-4 kernel: [    0.773147] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:50:58 node-4 kernel: [    0.773153] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:50:58 node-4 kernel: [    0.773160] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:50:58 node-4 kernel: [    0.773169] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:50:58 node-4 kernel: [    0.773177] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:50:58 node-4 kernel: [    0.773184] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 27 03:50:58 node-4 kernel: [    0.773262] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 27 03:50:58 node-4 kernel: [    0.773265] Scanning for low memory corruption every 60 seconds
Jul 27 03:50:58 node-4 kernel: [    0.773672] Initialise system trusted keyring
Jul 27 03:50:58 node-4 kernel: [    0.773725] audit: initializing netlink socket (disabled)
Jul 27 03:50:58 node-4 kernel: [    0.773741] type=2000 audit(1469591420.728:1): initialized
Jul 27 03:50:58 node-4 kernel: [    0.791617] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 27 03:50:58 node-4 kernel: [    0.793117] zbud: loaded
Jul 27 03:50:58 node-4 kernel: [    0.793243] VFS: Disk quotas dquot_6.5.2
Jul 27 03:50:58 node-4 kernel: [    0.793277] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 27 03:50:58 node-4 kernel: [    0.793643] fuse init (API version 7.22)
Jul 27 03:50:58 node-4 kernel: [    0.793699] msgmni has been set to 32768
Jul 27 03:50:58 node-4 kernel: [    0.793751] Key type big_key registered
Jul 27 03:50:58 node-4 kernel: [    0.794257] Key type asymmetric registered
Jul 27 03:50:58 node-4 kernel: [    0.794259] Asymmetric key parser 'x509' registered
Jul 27 03:50:58 node-4 kernel: [    0.794281] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 27 03:50:58 node-4 kernel: [    0.794349] io scheduler noop registered
Jul 27 03:50:58 node-4 kernel: [    0.794351] io scheduler deadline registered (default)
Jul 27 03:50:58 node-4 kernel: [    0.794369] io scheduler cfq registered
Jul 27 03:50:58 node-4 kernel: [    0.794917] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    0.795081] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    0.795200] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    0.795310] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    0.795426] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    0.795519] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    0.795923] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 27 03:50:58 node-4 kernel: [    0.795949] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 27 03:50:58 node-4 kernel: [    0.795965] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 27 03:50:58 node-4 kernel: [    0.795978] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.795980] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.795983] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 27 03:50:58 node-4 kernel: [    0.795988] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.795989] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.795991] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.795993] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.795994] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.795995] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.795997] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.795998] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.795999] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.796001] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.796002] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.796004] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.796006] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 27 03:50:58 node-4 kernel: [    0.796011] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.796013] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 27 03:50:58 node-4 kernel: [    0.796025] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.796028] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 27 03:50:58 node-4 kernel: [    0.796045] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.796046] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 27 03:50:58 node-4 kernel: [    0.796049] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 27 03:50:58 node-4 kernel: [    0.796091] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 27 03:50:58 node-4 kernel: [    0.796097] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 27 03:50:58 node-4 kernel: [    0.796101] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 27 03:50:58 node-4 kernel: [    0.796117] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 27 03:50:58 node-4 kernel: [    0.796157] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 27 03:50:58 node-4 kernel: [    0.796158] vesafb: scrolling: redraw
Jul 27 03:50:58 node-4 kernel: [    0.796160] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 27 03:50:58 node-4 kernel: [    0.816965] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 27 03:50:58 node-4 kernel: [    0.825463] Console: switching to colour frame buffer device 80x30
Jul 27 03:50:58 node-4 kernel: [    0.834133] fb0: VESA VGA frame buffer device
Jul 27 03:50:58 node-4 kernel: [    0.834333] intel_idle: MWAIT substates: 0x2120
Jul 27 03:50:58 node-4 kernel: [    0.834334] intel_idle: v0.4 model 0x3F
Jul 27 03:50:58 node-4 kernel: [    0.834335] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 27 03:50:58 node-4 kernel: [    0.834561] ipmi message handler version 39.2
Jul 27 03:50:58 node-4 kernel: [    0.834827] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 27 03:50:58 node-4 kernel: [    0.835263] ACPI: AC Adapter [P111] (on-line)
Jul 27 03:50:58 node-4 kernel: [    0.840493] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 27 03:50:58 node-4 kernel: [    0.851473] ACPI: Power Button [PWRB]
Jul 27 03:50:58 node-4 kernel: [    0.857233] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 27 03:50:58 node-4 kernel: [    0.869007] ACPI: Power Button [PWRF]
Jul 27 03:50:58 node-4 kernel: [    0.886722] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 27 03:50:58 node-4 kernel: [    0.898343] pstore: Registered erst as persistent store backend
Jul 27 03:50:58 node-4 kernel: [    0.904497] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 27 03:50:58 node-4 kernel: [    0.916395] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 27 03:50:58 node-4 kernel: [    0.943119] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 27 03:50:58 node-4 kernel: [    0.976443] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 27 03:50:58 node-4 kernel: [    0.990469] Linux agpgart interface v0.103
Jul 27 03:50:58 node-4 kernel: [    0.998066] brd: module loaded
Jul 27 03:50:58 node-4 kernel: [    1.005095] loop: module loaded
Jul 27 03:50:58 node-4 kernel: [    1.011790] libphy: Fixed MDIO Bus: probed
Jul 27 03:50:58 node-4 kernel: [    1.018273] tun: Universal TUN/TAP device driver, 1.6
Jul 27 03:50:58 node-4 kernel: [    1.024723] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 27 03:50:58 node-4 kernel: [    1.031239] PPP generic driver version 2.4.2
Jul 27 03:50:58 node-4 kernel: [    1.037624] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 27 03:50:58 node-4 kernel: [    1.044061] ehci-pci: EHCI PCI platform driver
Jul 27 03:50:58 node-4 kernel: [    1.050576] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 27 03:50:58 node-4 kernel: [    1.056970] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 27 03:50:58 node-4 kernel: [    1.069477] ehci-pci 0000:00:1a.0: debug port 2
Jul 27 03:50:58 node-4 kernel: [    1.079683] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 27 03:50:58 node-4 kernel: [    1.079702] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 27 03:50:58 node-4 kernel: [    1.096723] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 27 03:50:58 node-4 kernel: [    1.102785] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 27 03:50:58 node-4 kernel: [    1.108954] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 27 03:50:58 node-4 kernel: [    1.120838] usb usb1: Product: EHCI Host Controller
Jul 27 03:50:58 node-4 kernel: [    1.126859] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 27 03:50:58 node-4 kernel: [    1.132899] usb usb1: SerialNumber: 0000:00:1a.0
Jul 27 03:50:58 node-4 kernel: [    1.138842] hub 1-0:1.0: USB hub found
Jul 27 03:50:58 node-4 kernel: [    1.144592] hub 1-0:1.0: 2 ports detected
Jul 27 03:50:58 node-4 kernel: [    1.150369] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 27 03:50:58 node-4 kernel: [    1.155931] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 27 03:50:58 node-4 kernel: [    1.166775] ehci-pci 0000:00:1d.0: debug port 2
Jul 27 03:50:58 node-4 kernel: [    1.176156] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 27 03:50:58 node-4 kernel: [    1.176159] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 27 03:50:58 node-4 kernel: [    1.192641] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 27 03:50:58 node-4 kernel: [    1.197820] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 27 03:50:58 node-4 kernel: [    1.203098] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 27 03:50:58 node-4 kernel: [    1.213640] usb usb2: Product: EHCI Host Controller
Jul 27 03:50:58 node-4 kernel: [    1.219103] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 27 03:50:58 node-4 kernel: [    1.224627] usb usb2: SerialNumber: 0000:00:1d.0
Jul 27 03:50:58 node-4 kernel: [    1.230152] hub 2-0:1.0: USB hub found
Jul 27 03:50:58 node-4 kernel: [    1.235492] hub 2-0:1.0: 2 ports detected
Jul 27 03:50:58 node-4 kernel: [    1.240782] ehci-platform: EHCI generic platform driver
Jul 27 03:50:58 node-4 kernel: [    1.246014] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 27 03:50:58 node-4 kernel: [    1.251396] ohci-pci: OHCI PCI platform driver
Jul 27 03:50:58 node-4 kernel: [    1.256780] ohci-platform: OHCI generic platform driver
Jul 27 03:50:58 node-4 kernel: [    1.261957] uhci_hcd: USB Universal Host Controller Interface driver
Jul 27 03:50:58 node-4 kernel: [    1.267279] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 27 03:50:58 node-4 kernel: [    1.460418] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 27 03:50:58 node-4 kernel: [    1.628600] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 27 03:50:58 node-4 kernel: [    1.634101] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 27 03:50:58 node-4 kernel: [    1.639741] hub 1-1:1.0: USB hub found
Jul 27 03:50:58 node-4 kernel: [    1.645211] hub 1-1:1.0: 6 ports detected
Jul 27 03:50:58 node-4 kernel: [    1.760158] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 27 03:50:58 node-4 kernel: [    1.768172] tsc: Refined TSC clocksource calibration: 3491.914 MHz
Jul 27 03:50:58 node-4 kernel: [    2.040251] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 27 03:50:58 node-4 kernel: [    2.045783] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 27 03:50:58 node-4 kernel: [    2.051643] hub 2-1:1.0: USB hub found
Jul 27 03:50:58 node-4 kernel: [    2.057363] hub 2-1:1.0: 8 ports detected
Jul 27 03:50:58 node-4 kernel: [    2.308623] i8042: No controller found
Jul 27 03:50:58 node-4 kernel: [    2.314098] mousedev: PS/2 mouse device common for all mice
Jul 27 03:50:58 node-4 kernel: [    2.319660] rtc_cmos 00:02: RTC can wake from S4
Jul 27 03:50:58 node-4 kernel: [    2.325338] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 27 03:50:58 node-4 kernel: [    2.330968] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 27 03:50:58 node-4 kernel: [    2.342028] device-mapper: uevent: version 1.0.3
Jul 27 03:50:58 node-4 kernel: [    2.347641] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 27 03:50:58 node-4 kernel: [    2.358768] ledtrig-cpu: registered to indicate activity on CPUs
Jul 27 03:50:58 node-4 kernel: [    2.364591] TCP: cubic registered
Jul 27 03:50:58 node-4 kernel: [    2.367749] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 27 03:50:58 node-4 kernel: [    2.376400] NET: Registered protocol family 10
Jul 27 03:50:58 node-4 kernel: [    2.382486] NET: Registered protocol family 17
Jul 27 03:50:58 node-4 kernel: [    2.388276] Key type dns_resolver registered
Jul 27 03:50:58 node-4 kernel: [    2.394329] Loading compiled-in X.509 certificates
Jul 27 03:50:58 node-4 kernel: [    2.400616] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 27 03:50:58 node-4 kernel: [    2.412195] registered taskstats version 1
Jul 27 03:50:58 node-4 kernel: [    2.420303] Key type trusted registered
Jul 27 03:50:58 node-4 kernel: [    2.427988] Key type encrypted registered
Jul 27 03:50:58 node-4 kernel: [    2.433506] AppArmor: AppArmor sha1 policy hashing enabled
Jul 27 03:50:58 node-4 kernel: [    2.439094] IMA: No TPM chip found, activating TPM-bypass!
Jul 27 03:50:58 node-4 kernel: [    2.445342] regulator-dummy: disabling
Jul 27 03:50:58 node-4 kernel: [    2.451171]   Magic number: 8:139:817
Jul 27 03:50:58 node-4 kernel: [    2.456595]   hash matches /build/linux-ZqOzIB/linux-3.13.0/drivers/base/power/main.c:504
Jul 27 03:50:58 node-4 kernel: [    2.467693] acpi device:a6: hash matches
Jul 27 03:50:58 node-4 kernel: [    2.473356] rtc_cmos 00:02: setting system clock to 2016-07-27 03:50:22 UTC (1469591422)
Jul 27 03:50:58 node-4 kernel: [    2.486268] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 27 03:50:58 node-4 kernel: [    2.492202] EDD information not available.
Jul 27 03:50:58 node-4 kernel: [    2.498095] PM: Hibernation image not present or could not be loaded.
Jul 27 03:50:58 node-4 kernel: [    2.498954] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 27 03:50:58 node-4 kernel: [    2.504961] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 27 03:50:58 node-4 kernel: [    2.504963] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 27 03:50:58 node-4 kernel: [    2.504964] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 27 03:50:58 node-4 kernel: [    2.504964] usb 2-1.4: Manufacturer: Avocent
Jul 27 03:50:58 node-4 kernel: [    2.504965] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 27 03:50:58 node-4 kernel: [    2.547082] Write protecting the kernel read-only data: 12288k
Jul 27 03:50:58 node-4 kernel: [    2.553428] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 27 03:50:58 node-4 kernel: [    2.566366] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 27 03:50:58 node-4 kernel: [    2.599763] device-mapper: multipath: version 1.6.0 loaded
Jul 27 03:50:58 node-4 kernel: [    2.607771] systemd-udevd[216]: starting version 204
Jul 27 03:50:58 node-4 kernel: [    2.632578] md: linear personality registered for level -1
Jul 27 03:50:58 node-4 kernel: [    2.647672] md: multipath personality registered for level -4
Jul 27 03:50:58 node-4 kernel: [    2.655851] md: raid0 personality registered for level 0
Jul 27 03:50:58 node-4 kernel: [    2.664545] md: raid1 personality registered for level 1
Jul 27 03:50:58 node-4 kernel: [    2.673329] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 27 03:50:58 node-4 kernel: [    2.679882] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 27 03:50:58 node-4 kernel: [    2.686424] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 27 03:50:58 node-4 kernel: [    2.687502] hidraw: raw HID events driver (C) Jiri Kosina
Jul 27 03:50:58 node-4 kernel: [    2.697224] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 27 03:50:58 node-4 kernel: [    2.697239] 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:50:58 node-4 kernel: [    2.697243] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 03:50:58 node-4 kernel: [    2.697516] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.697582] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.697718] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.697844] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.698083] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.714233] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 27 03:50:58 node-4 kernel: [    2.714237] 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:50:58 node-4 kernel: [    2.714238] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 03:50:58 node-4 kernel: [    2.714464] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.714652] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.714794] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.714929] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.715197] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.729294] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 27 03:50:58 node-4 kernel: [    2.729308] 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:50:58 node-4 kernel: [    2.729320] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 03:50:58 node-4 kernel: [    2.729518] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.729619] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.729733] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.729799] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.730044] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.739390] raid6: sse2x1   10631 MB/s
Jul 27 03:50:58 node-4 kernel: [    2.742403] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 27 03:50:58 node-4 kernel: [    2.742444] 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:50:58 node-4 kernel: [    2.742444] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 27 03:50:58 node-4 kernel: [    2.742764] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.742892] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.743008] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.743109] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.743290] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 27 03:50:58 node-4 kernel: [    2.807340] raid6: sse2x2   14068 MB/s
Jul 27 03:50:58 node-4 kernel: [    2.875256] raid6: sse2x4   16554 MB/s
Jul 27 03:50:58 node-4 kernel: [    2.905281] megasas: FW now in Ready state
Jul 27 03:50:58 node-4 kernel: [    2.943169] raid6: avx2x1   18330 MB/s
Jul 27 03:50:58 node-4 kernel: [    3.015111] raid6: avx2x2   18869 MB/s
Jul 27 03:50:58 node-4 kernel: [    3.087040] raid6: avx2x4   21347 MB/s
Jul 27 03:50:58 node-4 kernel: [    3.093063] raid6: using algorithm avx2x4 (21347 MB/s)
Jul 27 03:50:58 node-4 kernel: [    3.099055] raid6: using avx2x2 recovery algorithm
Jul 27 03:50:58 node-4 kernel: [    3.104862] Switched to clocksource tsc
Jul 27 03:50:58 node-4 kernel: [    3.105405] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    3.105601] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    3.105743] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    3.105882] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    3.106022] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    3.106121] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    3.106233] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    3.106419] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    3.106539] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    3.106698] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    3.106835] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    3.107814] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    3.107855] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    3.107892] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    3.107921] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    3.107960] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Jul 27 03:50:58 node-4 kernel: [    3.108109] usbcore: registered new interface driver usbhid
Jul 27 03:50:58 node-4 kernel: [    3.108110] usbhid: USB HID core driver
Jul 27 03:50:58 node-4 kernel: [    3.108122] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 27 03:50:58 node-4 kernel: [    3.133016] xor: automatically using best checksumming function:
Jul 27 03:50:58 node-4 kernel: [    3.133165] 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:50:58 node-4 kernel: [    3.133464] 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:50:58 node-4 kernel: [    3.133552] 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:50:58 node-4 kernel: [    3.134536] 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:50:58 node-4 kernel: [    3.134618] 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:50:58 node-4 kernel: [    3.134705] 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:50:58 node-4 kernel: [    3.250901]    avx       : 36779.000 MB/sec
Jul 27 03:50:58 node-4 kernel: [    3.257808] async_tx: api initialized (async)
Jul 27 03:50:58 node-4 kernel: [    3.267795] md: raid6 personality registered for level 6
Jul 27 03:50:58 node-4 kernel: [    3.274027] md: raid5 personality registered for level 5
Jul 27 03:50:58 node-4 kernel: [    3.280167] md: raid4 personality registered for level 4
Jul 27 03:50:58 node-4 kernel: [    3.289250] md: raid10 personality registered for level 10
Jul 27 03:50:58 node-4 kernel: [    3.343402] multipathd (356): /proc/356/oom_adj is deprecated, please use /proc/356/oom_score_adj instead.
Jul 27 03:50:58 node-4 kernel: [    3.442771] megasas:IOC Init cmd success
Jul 27 03:50:58 node-4 kernel: [    3.470775] megasas: INIT adapter done
Jul 27 03:50:58 node-4 kernel: [    3.570677] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 27 03:50:58 node-4 kernel: [    3.577598] scsi0 : LSI SAS based MegaRAID driver
Jul 27 03:50:58 node-4 kernel: [    3.584990] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 27 03:50:58 node-4 kernel: [    3.603727] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 27 03:50:58 node-4 kernel: [    3.618907] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 27 03:50:58 node-4 kernel: [    3.625417] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 27 03:50:58 node-4 kernel: [    3.638298] sd 0:2:0:0: [sda] Write Protect is off
Jul 27 03:50:58 node-4 kernel: [    3.644544] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 27 03:50:58 node-4 kernel: [    3.644563] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 27 03:50:58 node-4 kernel: [    3.686353]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 27 03:50:58 node-4 kernel: [    3.692846] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 27 03:50:58 node-4 kernel: [    3.819748] random: lvm urandom read with 27 bits of entropy available
Jul 27 03:50:58 node-4 kernel: [    3.930422] bio: create slab <bio-1> at 1
Jul 27 03:50:58 node-4 kernel: [    4.727639] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 03:50:58 node-4 kernel: [    5.390536] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 27 03:50:58 node-4 kernel: [    5.426320] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 27 03:50:58 node-4 kernel: [    5.556219] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 27 03:50:58 node-4 kernel: [    5.598095] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 27 03:50:58 node-4 kernel: [    5.662231] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 03:50:58 node-4 kernel: [    5.765640] random: nonblocking pool is initialized
Jul 27 03:50:58 node-4 kernel: [    5.907237] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 27 03:50:58 node-4 kernel: [    5.951649] XFS (dm-0): Mounting Filesystem
Jul 27 03:50:58 node-4 kernel: [    6.155690] XFS (dm-0): Ending clean mount
Jul 27 03:50:58 node-4 kernel: [    6.210894] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 27 03:50:58 node-4 kernel: [    6.253816] XFS (dm-1): Mounting Filesystem
Jul 27 03:50:58 node-4 kernel: [    6.429667] XFS (dm-1): Ending clean mount
Jul 27 03:50:58 node-4 kernel: [    8.863867] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 27 03:50:58 node-4 kernel: [    8.877545] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 27 03:50:58 node-4 kernel: [    9.001858] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 27 03:50:58 node-4 kernel: [    9.001864] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 27 03:50:58 node-4 kernel: [    9.001868] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 27 03:50:58 node-4 kernel: [    9.001873] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 27 03:50:58 node-4 kernel: [    9.068780] systemd-udevd[774]: starting version 204
Jul 27 03:50:58 node-4 kernel: [    9.289608] IPMI System Interface driver.
Jul 27 03:50:58 node-4 kernel: [    9.289680] ipmi_si: probing via ACPI
Jul 27 03:50:58 node-4 kernel: [    9.289700] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 27 03:50:58 node-4 kernel: [    9.289701] ipmi_si: Adding ACPI-specified kcs state machine
Jul 27 03:50:58 node-4 kernel: [    9.289716] ipmi_si: probing via SMBIOS
Jul 27 03:50:58 node-4 kernel: [    9.289717] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 27 03:50:58 node-4 kernel: [    9.289718] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 27 03:50:58 node-4 kernel: [    9.289719] ipmi_si: probing via SPMI
Jul 27 03:50:58 node-4 kernel: [    9.289720] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 27 03:50:58 node-4 kernel: [    9.289721] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 27 03:50:58 node-4 kernel: [    9.289722] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 27 03:50:58 node-4 kernel: [    9.292878] wmi: Mapper loaded
Jul 27 03:50:58 node-4 kernel: [    9.321723] power_meter ACPI000D:00: Found ACPI power meter.
Jul 27 03:50:58 node-4 kernel: [    9.321739] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 27 03:50:58 node-4 kernel: [    9.389426] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 27 03:50:58 node-4 kernel: [    9.389432] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 27 03:50:58 node-4 kernel: [    9.389435] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 27 03:50:58 node-4 kernel: [    9.389438] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 27 03:50:58 node-4 kernel: [    9.389474] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 27 03:50:58 node-4 kernel: [    9.415413] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 27 03:50:58 node-4 kernel: [    9.430195] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 27 03:50:58 node-4 kernel: [    9.430201] ipmi_si 00:09: IPMI kcs interface initialized
Jul 27 03:50:58 node-4 kernel: [    9.498076] systemd-udevd[793]: renamed network interface eth0 to enp6s0
Jul 27 03:50:58 node-4 kernel: [    9.529989] systemd-udevd[792]: renamed network interface eth1 to enp7s0
Jul 27 03:50:58 node-4 kernel: [    9.541949] systemd-udevd[802]: renamed network interface eth3 to enp9s0
Jul 27 03:50:58 node-4 kernel: [    9.549934] systemd-udevd[795]: renamed network interface eth2 to enp8s0
Jul 27 03:50:58 node-4 kernel: [    9.927066] type=1400 audit(1469591429.955:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1051 comm="apparmor_parser"
Jul 27 03:50:58 node-4 kernel: [    9.927216] type=1400 audit(1469591429.955:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1051 comm="apparmor_parser"
Jul 27 03:50:58 node-4 kernel: [    9.927341] type=1400 audit(1469591429.955:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1051 comm="apparmor_parser"
Jul 27 03:50:58 node-4 kernel: [    9.929358] type=1400 audit(1469591429.959:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1049 comm="apparmor_parser"
Jul 27 03:50:58 node-4 kernel: [    9.929496] type=1400 audit(1469591429.959:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1049 comm="apparmor_parser"
Jul 27 03:50:58 node-4 kernel: [    9.929612] type=1400 audit(1469591429.959:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1049 comm="apparmor_parser"
Jul 27 03:50:58 node-4 kernel: [    9.933114] type=1400 audit(1469591429.959:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1053 comm="apparmor_parser"
Jul 27 03:50:58 node-4 kernel: [    9.933267] type=1400 audit(1469591429.963:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1053 comm="apparmor_parser"
Jul 27 03:50:58 node-4 kernel: [    9.933390] type=1400 audit(1469591429.963:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1053 comm="apparmor_parser"
Jul 27 03:50:58 node-4 kernel: [    9.934135] type=1400 audit(1469591429.963:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1050 comm="apparmor_parser"
Jul 27 03:50:58 node-4 kernel: [   10.484811] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 27 03:50:58 node-4 kernel: [   10.487298] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 27 03:50:58 node-4 kernel: [   10.719597] enic 0000:06:00.0 enp6s0: Link UP
Jul 27 03:50:58 node-4 kernel: [   10.720024] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 27 03:50:58 node-4 kernel: [   10.720031] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 27 03:50:58 node-4 kernel: [   20.566902] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 27 03:50:58 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 27 03:50:59 node-4 failsafe: Failsafe of 120 seconds reached.
Jul 27 03:50:59 node-4 kernel: [   39.586235] init: failsafe main process (8390) killed by TERM signal
Jul 27 03:50:59 node-4 dbus[8423]: [system] AppArmor D-Bus mediation is enabled
Jul 27 03:51:00 node-4 kernel: [   39.774735] audit_printk_skb: 30 callbacks suppressed
Jul 27 03:51:00 node-4 kernel: [   39.774737] type=1400 audit(1469591460.088:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8515 comm="apparmor_parser"
Jul 27 03:51:00 node-4 kernel: [   39.774742] type=1400 audit(1469591460.088:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8515 comm="apparmor_parser"
Jul 27 03:51:00 node-4 kernel: [   39.774744] type=1400 audit(1469591460.088:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8515 comm="apparmor_parser"
Jul 27 03:51:00 node-4 kernel: [   39.774966] type=1400 audit(1469591460.088:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8515 comm="apparmor_parser"
Jul 27 03:51:00 node-4 kernel: [   39.774968] type=1400 audit(1469591460.088:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8515 comm="apparmor_parser"
Jul 27 03:51:00 node-4 kernel: [   39.775082] type=1400 audit(1469591460.088:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8515 comm="apparmor_parser"
Jul 27 03:51:00 node-4 kernel: [   39.780064] type=1400 audit(1469591460.096:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8516 comm="apparmor_parser"
Jul 27 03:51:00 node-4 kernel: [   39.842215] type=1400 audit(1469591460.156:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8518 comm="apparmor_parser"
Jul 27 03:51:00 node-4 cron[8548]: (CRON) INFO (pidfile fd = 3)
Jul 27 03:51:00 node-4 anacron[8570]: Anacron 2.3 started on 2016-07-27
Jul 27 03:51:00 node-4 cron[8584]: (CRON) STARTUP (fork ok)
Jul 27 03:51:00 node-4 anacron[8570]: Will run job `cron.daily' in 5 min.
Jul 27 03:51:00 node-4 anacron[8570]: Will run job `cron.weekly' in 10 min.
Jul 27 03:51:00 node-4 anacron[8570]: Will run job `cron.monthly' in 15 min.
Jul 27 03:51:00 node-4 anacron[8570]: Jobs will be executed sequentially
Jul 27 03:51:00 node-4 multipathd: path checkers start up
Jul 27 03:51:00 node-4 cron[8584]: (CRON) INFO (Running @reboot jobs)
Jul 27 03:51:00 node-4 postfix/master[8727]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 27 03:51:03 node-4 puppet-agent[8911]: Reopening log files
Jul 27 03:51:04 node-4 puppet-agent[8911]: Could not request certificate: Connection refused - connect(2)
Jul 27 03:51:17 node-4 puppet-user[9119]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 27 03:51:17 node-4 puppet-user[9119]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 27 03:51:18 node-4 puppet-user[9119]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 27 03:51:18 node-4 puppet-user[9119]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 27 03:51:18 node-4 puppet-user[9119]: Finished catalog run in 0.49 seconds
Jul 27 03:51:19 node-4 multipathd: uevent trigger error
Jul 27 03:51:19 node-4 puppet-user[9724]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 27 03:51:19 node-4 puppet-user[9724]: Compiled catalog for node-4.domain.tld in environment production in 0.08 seconds
Jul 27 03:51:20 node-4 puppet-user[9724]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 27 03:51:20 node-4 puppet-user[9724]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 27 03:51:20 node-4 puppet-user[9724]: (/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-4 puppet-user[9724]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 27 03:51:20 node-4 puppet-user[9724]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 27 03:51:20 node-4 puppet-user[9724]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 27 03:51:20 node-4 puppet-user[9724]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 27 03:51:20 node-4 puppet-user[9724]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 27 03:51:20 node-4 puppet-user[9724]: Finished catalog run in 0.05 seconds
Jul 27 03:51:21 node-4 puppet-user[10181]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 27 03:51:21 node-4 puppet-user[10181]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Jul 27 03:51:21 node-4 puppet-user[10181]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 27 03:51:21 node-4 puppet-user[10181]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 27 03:51:21 node-4 puppet-user[10181]: Finished catalog run in 0.03 seconds
Jul 27 03:51:22 node-4 puppet-user[10643]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 27 03:51:22 node-4 puppet-user[10643]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 27 03:51:23 node-4 puppet-user[10643]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 27 03:51:23 node-4 puppet-user[10643]: Finished catalog run in 0.04 seconds
Jul 27 03:51:24 node-4 puppet-user[11085]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 27 03:51:24 node-4 puppet-user[11085]: Compiled catalog for node-4.domain.tld in environment production in 0.18 seconds
Jul 27 03:51:24 node-4 puppet-user[11085]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 27 03:51:25 node-4 puppet-user[11085]: (/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-4 puppet-user[11085]: Finished catalog run in 0.45 seconds
Jul 27 03:51:26 node-4 puppet-user[11559]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 27 03:51:26 node-4 puppet-user[11559]: Compiled catalog for node-4.domain.tld in environment production in 0.21 seconds
Jul 27 03:51:26 node-4 puppet-user[11559]: (/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:26 node-4 puppet-user[11559]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 27 03:51:26 node-4 puppet-user[11559]: (/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:26 node-4 puppet-user[11559]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 27 03:51:26 node-4 puppet-user[11559]: Finished catalog run in 0.23 seconds
Jul 27 03:51:28 node-4 puppet-user[12032]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 27 03:51:28 node-4 puppet-user[12032]: Compiled catalog for node-4.domain.tld in environment production in 0.14 seconds
Jul 27 03:51:28 node-4 puppet-user[12032]: (/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:28 node-4 kernel: [   67.985537] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 27 03:51:28 node-4 kernel: [   67.985585] 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:28 node-4 puppet-user[12032]: (/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:28 node-4 puppet-user[12032]: Finished catalog run in 0.05 seconds
Jul 27 03:51:30 node-4 puppet-user[12499]: (Scope(Class[main])) MODULAR: sync_time
Jul 27 03:51:30 node-4 puppet-user[12499]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 27 03:51:30 node-4 ntpdate[12920]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 27 03:51:30 node-4 kernel: [   70.583529] init: plymouth-upstart-bridge main process ended, respawning
Jul 27 03:51:31 node-4 puppet-agent[8911]: Could not run: SIGTERM
Jul 27 03:51:31 node-4 kernel: [   70.840211] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 27 03:51:31 node-4 ec2: 
Jul 27 03:51:31 node-4 ec2: #############################################################
Jul 27 03:51:31 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 27 03:51:31 node-4 ec2: 1024 88:91:86:04:c6:f5:60:79:22:9c:88:25:2f:46:22:c3  root@node-4.domain.tld (DSA)
Jul 27 03:51:31 node-4 ec2: 256 d9:83:f3:72:4c:09:dd:6f:e8:cb:20:ec:39:bc:d1:08  root@node-4.domain.tld (ECDSA)
Jul 27 03:51:31 node-4 ec2: 256 ed:2f:4e:0b:a2:9b:d1:48:0f:98:25:58:95:39:9c:ec  root@node-4.domain.tld (ED25519)
Jul 27 03:51:31 node-4 ec2: 2048 c7:87:74:4f:36:cf:d2:cb:64:6d:26:9f:ec:f1:3b:b1  root@node-4.domain.tld (RSA)
Jul 27 03:51:31 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 27 03:51:31 node-4 ec2: #############################################################
Jul 27 03:51:36 node-4 ntpdate[12920]: adjust time server 10.20.0.2 offset 0.002087 sec
Jul 27 03:51:36 node-4 puppet-user[12499]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 27 03:51:36 node-4 puppet-user[12499]: Finished catalog run in 6.18 seconds
Jul 27 03:51:42 node-4 puppet-user[13277]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 27 03:51:42 node-4 puppet-user[13277]: Compiled catalog for node-4.domain.tld in environment production in 0.08 seconds
Jul 27 03:51:42 node-4 puppet-user[13277]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 27 03:51:42 node-4 puppet-user[13277]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Jul 27 03:51:42 node-4 puppet-user[13277]: Finished catalog run in 0.07 seconds
Jul 27 03:51:43 node-4 puppet-user[13730]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 27 03:51:44 node-4 puppet-user[13730]: Compiled catalog for node-4.domain.tld in environment production in 0.96 seconds
Jul 27 03:51:45 node-4 puppet-user[13730]: (/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-4 puppet-user[13730]: (/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-4 puppet-user[13730]: (/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-4 puppet-user[13730]: (/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-4 puppet-user[13730]: (/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-4 puppet-user[13730]: (/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-4 puppet-user[13730]: (/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-4 puppet-user[13730]: (/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-4 puppet-user[13730]: (/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-4 puppet-user[13730]: (/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-4 puppet-user[13730]: (/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-4 puppet-user[13730]: (/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-4 puppet-user[13730]: (/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-4 puppet-user[13730]: (/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-4 puppet-user[13730]: (/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-4 puppet-user[13730]: (/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:57 node-4 puppet-user[13730]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 27 03:51:57 node-4 puppet-user[13730]: Finished catalog run in 12.70 seconds
Jul 27 03:51:59 node-4 puppet-user[14667]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 27 03:51:59 node-4 puppet-user[14667]: Compiled catalog for node-4.domain.tld in environment production in 0.11 seconds
Jul 27 03:52:01 node-4 CRON[15163]: (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:03 node-4 puppet-user[14667]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 27 03:52:26 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 03:52:26 node-4 nailgun-agent: I, [2016-07-27T03:52:26.607143 #15166]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 27 03:52:33 node-4 puppet-user[14667]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 27 03:52:33 node-4 puppet-user[14667]: Finished catalog run in 34.35 seconds
Jul 27 03:52:35 node-4 puppet-user[17270]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 27 03:52:36 node-4 puppet-user[17270]: Compiled catalog for node-4.domain.tld in environment production in 0.57 seconds
Jul 27 03:52:36 node-4 puppet-user[17270]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 27 03:52:36 node-4 puppet-user[17270]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 27 03:52:36 node-4 puppet-user[17270]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 27 03:52:36 node-4 puppet-user[17270]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 27 03:52:36 node-4 puppet-user[17270]: Finished catalog run in 0.08 seconds
Jul 27 03:52:38 node-4 puppet-user[17728]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 27 03:52:38 node-4 puppet-user[17728]: Compiled catalog for node-4.domain.tld in environment production in 0.79 seconds
Jul 27 03:52:39 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 27 03:52:39 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 27 03:52:39 node-4 crontab[18174]: (root) LIST (root)
Jul 27 03:52:39 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 27 03:52:39 node-4 crontab[18175]: (root) REPLACE (root)
Jul 27 03:52:39 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 27 03:52:39 node-4 nailgun-agent: I, [2016-07-27T03:52:39.821178 #15166]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 27 03:52:41 node-4 puppet-user[17728]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 27 03:52:42 node-4 puppet-user[17728]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/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:43 node-4 puppet-user[17728]: (/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:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/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:43 node-4 puppet-user[17728]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/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:43 node-4 puppet-user[17728]: (/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:43 node-4 puppet-user[17728]: (/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:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/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:43 node-4 puppet-user[17728]: (/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-4 puppet-user[17728]: (/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-4 puppet-user[17728]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/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-4 puppet-user[17728]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/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-4 puppet-user[17728]: (/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-4 puppet-user[17728]: (/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-4 puppet-user[17728]: (/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-4 puppet-user[17728]: (/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-4 puppet-user[17728]: (/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-4 puppet-user[17728]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/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-4 puppet-user[17728]: (/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-4 puppet-user[17728]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/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-4 puppet-user[17728]: (/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-4 puppet-user[17728]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 27 03:52:43 node-4 puppet-user[17728]: (/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-4 puppet-user[17728]: (/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-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8362" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 27 03:52:43 node-4 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-4 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-4 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-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:44 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 27 03:52:44 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 27 03:52:45 node-4 multipathd: uevent trigger error
<27>Jul 27 03:52:45 node-4 multipathd: uevent trigger error
<27>Jul 27 03:52:46 node-4 multipathd: uevent trigger error
<27>Jul 27 03:52:46 node-4 multipathd: uevent trigger error
<27>Jul 27 03:53:04 node-4 multipathd: uevent trigger error
<27>Jul 27 03:53:04 node-4 multipathd: uevent trigger error
<27>Jul 27 03:53:04 node-4 multipathd: uevent trigger error
<27>Jul 27 03:53:04 node-4 multipathd: uevent trigger error
<27>Jul 27 03:53:08 node-4 multipathd: uevent trigger error
<27>Jul 27 03:53:08 node-4 multipathd: uevent trigger error
<27>Jul 27 03:53:08 node-4 multipathd: uevent trigger error
<27>Jul 27 03:53:08 node-4 multipathd: uevent trigger error
<27>Jul 27 03:53:10 node-4 multipathd: uevent trigger error
<27>Jul 27 03:53:10 node-4 multipathd: uevent trigger error
<27>Jul 27 03:53:10 node-4 multipathd: uevent trigger error
<27>Jul 27 03:53:10 node-4 multipathd: uevent trigger error
<27>Jul 27 03:53:10 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:09 node-4 ntpdate[29558]: no servers can be used, exiting
<27>Jul 27 03:54:09 node-4 ntpdate[29800]: no servers can be used, exiting
<27>Jul 27 03:54:41 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:41 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:41 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:41 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:41 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:44 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:44 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:44 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:44 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:56 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:56 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:56 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:56 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:56 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:59 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:59 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:59 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:59 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:59 node-4 multipathd: uevent trigger error
<27>Jul 27 03:54:59 node-4 multipathd: uevent trigger error
<27>Jul 27 03:55:31 node-4 multipathd: uevent trigger error
<27>Jul 27 03:55:31 node-4 multipathd: uevent trigger error
<27>Jul 27 03:55:31 node-4 multipathd: uevent trigger error
<27>Jul 27 03:55:31 node-4 multipathd: uevent trigger error
<27>Jul 27 03:55:37 node-4 multipathd: uevent trigger error
<27>Jul 27 03:55:37 node-4 multipathd: uevent trigger error
<27>Jul 27 03:55:37 node-4 multipathd: uevent trigger error
<27>Jul 27 03:55:37 node-4 multipathd: uevent trigger error
<27>Jul 27 03:55:37 node-4 multipathd: uevent trigger error
<43>Jul 27 03:55:54 node-4 apache2_error [Wed Jul 27 03:55:50.564023 2016] [mpm_event:notice] [pid 12171:tid 140177810556800] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 27 03:55:54 node-4 apache2_error [Wed Jul 27 03:55:50.564160 2016] [core:notice] [pid 12171:tid 140177810556800] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 27 03:55:54 node-4 apache2_error [Wed Jul 27 03:55:53.400679 2016] [mpm_event:notice] [pid 12171:tid 140177810556800] AH00491: caught SIGTERM, shutting down
<27>Jul 27 03:55:58 node-4 multipathd: uevent trigger error
<27>Jul 27 03:55:58 node-4 multipathd: uevent trigger error
<27>Jul 27 03:55:58 node-4 multipathd: uevent trigger error
<27>Jul 27 03:55:58 node-4 multipathd: uevent trigger error
<27>Jul 27 03:55:58 node-4 multipathd: uevent trigger error
<43>Jul 27 03:56:04 node-4 apache2_error [Wed Jul 27 03:55:54.506334 2016] [mpm_worker:notice] [pid 12485:tid 140678768166784] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 27 03:56:04 node-4 apache2_error [Wed Jul 27 03:55:54.506371 2016] [core:notice] [pid 12485:tid 140678768166784] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 27 03:56:34 node-4 apache2_error [Wed Jul 27 03:56:31.910343 2016] [mpm_worker:notice] [pid 12485:tid 140678768166784] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 03:56:34 node-4 apache2_error [Wed Jul 27 03:56:31.917257 2016] [mpm_worker:warn] [pid 12485:tid 140678768166784] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 03:56:34 node-4 apache2_error [Wed Jul 27 03:56:31.918015 2016] [mpm_worker:notice] [pid 12485:tid 140678768166784] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 27 03:56:34 node-4 apache2_error [Wed Jul 27 03:56:31.918027 2016] [core:notice] [pid 12485:tid 140678768166784] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 03:56:34 node-4 multipathd: uevent trigger error
<27>Jul 27 03:56:34 node-4 multipathd: uevent trigger error
<27>Jul 27 03:56:34 node-4 multipathd: uevent trigger error
<27>Jul 27 03:56:34 node-4 multipathd: uevent trigger error
<27>Jul 27 03:56:34 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:09 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 27 03:57:13 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:13 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:13 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:13 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:13 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:16 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:16 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:16 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:16 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:16 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:23 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:23 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:23 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:23 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:23 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:23 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:23 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:30 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:30 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:30 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:30 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:30 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:36 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:36 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:36 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:36 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:36 node-4 multipathd: uevent trigger error
<129>Jul 27 03:57:39 node-4 haproxy[26973]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 27 03:57:41 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:41 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:41 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:41 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:41 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:45 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:45 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:45 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:45 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:45 node-4 multipathd: uevent trigger error
<129>Jul 27 03:57:48 node-4 haproxy[29241]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:57:48 node-4 haproxy[29241]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 27 03:57:50 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:50 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:50 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:50 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:50 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:50 node-4 multipathd: uevent trigger error
<129>Jul 27 03:57:53 node-4 haproxy[30425]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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:53 node-4 haproxy[30425]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:57:54 node-4 haproxy[30425]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 27 03:57:55 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:55 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:55 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:55 node-4 multipathd: uevent trigger error
<27>Jul 27 03:57:55 node-4 multipathd: uevent trigger error
<129>Jul 27 03:57:58 node-4 haproxy[31634]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", 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-4 haproxy[31634]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:57:59 node-4 haproxy[31638]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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:59 node-4 haproxy[31638]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:00 node-4 haproxy[31638]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 27 03:58:01 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:01 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:01 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:01 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:01 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:01 node-4 multipathd: uevent trigger error
<129>Jul 27 03:58:03 node-4 haproxy[376]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", 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-4 haproxy[381]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", 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-4 haproxy[381]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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-4 haproxy[381]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:05 node-4 haproxy[381]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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:05 node-4 haproxy[381]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 27 03:58:06 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:06 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:06 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:06 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:06 node-4 multipathd: uevent trigger error
<129>Jul 27 03:58:07 node-4 haproxy[381]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:07 node-4 haproxy[381]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:07 node-4 haproxy[381]: proxy aodh has no server available!
<129>Jul 27 03:58:09 node-4 haproxy[1606]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:09 node-4 haproxy[1606]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:10 node-4 haproxy[1610]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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:10 node-4 haproxy[1610]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:10 node-4 haproxy[1610]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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:10 node-4 haproxy[1610]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, 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:11 node-4 haproxy[1610]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 27 03:58:12 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:12 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:12 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:12 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:12 node-4 multipathd: uevent trigger error
<129>Jul 27 03:58:12 node-4 haproxy[1610]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:12 node-4 haproxy[1610]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:12 node-4 haproxy[1610]: proxy aodh has no server available!
<129>Jul 27 03:58:12 node-4 haproxy[1610]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:12 node-4 haproxy[1610]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:12 node-4 haproxy[1610]: proxy ceilometer has no server available!
<129>Jul 27 03:58:14 node-4 haproxy[2810]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:14 node-4 haproxy[2810]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:15 node-4 haproxy[2817]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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:15 node-4 haproxy[2817]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:15 node-4 haproxy[2817]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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:16 node-4 haproxy[2817]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, 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:16 node-4 haproxy[2817]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 27 03:58:17 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:17 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:17 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:17 node-4 multipathd: uevent trigger error
<129>Jul 27 03:58:17 node-4 haproxy[2817]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:17 node-4 haproxy[2817]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:17 node-4 haproxy[2817]: proxy aodh has no server available!
<129>Jul 27 03:58:18 node-4 haproxy[2817]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:18 node-4 haproxy[2817]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:18 node-4 haproxy[2817]: proxy ceilometer has no server available!
<129>Jul 27 03:58:20 node-4 haproxy[4020]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:20 node-4 haproxy[4020]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:20 node-4 haproxy[4020]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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:20 node-4 haproxy[4020]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:21 node-4 haproxy[4020]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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:21 node-4 haproxy[4020]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, 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:21 node-4 haproxy[4020]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, 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:21 node-4 haproxy[4020]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:21 node-4 haproxy[4020]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 27 03:58:22 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 27 03:58:22 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:22 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:22 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:22 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:22 node-4 multipathd: uevent trigger error
<129>Jul 27 03:58:23 node-4 haproxy[4020]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:23 node-4 haproxy[4020]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:23 node-4 haproxy[4020]: proxy aodh has no server available!
<129>Jul 27 03:58:23 node-4 haproxy[4020]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:23 node-4 haproxy[4020]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:23 node-4 haproxy[4020]: proxy ceilometer has no server available!
<129>Jul 27 03:58:25 node-4 haproxy[5433]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:25 node-4 haproxy[5433]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:25 node-4 haproxy[5433]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, 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:26 node-4 haproxy[5442]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, 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:26 node-4 haproxy[5442]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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:26 node-4 haproxy[5442]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, 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:26 node-4 haproxy[5442]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:26 node-4 haproxy[5442]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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:27 node-4 haproxy[5442]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, 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:27 node-4 haproxy[5442]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, 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:27 node-4 haproxy[5442]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:27 node-4 haproxy[5442]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 27 03:58:28 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:28 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:28 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:28 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:28 node-4 multipathd: uevent trigger error
<129>Jul 27 03:58:28 node-4 haproxy[5442]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:28 node-4 haproxy[5442]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:28 node-4 haproxy[5442]: proxy glance-registry has no server available!
<129>Jul 27 03:58:28 node-4 haproxy[5442]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:28 node-4 haproxy[5442]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:28 node-4 haproxy[5442]: proxy aodh has no server available!
<129>Jul 27 03:58:29 node-4 haproxy[5442]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:29 node-4 haproxy[5442]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:29 node-4 haproxy[5442]: proxy ceilometer has no server available!
<129>Jul 27 03:58:31 node-4 haproxy[6710]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:31 node-4 haproxy[6710]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:31 node-4 haproxy[6710]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, 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:31 node-4 haproxy[6710]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, 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:31 node-4 haproxy[6710]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, 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:31 node-4 haproxy[6710]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, 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:32 node-4 haproxy[6716]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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:32 node-4 haproxy[6716]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, 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:32 node-4 haproxy[6716]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:32 node-4 haproxy[6716]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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:32 node-4 haproxy[6716]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, 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:32 node-4 haproxy[6716]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, 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:32 node-4 haproxy[6716]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, 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:33 node-4 haproxy[6716]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:33 node-4 haproxy[6716]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 27 03:58:33 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:33 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:33 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:33 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:33 node-4 multipathd: uevent trigger error
<129>Jul 27 03:58:34 node-4 haproxy[6716]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:34 node-4 haproxy[6716]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:34 node-4 haproxy[6716]: proxy glance-registry has no server available!
<129>Jul 27 03:58:34 node-4 haproxy[6716]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:34 node-4 haproxy[6716]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:34 node-4 haproxy[6716]: proxy aodh has no server available!
<129>Jul 27 03:58:34 node-4 haproxy[6716]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:34 node-4 haproxy[6716]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:34 node-4 haproxy[6716]: proxy ceilometer has no server available!
<129>Jul 27 03:58:34 node-4 haproxy[6716]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:34 node-4 haproxy[6716]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:34 node-4 haproxy[6716]: proxy nova-novncproxy has no server available!
<129>Jul 27 03:58:36 node-4 haproxy[8093]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:36 node-4 haproxy[8093]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:36 node-4 haproxy[8093]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, 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:36 node-4 haproxy[8093]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, 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:36 node-4 haproxy[8093]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:37 node-4 haproxy[8097]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, 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:37 node-4 haproxy[8097]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, 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:37 node-4 haproxy[8097]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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:37 node-4 haproxy[8097]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, 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:37 node-4 haproxy[8097]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:37 node-4 haproxy[8097]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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:37 node-4 haproxy[8097]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, 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:38 node-4 haproxy[8097]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, 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:38 node-4 haproxy[8097]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, 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:38 node-4 haproxy[8097]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:38 node-4 haproxy[8097]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 27 03:58:39 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:39 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:39 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:39 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:39 node-4 multipathd: uevent trigger error
<129>Jul 27 03:58:39 node-4 haproxy[8097]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:39 node-4 haproxy[8097]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:39 node-4 haproxy[8097]: proxy glance-registry has no server available!
<129>Jul 27 03:58:39 node-4 haproxy[8097]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:39 node-4 haproxy[8097]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:39 node-4 haproxy[8097]: proxy aodh has no server available!
<129>Jul 27 03:58:39 node-4 haproxy[8097]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:39 node-4 haproxy[8097]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:39 node-4 haproxy[8097]: proxy ceilometer has no server available!
<129>Jul 27 03:58:40 node-4 haproxy[8097]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:40 node-4 haproxy[8097]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:40 node-4 haproxy[8097]: proxy nova-novncproxy has no server available!
<129>Jul 27 03:58:42 node-4 haproxy[9443]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:42 node-4 haproxy[9443]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:42 node-4 haproxy[9443]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, 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:42 node-4 haproxy[9443]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, 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:42 node-4 haproxy[9443]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:42 node-4 haproxy[9443]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, 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:42 node-4 haproxy[9443]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, 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:42 node-4 haproxy[9443]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, 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:43 node-4 haproxy[9447]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, 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:43 node-4 haproxy[9447]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:43 node-4 haproxy[9447]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, 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:43 node-4 haproxy[9447]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, 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:43 node-4 haproxy[9447]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, 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:43 node-4 haproxy[9447]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, 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:43 node-4 haproxy[9447]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, 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:43 node-4 haproxy[9447]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, 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:43 node-4 haproxy[9447]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, 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:44 node-4 haproxy[9447]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:44 node-4 haproxy[9447]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:44 node-4 haproxy[9447]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 27 03:58:44 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:44 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:45 node-4 multipathd: uevent trigger error
<129>Jul 27 03:58:45 node-4 haproxy[9447]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:45 node-4 haproxy[9447]: proxy glance-registry has no server available!
<27>Jul 27 03:58:45 node-4 multipathd: uevent trigger error
<129>Jul 27 03:58:45 node-4 haproxy[9447]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:45 node-4 haproxy[9447]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:45 node-4 haproxy[9447]: proxy aodh has no server available!
<129>Jul 27 03:58:45 node-4 haproxy[9447]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:45 node-4 haproxy[9447]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:45 node-4 haproxy[9447]: proxy ceilometer has no server available!
<129>Jul 27 03:58:45 node-4 haproxy[9447]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:45 node-4 haproxy[9447]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:45 node-4 haproxy[9447]: proxy nova-novncproxy has no server available!
<27>Jul 27 03:58:48 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:48 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:48 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:48 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:48 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:51 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:51 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:51 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:51 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:51 node-4 multipathd: uevent trigger error
<129>Jul 27 03:58:52 node-4 haproxy[9447]: Server keystone-1/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:52 node-4 haproxy[9447]: Server keystone-1/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:52 node-4 haproxy[9447]: proxy keystone-1 has no server available!
<129>Jul 27 03:58:52 node-4 haproxy[9447]: Server keystone-2/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:52 node-4 haproxy[9447]: Server keystone-2/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:52 node-4 haproxy[9447]: proxy keystone-2 has no server available!
<129>Jul 27 03:58:52 node-4 haproxy[9447]: Server nova-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:52 node-4 haproxy[9447]: Server nova-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:52 node-4 haproxy[9447]: proxy nova-api has no server available!
<129>Jul 27 03:58:52 node-4 haproxy[9447]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:52 node-4 haproxy[9447]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:52 node-4 haproxy[9447]: proxy nova-metadata-api has no server available!
<129>Jul 27 03:58:52 node-4 haproxy[9447]: Server cinder-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:52 node-4 haproxy[9447]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:52 node-4 haproxy[9447]: proxy cinder-api has no server available!
<129>Jul 27 03:58:52 node-4 haproxy[9447]: Server glance-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:52 node-4 haproxy[9447]: Server glance-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:52 node-4 haproxy[9447]: proxy glance-api has no server available!
<129>Jul 27 03:58:52 node-4 haproxy[9447]: Server glance-glare/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:52 node-4 haproxy[9447]: Server glance-glare/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:52 node-4 haproxy[9447]: proxy glance-glare has no server available!
<129>Jul 27 03:58:52 node-4 haproxy[9447]: Server neutron/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:52 node-4 haproxy[9447]: Server neutron/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:52 node-4 haproxy[9447]: proxy neutron has no server available!
<129>Jul 27 03:58:53 node-4 haproxy[9447]: Server mysqld/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:53 node-4 haproxy[9447]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:53 node-4 haproxy[9447]: proxy mysqld has no server available!
<129>Jul 27 03:58:53 node-4 haproxy[9447]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:53 node-4 haproxy[9447]: Server object-storage/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:53 node-4 haproxy[9447]: proxy object-storage has no server available!
<129>Jul 27 03:58:53 node-4 haproxy[9447]: Server heat-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:53 node-4 haproxy[9447]: Server heat-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:53 node-4 haproxy[9447]: proxy heat-api has no server available!
<129>Jul 27 03:58:53 node-4 haproxy[9447]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:53 node-4 haproxy[9447]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:53 node-4 haproxy[9447]: proxy heat-api-cfn has no server available!
<129>Jul 27 03:58:53 node-4 haproxy[9447]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 27 03:58:53 node-4 haproxy[9447]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 27 03:58:53 node-4 haproxy[9447]: proxy heat-api-cloudwatch has no server available!
<27>Jul 27 03:58:55 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:55 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:55 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:55 node-4 multipathd: uevent trigger error
<27>Jul 27 03:58:55 node-4 multipathd: uevent trigger error
<27>Jul 27 03:59:13 node-4 multipathd: uevent trigger error
<27>Jul 27 03:59:19 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 27 03:59:19 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 27 03:59:47 node-4 multipathd: uevent trigger error
<27>Jul 27 03:59:47 node-4 multipathd: uevent trigger error
<27>Jul 27 03:59:47 node-4 multipathd: uevent trigger error
<27>Jul 27 03:59:47 node-4 multipathd: uevent trigger error
<27>Jul 27 03:59:47 node-4 multipathd: uevent trigger error
<27>Jul 27 04:00:02 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 27 04:00:23 node-4 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 04:00:25 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 27 04:02:04 node-4 multipathd: uevent trigger error
<27>Jul 27 04:02:04 node-4 multipathd: uevent trigger error
<27>Jul 27 04:02:04 node-4 multipathd: uevent trigger error
<27>Jul 27 04:02:04 node-4 multipathd: uevent trigger error
<27>Jul 27 04:02:04 node-4 multipathd: uevent trigger error
<27>Jul 27 04:05:25 node-4 multipathd: uevent trigger error
<27>Jul 27 04:05:25 node-4 multipathd: uevent trigger error
<27>Jul 27 04:05:25 node-4 multipathd: uevent trigger error
<27>Jul 27 04:05:25 node-4 multipathd: uevent trigger error
<27>Jul 27 04:05:25 node-4 multipathd: uevent trigger error
<43>Jul 27 04:06:35 node-4 apache2_error [Wed Jul 27 04:06:32.453255 2016] [mpm_worker:notice] [pid 12485:tid 140678768166784] AH00295: caught SIGTERM, shutting down
<43>Jul 27 04:06:35 node-4 apache2_error [Wed Jul 27 04:06:33.201648 2016] [mpm_worker:notice] [pid 11565:tid 140299015985024] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 04:06:35 node-4 apache2_error [Wed Jul 27 04:06:33.201692 2016] [core:notice] [pid 11565:tid 140299015985024] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 04:07:12 node-4 multipathd: uevent trigger error
<27>Jul 27 04:07:12 node-4 multipathd: uevent trigger error
<27>Jul 27 04:07:12 node-4 multipathd: uevent trigger error
<27>Jul 27 04:07:12 node-4 multipathd: uevent trigger error
<27>Jul 27 04:07:12 node-4 multipathd: uevent trigger error
<27>Jul 27 04:07:12 node-4 multipathd: uevent trigger error
<43>Jul 27 04:07:15 node-4 apache2_error [Wed Jul 27 04:07:05.196106 2016] [mpm_worker:notice] [pid 11565:tid 140299015985024] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 04:07:15 node-4 apache2_error [Wed Jul 27 04:07:05.209182 2016] [mpm_worker:warn] [pid 11565:tid 140299015985024] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 04:07:15 node-4 apache2_error [Wed Jul 27 04:07:05.212815 2016] [mpm_worker:notice] [pid 11565:tid 140299015985024] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 04:07:15 node-4 apache2_error [Wed Jul 27 04:07:05.212845 2016] [core:notice] [pid 11565:tid 140299015985024] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 04:08:10 node-4 multipathd: uevent trigger error
<27>Jul 27 04:08:10 node-4 multipathd: uevent trigger error
<27>Jul 27 04:08:10 node-4 multipathd: uevent trigger error
<27>Jul 27 04:08:10 node-4 multipathd: uevent trigger error
<27>Jul 27 04:08:10 node-4 multipathd: uevent trigger error
<27>Jul 27 04:09:21 node-4 multipathd: uevent trigger error
<27>Jul 27 04:09:21 node-4 multipathd: uevent trigger error
<27>Jul 27 04:09:21 node-4 multipathd: uevent trigger error
<27>Jul 27 04:09:21 node-4 multipathd: uevent trigger error
<27>Jul 27 04:09:21 node-4 multipathd: uevent trigger error
<27>Jul 27 04:09:21 node-4 multipathd: uevent trigger error
<27>Jul 27 04:14:15 node-4 multipathd: uevent trigger error
<27>Jul 27 04:14:15 node-4 multipathd: uevent trigger error
<27>Jul 27 04:14:15 node-4 multipathd: uevent trigger error
<27>Jul 27 04:14:15 node-4 multipathd: uevent trigger error
<27>Jul 27 04:14:15 node-4 multipathd: uevent trigger error
<27>Jul 27 04:14:15 node-4 multipathd: uevent trigger error
<27>Jul 27 04:16:20 node-4 multipathd: uevent trigger error
<27>Jul 27 04:16:20 node-4 multipathd: uevent trigger error
<27>Jul 27 04:16:20 node-4 multipathd: uevent trigger error
<27>Jul 27 04:16:20 node-4 multipathd: uevent trigger error
<27>Jul 27 04:16:20 node-4 multipathd: uevent trigger error
<27>Jul 27 04:17:30 node-4 multipathd: uevent trigger error
<27>Jul 27 04:17:30 node-4 multipathd: uevent trigger error
<27>Jul 27 04:17:30 node-4 multipathd: uevent trigger error
<27>Jul 27 04:17:30 node-4 multipathd: uevent trigger error
<27>Jul 27 04:17:30 node-4 multipathd: uevent trigger error
<27>Jul 27 04:17:30 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:06 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:06 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:06 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:07 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:07 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:07 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:16 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:16 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:16 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:16 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:16 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:21 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:21 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:21 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:21 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:21 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:21 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:27 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:27 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:27 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:27 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:27 node-4 multipathd: uevent trigger error
<27>Jul 27 04:18:27 node-4 multipathd: uevent trigger error
<43>Jul 27 04:19:15 node-4 apache2_error [Wed Jul 27 04:19:14.945093 2016] [mpm_worker:notice] [pid 11565:tid 140299015985024] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 04:19:15 node-4 apache2_error [Wed Jul 27 04:19:15.331696 2016] [mpm_worker:warn] [pid 11565:tid 140299015985024] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 04:19:15 node-4 apache2_error [Wed Jul 27 04:19:15.337299 2016] [mpm_worker:notice] [pid 11565:tid 140299015985024] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 04:19:15 node-4 apache2_error [Wed Jul 27 04:19:15.337359 2016] [core:notice] [pid 11565:tid 140299015985024] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 27 04:19:55 node-4 apache2_error [Wed Jul 27 04:19:52.558520 2016] [mpm_worker:notice] [pid 11565:tid 140299015985024] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 27 04:19:55 node-4 apache2_error [Wed Jul 27 04:19:52.941229 2016] [mpm_worker:warn] [pid 11565:tid 140299015985024] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 27 04:19:55 node-4 apache2_error [Wed Jul 27 04:19:52.951516 2016] [mpm_worker:notice] [pid 11565:tid 140299015985024] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 27 04:19:55 node-4 apache2_error [Wed Jul 27 04:19:52.951553 2016] [core:notice] [pid 11565:tid 140299015985024] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 27 04:19:56 node-4 multipathd: uevent trigger error
<27>Jul 27 04:19:56 node-4 multipathd: uevent trigger error
<27>Jul 27 04:19:56 node-4 multipathd: uevent trigger error
<27>Jul 27 04:19:56 node-4 multipathd: uevent trigger error
<27>Jul 27 04:19:56 node-4 multipathd: uevent trigger error
<27>Jul 27 04:20:30 node-4 multipathd: uevent trigger error
<27>Jul 27 04:20:30 node-4 multipathd: uevent trigger error
<27>Jul 27 04:20:30 node-4 multipathd: uevent trigger error
<27>Jul 27 04:20:30 node-4 multipathd: uevent trigger error
<27>Jul 27 04:20:35 node-4 multipathd: uevent trigger error
<27>Jul 27 04:20:35 node-4 multipathd: uevent trigger error
<27>Jul 27 04:20:35 node-4 multipathd: uevent trigger error
<27>Jul 27 04:20:35 node-4 multipathd: uevent trigger error
<27>Jul 27 04:20:35 node-4 multipathd: uevent trigger error
<27>Jul 27 04:21:55 node-4 multipathd: uevent trigger error
<27>Jul 27 04:21:55 node-4 multipathd: uevent trigger error
<27>Jul 27 04:21:55 node-4 multipathd: uevent trigger error
<27>Jul 27 04:21:55 node-4 multipathd: uevent trigger error
<27>Jul 27 04:21:55 node-4 multipathd: uevent trigger error
<27>Jul 27 04:22:43 node-4 multipathd: uevent trigger error
<27>Jul 27 04:22:43 node-4 multipathd: uevent trigger error
<27>Jul 27 04:22:43 node-4 multipathd: uevent trigger error
<27>Jul 27 04:22:43 node-4 multipathd: uevent trigger error
<27>Jul 27 04:22:43 node-4 multipathd: uevent trigger error
<27>Jul 27 04:22:56 node-4 multipathd: uevent trigger error
<27>Jul 27 04:22:56 node-4 multipathd: uevent trigger error
<27>Jul 27 04:22:56 node-4 multipathd: uevent trigger error
<27>Jul 27 04:22:56 node-4 multipathd: uevent trigger error
<11>Jul 27 04:23:05 node-4 liberasurecode[31859]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:05 node-4 liberasurecode[31859]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:05 node-4 liberasurecode[31859]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:05 node-4 liberasurecode[31859]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:05 node-4 liberasurecode[31883]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:05 node-4 liberasurecode[31883]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:05 node-4 liberasurecode[31883]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:05 node-4 liberasurecode[31883]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:08 node-4 liberasurecode[752]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:08 node-4 liberasurecode[752]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:08 node-4 liberasurecode[752]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:08 node-4 liberasurecode[752]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:13 node-4 liberasurecode[2228]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:13 node-4 liberasurecode[2228]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:13 node-4 liberasurecode[2228]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:13 node-4 liberasurecode[2228]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:13 node-4 liberasurecode[2269]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:13 node-4 liberasurecode[2269]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:13 node-4 liberasurecode[2269]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:13 node-4 liberasurecode[2269]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:13 node-4 liberasurecode[2309]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:13 node-4 liberasurecode[2309]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:13 node-4 liberasurecode[2309]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:13 node-4 liberasurecode[2309]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:14 node-4 liberasurecode[2374]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:14 node-4 liberasurecode[2374]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:14 node-4 liberasurecode[2374]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:14 node-4 liberasurecode[2374]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:14 node-4 liberasurecode[2386]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:14 node-4 liberasurecode[2386]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:14 node-4 liberasurecode[2386]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:14 node-4 liberasurecode[2386]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:14 node-4 liberasurecode[2398]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:14 node-4 liberasurecode[2398]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:14 node-4 liberasurecode[2398]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:14 node-4 liberasurecode[2398]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:14 node-4 liberasurecode[2416]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:14 node-4 liberasurecode[2416]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:14 node-4 liberasurecode[2416]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:23:14 node-4 liberasurecode[2416]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 27 04:23:20 node-4 multipathd: uevent trigger error
<27>Jul 27 04:23:20 node-4 multipathd: uevent trigger error
<27>Jul 27 04:23:20 node-4 multipathd: uevent trigger error
<27>Jul 27 04:23:20 node-4 multipathd: uevent trigger error
<27>Jul 27 04:23:25 node-4 multipathd: uevent trigger error
<27>Jul 27 04:23:25 node-4 multipathd: uevent trigger error
<27>Jul 27 04:23:25 node-4 multipathd: uevent trigger error
<27>Jul 27 04:23:25 node-4 multipathd: uevent trigger error
<27>Jul 27 04:23:25 node-4 multipathd: uevent trigger error
<27>Jul 27 04:24:32 node-4 multipathd: uevent trigger error
<27>Jul 27 04:24:32 node-4 multipathd: uevent trigger error
<27>Jul 27 04:24:32 node-4 multipathd: uevent trigger error
<27>Jul 27 04:24:32 node-4 multipathd: uevent trigger error
<11>Jul 27 04:25:01 node-4 liberasurecode[20238]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:25:01 node-4 liberasurecode[20238]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:25:01 node-4 liberasurecode[20238]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:25:01 node-4 liberasurecode[20238]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 27 04:26:34 node-4 multipathd: uevent trigger error
<27>Jul 27 04:26:34 node-4 multipathd: uevent trigger error
<27>Jul 27 04:26:34 node-4 multipathd: uevent trigger error
<27>Jul 27 04:26:34 node-4 multipathd: uevent trigger error
<27>Jul 27 04:26:34 node-4 multipathd: uevent trigger error
<27>Jul 27 04:26:39 node-4 multipathd: uevent trigger error
<27>Jul 27 04:26:39 node-4 multipathd: uevent trigger error
<27>Jul 27 04:26:39 node-4 multipathd: uevent trigger error
<27>Jul 27 04:26:39 node-4 multipathd: uevent trigger error
<27>Jul 27 04:26:53 node-4 multipathd: uevent trigger error
<27>Jul 27 04:26:53 node-4 multipathd: uevent trigger error
<27>Jul 27 04:26:53 node-4 multipathd: uevent trigger error
<27>Jul 27 04:26:53 node-4 multipathd: uevent trigger error
<27>Jul 27 04:26:53 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:06 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:06 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:06 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:06 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:10 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:10 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:10 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:10 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:10 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:23 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:23 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:23 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:23 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:23 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:27 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:27 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:27 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:27 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:31 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:31 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:31 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:31 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:31 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:31 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:35 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:35 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:35 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:35 node-4 multipathd: uevent trigger error
<27>Jul 27 04:27:35 node-4 multipathd: uevent trigger error
<27>Jul 27 04:28:17 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 27 04:28:17 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<11>Jul 27 04:30:02 node-4 liberasurecode[3305]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:30:02 node-4 liberasurecode[3305]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:30:02 node-4 liberasurecode[3305]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 27 04:30:02 node-4 liberasurecode[3305]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
