Sep 14 13:55:04 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8390" x-info="http://www.rsyslog.com"] start
Sep 14 13:55:04 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 14 13:55:04 node-4 rsyslogd: rsyslogd's groupid changed to 104
Sep 14 13:55:04 node-4 rsyslogd: rsyslogd's userid changed to 101
Sep 14 13:55:04 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 14 13:55:04 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 14 13:55:04 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 14 13:55:04 node-4 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep 14 13:55:04 node-4 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=894096ce-84e3-440c-8ee2-821ac3bb600c nomdmonddf nomdmonisw
Sep 14 13:55:04 node-4 kernel: [    0.000000] KERNEL supported cpus:
Sep 14 13:55:04 node-4 kernel: [    0.000000]   Intel GenuineIntel
Sep 14 13:55:04 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Sep 14 13:55:04 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Sep 14 13:55:04 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 14 13:55:04 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 14 13:55:04 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 14 13:55:04 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 14 13:55:04 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 14 13:55:04 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 14 13:55:04 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 14 13:55:04 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 14 13:55:04 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 14 13:55:04 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 14 13:55:04 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 14 13:55:04 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 14 13:55:04 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 14 13:55:04 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 14 13:55:04 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 14 13:55:04 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 14 13:55:04 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 14 13:55:04 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 14 13:55:04 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
Sep 14 13:55:04 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 14 13:55:04 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 14 13:55:04 node-4 kernel: [    0.000000] No AGP bridge found
Sep 14 13:55:04 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 14 13:55:04 node-4 kernel: [    0.000000] MTRR default type: write-back
Sep 14 13:55:04 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 14 13:55:04 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Sep 14 13:55:04 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 14 13:55:04 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 14 13:55:04 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 14 13:55:04 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 14 13:55:04 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 14 13:55:04 node-4 kernel: [    0.000000]   2 disabled
Sep 14 13:55:04 node-4 kernel: [    0.000000]   3 disabled
Sep 14 13:55:04 node-4 kernel: [    0.000000]   4 disabled
Sep 14 13:55:04 node-4 kernel: [    0.000000]   5 disabled
Sep 14 13:55:04 node-4 kernel: [    0.000000]   6 disabled
Sep 14 13:55:04 node-4 kernel: [    0.000000]   7 disabled
Sep 14 13:55:04 node-4 kernel: [    0.000000]   8 disabled
Sep 14 13:55:04 node-4 kernel: [    0.000000]   9 disabled
Sep 14 13:55:04 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 14 13:55:04 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 14 13:55:04 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 14 13:55:04 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 14 13:55:04 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 14 13:55:04 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Sep 14 13:55:04 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 14 13:55:04 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 14 13:55:04 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 14 13:55:04 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 14 13:55:04 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 14 13:55:04 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 14 13:55:04 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 14 13:55:04 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 14 13:55:04 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 14 13:55:04 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 14 13:55:04 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 14 13:55:04 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 14 13:55:04 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 14 13:55:04 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 14 13:55:04 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 14 13:55:04 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 14 13:55:04 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 14 13:55:04 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 14 13:55:04 node-4 kernel: [    0.000000] Zone ranges:
Sep 14 13:55:04 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] Movable zone start for each node
Sep 14 13:55:04 node-4 kernel: [    0.000000] Early memory node ranges
Sep 14 13:55:04 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 14 13:55:04 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 14 13:55:04 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 14 13:55:04 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 14 13:55:04 node-4 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 14 13:55:04 node-4 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 14 13:55:04 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 14 13:55:04 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 14 13:55:04 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 14 13:55:04 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 14 13:55:04 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 14 13:55:04 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 14 13:55:04 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 14 13:55:04 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 14 13:55:04 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 14 13:55:04 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 14 13:55:04 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 14 13:55:04 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 14 13:55:04 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 14 13:55:04 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 14 13:55:04 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 14 13:55:04 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 14 13:55:04 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 14 13:55:04 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 14 13:55:04 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 
Sep 14 13:55:04 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 14 13:55:04 node-4 kernel: [    0.000000] Policy zone: Normal
Sep 14 13:55:04 node-4 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=894096ce-84e3-440c-8ee2-821ac3bb600c nomdmonddf nomdmonisw
Sep 14 13:55:04 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 14 13:55:04 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 14 13:55:04 node-4 kernel: [    0.000000] Checking aperture...
Sep 14 13:55:04 node-4 kernel: [    0.000000] No AGP bridge found
Sep 14 13:55:04 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 14 13:55:04 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 14 13:55:04 node-4 kernel: [    0.000000] Memory: 32653312K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Sep 14 13:55:04 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 14 13:55:04 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 14 13:55:04 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 14 13:55:04 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 14 13:55:04 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 14 13:55:04 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 14 13:55:04 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 14 13:55:04 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 14 13:55:04 node-4 kernel: [    0.000000] console [tty0] enabled
Sep 14 13:55:04 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 14 13:55:04 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 14 13:55:04 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 14 13:55:04 node-4 kernel: [    0.000000] hpet clockevent registered
Sep 14 13:55:04 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 14 13:55:04 node-4 kernel: [    0.004000] tsc: Detected 3491.839 MHz processor
Sep 14 13:55:04 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.67 BogoMIPS (lpj=13967356)
Sep 14 13:55:04 node-4 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 14 13:55:04 node-4 kernel: [    0.000045] Security Framework initialized
Sep 14 13:55:04 node-4 kernel: [    0.000064] AppArmor: AppArmor initialized
Sep 14 13:55:04 node-4 kernel: [    0.000066] Yama: becoming mindful.
Sep 14 13:55:04 node-4 kernel: [    0.001455] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 14 13:55:04 node-4 kernel: [    0.006358] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 14 13:55:04 node-4 kernel: [    0.008284] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 14 13:55:04 node-4 kernel: [    0.008312] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 14 13:55:04 node-4 kernel: [    0.008604] Initializing cgroup subsys memory
Sep 14 13:55:04 node-4 kernel: [    0.008613] Initializing cgroup subsys devices
Sep 14 13:55:04 node-4 kernel: [    0.008614] Initializing cgroup subsys freezer
Sep 14 13:55:04 node-4 kernel: [    0.008616] Initializing cgroup subsys blkio
Sep 14 13:55:04 node-4 kernel: [    0.008618] Initializing cgroup subsys perf_event
Sep 14 13:55:04 node-4 kernel: [    0.008620] Initializing cgroup subsys hugetlb
Sep 14 13:55:04 node-4 kernel: [    0.008639] CPU: Physical Processor ID: 0
Sep 14 13:55:04 node-4 kernel: [    0.008641] CPU: Processor Core ID: 0
Sep 14 13:55:04 node-4 kernel: [    0.008644] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 14 13:55:04 node-4 kernel: [    0.008644] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 14 13:55:04 node-4 kernel: [    0.009339] mce: CPU supports 22 MCE banks
Sep 14 13:55:04 node-4 kernel: [    0.009366] CPU0: Thermal monitoring enabled (TM1)
Sep 14 13:55:04 node-4 kernel: [    0.009387] process: using mwait in idle threads
Sep 14 13:55:04 node-4 kernel: [    0.009389] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 14 13:55:04 node-4 kernel: [    0.009389] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 14 13:55:04 node-4 kernel: [    0.009389] tlb_flushall_shift: 6
Sep 14 13:55:04 node-4 kernel: [    0.009479] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 14 13:55:04 node-4 kernel: [    0.010204] ACPI: Core revision 20131115
Sep 14 13:55:04 node-4 kernel: [    0.022889] ACPI: All ACPI Tables successfully acquired
Sep 14 13:55:04 node-4 kernel: [    0.023051] ftrace: allocating 28617 entries in 112 pages
Sep 14 13:55:04 node-4 kernel: [    0.032023] dmar: Host address width 46
Sep 14 13:55:04 node-4 kernel: [    0.032025] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 14 13:55:04 node-4 kernel: [    0.032031] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 14 13:55:04 node-4 kernel: [    0.032033] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 14 13:55:04 node-4 kernel: [    0.032037] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 14 13:55:04 node-4 kernel: [    0.032038] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 14 13:55:04 node-4 kernel: [    0.032040] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 14 13:55:04 node-4 kernel: [    0.032041] dmar: ATSR flags: 0x0
Sep 14 13:55:04 node-4 kernel: [    0.032042] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 14 13:55:04 node-4 kernel: [    0.032043] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 14 13:55:04 node-4 kernel: [    0.032158] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 14 13:55:04 node-4 kernel: [    0.032159] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 14 13:55:04 node-4 kernel: [    0.032160] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 14 13:55:04 node-4 kernel: [    0.032161] HPET id 0 under DRHD base 0xc7ffc000
Sep 14 13:55:04 node-4 kernel: [    0.032162] Your BIOS is broken and requested that x2apic be disabled.
Sep 14 13:55:04 node-4 kernel: [    0.032162] This will slightly decrease performance.
Sep 14 13:55:04 node-4 kernel: [    0.032162] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 14 13:55:04 node-4 kernel: [    0.032593] Enabled IRQ remapping in xapic mode
Sep 14 13:55:04 node-4 kernel: [    0.032594] x2apic not enabled, IRQ remapping is in xapic mode
Sep 14 13:55:04 node-4 kernel: [    0.032598] Switched APIC routing to physical flat.
Sep 14 13:55:04 node-4 kernel: [    0.033215] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 14 13:55:04 node-4 kernel: [    0.072864] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 14 13:55:04 node-4 kernel: [    0.072869] TSC deadline timer enabled
Sep 14 13:55:04 node-4 kernel: [    0.072877] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 14 13:55:04 node-4 kernel: [    0.072883] ... version:                3
Sep 14 13:55:04 node-4 kernel: [    0.072884] ... bit width:              48
Sep 14 13:55:04 node-4 kernel: [    0.072885] ... generic registers:      4
Sep 14 13:55:04 node-4 kernel: [    0.072886] ... value mask:             0000ffffffffffff
Sep 14 13:55:04 node-4 kernel: [    0.072887] ... max period:             0000ffffffffffff
Sep 14 13:55:04 node-4 kernel: [    0.072888] ... fixed-purpose events:   3
Sep 14 13:55:04 node-4 kernel: [    0.072889] ... event mask:             000000070000000f
Sep 14 13:55:04 node-4 kernel: [    0.074273] x86: Booting SMP configuration:
Sep 14 13:55:04 node-4 kernel: [    0.088379] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 14 13:55:04 node-4 kernel: [    0.074275] .... node  #0, CPUs:        #1  #2  #3
Sep 14 13:55:04 node-4 kernel: [    0.116287] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 14 13:55:04 node-4 kernel: [    0.270237] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 14 13:55:04 node-4 kernel: [    0.325846] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 14 13:55:04 node-4 kernel: [    0.382498] x86: Booted up 2 nodes, 16 CPUs
Sep 14 13:55:04 node-4 kernel: [    0.382501] smpboot: Total of 16 processors activated (111750.45 BogoMIPS)
Sep 14 13:55:04 node-4 kernel: [    0.405956] devtmpfs: initialized
Sep 14 13:55:04 node-4 kernel: [    0.409081] EVM: security.selinux
Sep 14 13:55:04 node-4 kernel: [    0.409082] EVM: security.SMACK64
Sep 14 13:55:04 node-4 kernel: [    0.409083] EVM: security.ima
Sep 14 13:55:04 node-4 kernel: [    0.409084] EVM: security.capability
Sep 14 13:55:04 node-4 kernel: [    0.409136] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 14 13:55:04 node-4 kernel: [    0.409823] pinctrl core: initialized pinctrl subsystem
Sep 14 13:55:04 node-4 kernel: [    0.409883] regulator-dummy: no parameters
Sep 14 13:55:04 node-4 kernel: [    0.409915] RTC time: 13:54:29, date: 09/14/16
Sep 14 13:55:04 node-4 kernel: [    0.409949] NET: Registered protocol family 16
Sep 14 13:55:04 node-4 kernel: [    0.410033] cpuidle: using governor ladder
Sep 14 13:55:04 node-4 kernel: [    0.410035] cpuidle: using governor menu
Sep 14 13:55:04 node-4 kernel: [    0.410070] ACPI: bus type PCI registered
Sep 14 13:55:04 node-4 kernel: [    0.410072] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 14 13:55:04 node-4 kernel: [    0.410115] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 14 13:55:04 node-4 kernel: [    0.410117] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 14 13:55:04 node-4 kernel: [    0.423843] PCI: Using configuration type 1 for base access
Sep 14 13:55:04 node-4 kernel: [    0.424830] bio: create slab <bio-0> at 0
Sep 14 13:55:04 node-4 kernel: [    0.425098] ACPI: Added _OSI(Module Device)
Sep 14 13:55:04 node-4 kernel: [    0.425100] ACPI: Added _OSI(Processor Device)
Sep 14 13:55:04 node-4 kernel: [    0.425101] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 14 13:55:04 node-4 kernel: [    0.425102] ACPI: Added _OSI(Processor Aggregator Device)
Sep 14 13:55:04 node-4 kernel: [    0.437760] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 14 13:55:04 node-4 kernel: [    0.448461] ACPI: Interpreter enabled
Sep 14 13:55:04 node-4 kernel: [    0.448466] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 14 13:55:04 node-4 kernel: [    0.448470] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 14 13:55:04 node-4 kernel: [    0.448473] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 14 13:55:04 node-4 kernel: [    0.448480] ACPI: (supports S0 S4 S5)
Sep 14 13:55:04 node-4 kernel: [    0.448481] ACPI: Using IOAPIC for interrupt routing
Sep 14 13:55:04 node-4 kernel: [    0.448521] HEST: Table parsing has been initialized.
Sep 14 13:55:04 node-4 kernel: [    0.448524] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 14 13:55:04 node-4 kernel: [    0.449077] ACPI: No dock devices found.
Sep 14 13:55:04 node-4 kernel: [    0.460805] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 14 13:55:04 node-4 kernel: [    0.460810] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 14 13:55:04 node-4 kernel: [    0.460813] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 14 13:55:04 node-4 kernel: [    0.460842] PCI host bridge to bus 0000:ff
Sep 14 13:55:04 node-4 kernel: [    0.460844] pci_bus 0000:ff: root bus resource [bus ff]
Sep 14 13:55:04 node-4 kernel: [    0.460852] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.460890] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 14 13:55:04 node-4 kernel: [    0.460921] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.460956] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.460985] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 14 13:55:04 node-4 kernel: [    0.461015] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 14 13:55:04 node-4 kernel: [    0.461046] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461074] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461105] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461135] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461162] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461188] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461216] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461242] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461269] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461295] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461325] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461352] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461379] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 14 13:55:04 node-4 kernel: [    0.461408] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461434] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 14 13:55:04 node-4 kernel: [    0.461459] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461485] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461515] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 14 13:55:04 node-4 kernel: [    0.461549] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461580] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461610] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461641] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461671] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461702] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461732] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461762] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461793] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461826] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461859] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461890] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461921] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461952] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.461980] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462011] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462044] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462086] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462122] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462155] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462186] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462215] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462248] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462279] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462312] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462344] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462376] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462406] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462436] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462468] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462498] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462529] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462566] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462625] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 14 13:55:04 node-4 kernel: [    0.462628] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 14 13:55:04 node-4 kernel: [    0.462631] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 14 13:55:04 node-4 kernel: [    0.462649] PCI host bridge to bus 0000:7f
Sep 14 13:55:04 node-4 kernel: [    0.462651] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 14 13:55:04 node-4 kernel: [    0.462656] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462683] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 14 13:55:04 node-4 kernel: [    0.462712] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462742] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462765] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 14 13:55:04 node-4 kernel: [    0.462790] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 14 13:55:04 node-4 kernel: [    0.462817] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462843] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462866] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462889] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462912] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462934] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462959] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.462981] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463006] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463031] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463053] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463076] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463099] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 14 13:55:04 node-4 kernel: [    0.463123] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463145] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 14 13:55:04 node-4 kernel: [    0.463167] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463190] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463217] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 14 13:55:04 node-4 kernel: [    0.463252] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463278] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463304] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463332] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463357] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463386] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463414] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463443] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463469] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463498] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463526] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463555] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463582] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463608] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463633] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463662] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463687] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463714] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463744] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463773] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463798] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463823] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463851] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463881] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463909] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463937] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463967] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.463994] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.464017] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.464044] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.464070] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.464101] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.464126] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.465368] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 14 13:55:04 node-4 kernel: [    0.465371] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 14 13:55:04 node-4 kernel: [    0.466496] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 14 13:55:04 node-4 kernel: [    0.467007] PCI host bridge to bus 0000:00
Sep 14 13:55:04 node-4 kernel: [    0.467009] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 14 13:55:04 node-4 kernel: [    0.467011] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 14 13:55:04 node-4 kernel: [    0.467012] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 14 13:55:04 node-4 kernel: [    0.467014] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 14 13:55:04 node-4 kernel: [    0.467015] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 14 13:55:04 node-4 kernel: [    0.467016] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 14 13:55:04 node-4 kernel: [    0.467018] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 14 13:55:04 node-4 kernel: [    0.467024] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 14 13:55:04 node-4 kernel: [    0.467106] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 14 13:55:04 node-4 kernel: [    0.467137] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 14 13:55:04 node-4 kernel: [    0.467178] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 14 13:55:04 node-4 kernel: [    0.467197] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 14 13:55:04 node-4 kernel: [    0.467227] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 14 13:55:04 node-4 kernel: [    0.467267] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 14 13:55:04 node-4 kernel: [    0.467286] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 14 13:55:04 node-4 kernel: [    0.467315] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 14 13:55:04 node-4 kernel: [    0.467358] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 14 13:55:04 node-4 kernel: [    0.467375] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.467445] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.467520] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.467595] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 14 13:55:04 node-4 kernel: [    0.467600] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 14 13:55:04 node-4 kernel: [    0.467685] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 14 13:55:04 node-4 kernel: [    0.467833] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 14 13:55:04 node-4 kernel: [    0.467850] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 14 13:55:04 node-4 kernel: [    0.467928] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 14 13:55:04 node-4 kernel: [    0.467981] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 14 13:55:04 node-4 kernel: [    0.468002] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 14 13:55:04 node-4 kernel: [    0.468058] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 14 13:55:04 node-4 kernel: [    0.468101] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 14 13:55:04 node-4 kernel: [    0.468128] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 14 13:55:04 node-4 kernel: [    0.468184] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 14 13:55:04 node-4 kernel: [    0.468227] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 14 13:55:04 node-4 kernel: [    0.468251] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 14 13:55:04 node-4 kernel: [    0.468268] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 14 13:55:04 node-4 kernel: [    0.468345] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 14 13:55:04 node-4 kernel: [    0.468395] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 14 13:55:04 node-4 kernel: [    0.468421] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 14 13:55:04 node-4 kernel: [    0.468670] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 14 13:55:04 node-4 kernel: [    0.468676] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 14 13:55:04 node-4 kernel: [    0.468682] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 14 13:55:04 node-4 kernel: [    0.468688] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 14 13:55:04 node-4 kernel: [    0.468695] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 14 13:55:04 node-4 kernel: [    0.468725] pci 0000:01:00.0: supports D1 D2
Sep 14 13:55:04 node-4 kernel: [    0.478548] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 14 13:55:04 node-4 kernel: [    0.478555] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 14 13:55:04 node-4 kernel: [    0.478559] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 14 13:55:04 node-4 kernel: [    0.478811] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 14 13:55:04 node-4 kernel: [    0.478845] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 14 13:55:04 node-4 kernel: [    0.486545] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 14 13:55:04 node-4 kernel: [    0.486551] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 14 13:55:04 node-4 kernel: [    0.486555] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 14 13:55:04 node-4 kernel: [    0.486640] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 14 13:55:04 node-4 kernel: [    0.486713] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 14 13:55:04 node-4 kernel: [    0.486807] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 14 13:55:04 node-4 kernel: [    0.486852] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 14 13:55:04 node-4 kernel: [    0.486855] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 14 13:55:04 node-4 kernel: [    0.486857] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 14 13:55:04 node-4 kernel: [    0.486909] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 14 13:55:04 node-4 kernel: [    0.487031] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 14 13:55:04 node-4 kernel: [    0.487084] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 14 13:55:04 node-4 kernel: [    0.487087] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 14 13:55:04 node-4 kernel: [    0.487089] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 14 13:55:04 node-4 kernel: [    0.487138] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 14 13:55:04 node-4 kernel: [    0.487259] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 14 13:55:04 node-4 kernel: [    0.487297] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 14 13:55:04 node-4 kernel: [    0.487416] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 14 13:55:04 node-4 kernel: [    0.487452] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 14 13:55:04 node-4 kernel: [    0.487591] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 14 13:55:04 node-4 kernel: [    0.487628] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 14 13:55:04 node-4 kernel: [    0.487750] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 14 13:55:04 node-4 kernel: [    0.487793] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 14 13:55:04 node-4 kernel: [    0.487795] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 14 13:55:04 node-4 kernel: [    0.487797] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 14 13:55:04 node-4 kernel: [    0.487855] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 14 13:55:04 node-4 kernel: [    0.487919] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 14 13:55:04 node-4 kernel: [    0.487971] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 14 13:55:04 node-4 kernel: [    0.488012] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 14 13:55:04 node-4 kernel: [    0.488094] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 14 13:55:04 node-4 kernel: [    0.488199] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 14 13:55:04 node-4 kernel: [    0.488202] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 14 13:55:04 node-4 kernel: [    0.488204] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 14 13:55:04 node-4 kernel: [    0.488262] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 14 13:55:04 node-4 kernel: [    0.488315] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 14 13:55:04 node-4 kernel: [    0.488363] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 14 13:55:04 node-4 kernel: [    0.488597] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 14 13:55:04 node-4 kernel: [    0.488601] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 14 13:55:04 node-4 kernel: [    0.488663] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 14 13:55:04 node-4 kernel: [    0.488719] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 14 13:55:04 node-4 kernel: [    0.488771] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 14 13:55:04 node-4 kernel: [    0.488980] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 14 13:55:04 node-4 kernel: [    0.488984] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 14 13:55:04 node-4 kernel: [    0.489042] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 14 13:55:04 node-4 kernel: [    0.489102] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 14 13:55:04 node-4 kernel: [    0.489155] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 14 13:55:04 node-4 kernel: [    0.489378] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 14 13:55:04 node-4 kernel: [    0.489382] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 14 13:55:04 node-4 kernel: [    0.489556] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 14 13:55:04 node-4 kernel: [    0.489594] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 14 13:55:04 node-4 kernel: [    0.489668] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 14 13:55:04 node-4 kernel: [    0.489686] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 14 13:55:04 node-4 kernel: [    0.489700] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 14 13:55:04 node-4 kernel: [    0.489713] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 14 13:55:04 node-4 kernel: [    0.489763] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 14 13:55:04 node-4 kernel: [    0.494552] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 14 13:55:04 node-4 kernel: [    0.494561] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 14 13:55:04 node-4 kernel: [    0.494613] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 14 13:55:04 node-4 kernel: [    0.495179] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 14 13:55:04 node-4 kernel: [    0.495182] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 14 13:55:04 node-4 kernel: [    0.495307] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 14 13:55:04 node-4 kernel: [    0.495413] PCI host bridge to bus 0000:80
Sep 14 13:55:04 node-4 kernel: [    0.495415] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 14 13:55:04 node-4 kernel: [    0.495416] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 14 13:55:04 node-4 kernel: [    0.495418] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 14 13:55:04 node-4 kernel: [    0.495426] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.495489] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.495557] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 14 13:55:04 node-4 kernel: [    0.495618] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 14 13:55:04 node-4 kernel: [    0.495624] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 14 13:55:04 node-4 kernel: [    0.495696] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 14 13:55:04 node-4 kernel: [    0.495999] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 14 13:55:04 node-4 kernel: [    0.496031] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 14 13:55:04 node-4 kernel: [    0.496060] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 14 13:55:04 node-4 kernel: [    0.496090] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 14 13:55:04 node-4 kernel: [    0.496119] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 14 13:55:04 node-4 kernel: [    0.496149] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 14 13:55:04 node-4 kernel: [    0.496179] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 14 13:55:04 node-4 kernel: [    0.496209] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 14 13:55:04 node-4 kernel: [    0.496294] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 14 13:55:04 node-4 kernel: [    0.496299] ACPI: \_SB_.UNC1: notify handler is installed
Sep 14 13:55:04 node-4 kernel: [    0.496300] ACPI: \_SB_.UNC0: notify handler is installed
Sep 14 13:55:04 node-4 kernel: [    0.496315] ACPI: \_SB_.PCI0: notify handler is installed
Sep 14 13:55:04 node-4 kernel: [    0.496368] ACPI: \_SB_.PCI1: notify handler is installed
Sep 14 13:55:04 node-4 kernel: [    0.496447] Found 4 acpi root devices
Sep 14 13:55:04 node-4 kernel: [    0.496554] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 14 13:55:04 node-4 kernel: [    0.496556] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 14 13:55:04 node-4 kernel: [    0.496558] vgaarb: loaded
Sep 14 13:55:04 node-4 kernel: [    0.496559] vgaarb: bridge control possible 0000:0c:00.0
Sep 14 13:55:04 node-4 kernel: [    0.496679] SCSI subsystem initialized
Sep 14 13:55:04 node-4 kernel: [    0.496744] libata version 3.00 loaded.
Sep 14 13:55:04 node-4 kernel: [    0.496759] ACPI: bus type USB registered
Sep 14 13:55:04 node-4 kernel: [    0.496770] usbcore: registered new interface driver usbfs
Sep 14 13:55:04 node-4 kernel: [    0.496775] usbcore: registered new interface driver hub
Sep 14 13:55:04 node-4 kernel: [    0.496799] usbcore: registered new device driver usb
Sep 14 13:55:04 node-4 kernel: [    0.496969] PCI: Using ACPI for IRQ routing
Sep 14 13:55:04 node-4 kernel: [    0.500571] PCI: pci_cache_line_size set to 64 bytes
Sep 14 13:55:04 node-4 kernel: [    0.500783] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 14 13:55:04 node-4 kernel: [    0.500784] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 14 13:55:04 node-4 kernel: [    0.500784] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 14 13:55:04 node-4 kernel: [    0.500852] NetLabel: Initializing
Sep 14 13:55:04 node-4 kernel: [    0.500854] NetLabel:  domain hash size = 128
Sep 14 13:55:04 node-4 kernel: [    0.500855] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 14 13:55:04 node-4 kernel: [    0.500865] NetLabel:  unlabeled traffic allowed by default
Sep 14 13:55:04 node-4 kernel: [    0.500922] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 14 13:55:04 node-4 kernel: [    0.500927] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 14 13:55:04 node-4 kernel: [    0.502984] Switched to clocksource hpet
Sep 14 13:55:04 node-4 kernel: [    0.506925] AppArmor: AppArmor Filesystem Enabled
Sep 14 13:55:04 node-4 kernel: [    0.506947] pnp: PnP ACPI init
Sep 14 13:55:04 node-4 kernel: [    0.506954] ACPI: bus type PNP registered
Sep 14 13:55:04 node-4 kernel: [    0.507071] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 14 13:55:04 node-4 kernel: [    0.507079] pnp 00:01: [dma 4]
Sep 14 13:55:04 node-4 kernel: [    0.507091] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 14 13:55:04 node-4 kernel: [    0.507118] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 14 13:55:04 node-4 kernel: [    0.507138] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 14 13:55:04 node-4 kernel: [    0.507156] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 14 13:55:04 node-4 kernel: [    0.507190] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 14 13:55:04 node-4 kernel: [    0.507244] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 14 13:55:04 node-4 kernel: [    0.507246] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 14 13:55:04 node-4 kernel: [    0.507247] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 14 13:55:04 node-4 kernel: [    0.507249] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 14 13:55:04 node-4 kernel: [    0.507250] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 14 13:55:04 node-4 kernel: [    0.507255] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 14 13:55:04 node-4 kernel: [    0.507257] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 14 13:55:04 node-4 kernel: [    0.507259] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 14 13:55:04 node-4 kernel: [    0.507261] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 14 13:55:04 node-4 kernel: [    0.507262] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 14 13:55:04 node-4 kernel: [    0.507263] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 14 13:55:04 node-4 kernel: [    0.507265] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 14 13:55:04 node-4 kernel: [    0.507266] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 14 13:55:04 node-4 kernel: [    0.507268] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 14 13:55:04 node-4 kernel: [    0.507352] pnp 00:07: [dma 0 disabled]
Sep 14 13:55:04 node-4 kernel: [    0.507381] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 14 13:55:04 node-4 kernel: [    0.507456] pnp 00:08: [dma 0 disabled]
Sep 14 13:55:04 node-4 kernel: [    0.507489] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 14 13:55:04 node-4 kernel: [    0.507541] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 14 13:55:04 node-4 kernel: [    0.507893] pnp: PnP ACPI: found 10 devices
Sep 14 13:55:04 node-4 kernel: [    0.507895] ACPI: bus type PNP unregistered
Sep 14 13:55:04 node-4 kernel: [    0.514159] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 14 13:55:04 node-4 kernel: [    0.514162] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 14 13:55:04 node-4 kernel: [    0.514165] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 14 13:55:04 node-4 kernel: [    0.514169] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 14 13:55:04 node-4 kernel: [    0.514171] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 14 13:55:04 node-4 kernel: [    0.514186] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 14 13:55:04 node-4 kernel: [    0.514215] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 14 13:55:04 node-4 kernel: [    0.514230] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 14 13:55:04 node-4 kernel: [    0.514258] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 14 13:55:04 node-4 kernel: [    0.514273] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 14 13:55:04 node-4 kernel: [    0.514301] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 14 13:55:04 node-4 kernel: [    0.514316] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 14 13:55:04 node-4 kernel: [    0.514345] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 14 13:55:04 node-4 kernel: [    0.514346] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 14 13:55:04 node-4 kernel: [    0.514361] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 14 13:55:04 node-4 kernel: [    0.514392] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 14 13:55:04 node-4 kernel: [    0.514394] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 14 13:55:04 node-4 kernel: [    0.514409] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 14 13:55:04 node-4 kernel: [    0.514437] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 14 13:55:04 node-4 kernel: [    0.514439] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 14 13:55:04 node-4 kernel: [    0.514442] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 14 13:55:04 node-4 kernel: [    0.514446] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 14 13:55:04 node-4 kernel: [    0.514448] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 14 13:55:04 node-4 kernel: [    0.514450] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 14 13:55:04 node-4 kernel: [    0.514454] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 14 13:55:04 node-4 kernel: [    0.514459] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 14 13:55:04 node-4 kernel: [    0.514466] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 14 13:55:04 node-4 kernel: [    0.514470] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 14 13:55:04 node-4 kernel: [    0.514476] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 14 13:55:04 node-4 kernel: [    0.514477] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 14 13:55:04 node-4 kernel: [    0.514478] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 14 13:55:04 node-4 kernel: [    0.514479] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 14 13:55:04 node-4 kernel: [    0.514480] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 14 13:55:04 node-4 kernel: [    0.514481] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 14 13:55:04 node-4 kernel: [    0.514482] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 14 13:55:04 node-4 kernel: [    0.514482] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 14 13:55:04 node-4 kernel: [    0.514483] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 14 13:55:04 node-4 kernel: [    0.514484] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 14 13:55:04 node-4 kernel: [    0.514485] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 14 13:55:04 node-4 kernel: [    0.514486] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 14 13:55:04 node-4 kernel: [    0.514487] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 14 13:55:04 node-4 kernel: [    0.514488] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 14 13:55:04 node-4 kernel: [    0.514489] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 14 13:55:04 node-4 kernel: [    0.514489] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 14 13:55:04 node-4 kernel: [    0.514490] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 14 13:55:04 node-4 kernel: [    0.514491] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 14 13:55:04 node-4 kernel: [    0.514492] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 14 13:55:04 node-4 kernel: [    0.514493] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 14 13:55:04 node-4 kernel: [    0.514494] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 14 13:55:04 node-4 kernel: [    0.514495] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 14 13:55:04 node-4 kernel: [    0.514497] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 14 13:55:04 node-4 kernel: [    0.514498] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 14 13:55:04 node-4 kernel: [    0.514540] NET: Registered protocol family 2
Sep 14 13:55:04 node-4 kernel: [    0.514810] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 14 13:55:04 node-4 kernel: [    0.515149] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 14 13:55:04 node-4 kernel: [    0.515297] TCP: Hash tables configured (established 262144 bind 65536)
Sep 14 13:55:04 node-4 kernel: [    0.515334] TCP: reno registered
Sep 14 13:55:04 node-4 kernel: [    0.515363] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 14 13:55:04 node-4 kernel: [    0.515459] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 14 13:55:04 node-4 kernel: [    0.515613] NET: Registered protocol family 1
Sep 14 13:55:04 node-4 kernel: [    0.551058] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 14 13:55:04 node-4 kernel: [    0.551065] PCI: CLS 64 bytes, default 64
Sep 14 13:55:04 node-4 kernel: [    0.551106] Trying to unpack rootfs image as initramfs...
Sep 14 13:55:04 node-4 kernel: [    0.771002] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Sep 14 13:55:04 node-4 kernel: [    0.771046] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 14 13:55:04 node-4 kernel: [    0.771048] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 14 13:55:04 node-4 kernel: [    0.771465] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 13:55:04 node-4 kernel: [    0.771471] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 13:55:04 node-4 kernel: [    0.771476] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 13:55:04 node-4 kernel: [    0.771482] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 13:55:04 node-4 kernel: [    0.771493] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 13:55:04 node-4 kernel: [    0.771510] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 13:55:04 node-4 kernel: [    0.771525] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 13:55:04 node-4 kernel: [    0.771540] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 13:55:04 node-4 kernel: [    0.771552] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 13:55:04 node-4 kernel: [    0.771562] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 13:55:04 node-4 kernel: [    0.771568] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 13:55:04 node-4 kernel: [    0.771575] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 13:55:04 node-4 kernel: [    0.771584] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 13:55:04 node-4 kernel: [    0.771596] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 13:55:04 node-4 kernel: [    0.771608] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 13:55:04 node-4 kernel: [    0.771621] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 14 13:55:04 node-4 kernel: [    0.771725] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 14 13:55:04 node-4 kernel: [    0.771731] Scanning for low memory corruption every 60 seconds
Sep 14 13:55:04 node-4 kernel: [    0.772134] Initialise system trusted keyring
Sep 14 13:55:04 node-4 kernel: [    0.772190] audit: initializing netlink socket (disabled)
Sep 14 13:55:04 node-4 kernel: [    0.772207] type=2000 audit(1473861268.728:1): initialized
Sep 14 13:55:04 node-4 kernel: [    0.790060] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 14 13:55:04 node-4 kernel: [    0.791595] zbud: loaded
Sep 14 13:55:04 node-4 kernel: [    0.791720] VFS: Disk quotas dquot_6.5.2
Sep 14 13:55:04 node-4 kernel: [    0.791757] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 14 13:55:04 node-4 kernel: [    0.792132] fuse init (API version 7.22)
Sep 14 13:55:04 node-4 kernel: [    0.792194] msgmni has been set to 32768
Sep 14 13:55:04 node-4 kernel: [    0.792245] Key type big_key registered
Sep 14 13:55:04 node-4 kernel: [    0.792797] Key type asymmetric registered
Sep 14 13:55:04 node-4 kernel: [    0.792799] Asymmetric key parser 'x509' registered
Sep 14 13:55:04 node-4 kernel: [    0.792821] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 14 13:55:04 node-4 kernel: [    0.792894] io scheduler noop registered
Sep 14 13:55:04 node-4 kernel: [    0.792896] io scheduler deadline registered (default)
Sep 14 13:55:04 node-4 kernel: [    0.792916] io scheduler cfq registered
Sep 14 13:55:04 node-4 kernel: [    0.793305] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    0.793423] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    0.793558] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    0.793664] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    0.793804] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    0.793896] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    0.794326] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 14 13:55:04 node-4 kernel: [    0.794360] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 14 13:55:04 node-4 kernel: [    0.794376] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 14 13:55:04 node-4 kernel: [    0.794385] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794387] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794390] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 14 13:55:04 node-4 kernel: [    0.794395] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794397] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794398] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794400] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794401] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794403] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794404] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794406] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794407] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794409] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794410] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794411] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794414] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 14 13:55:04 node-4 kernel: [    0.794419] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794421] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 14 13:55:04 node-4 kernel: [    0.794440] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794443] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 14 13:55:04 node-4 kernel: [    0.794454] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794455] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 14 13:55:04 node-4 kernel: [    0.794458] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 14 13:55:04 node-4 kernel: [    0.794497] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 14 13:55:04 node-4 kernel: [    0.794503] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 14 13:55:04 node-4 kernel: [    0.794507] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 14 13:55:04 node-4 kernel: [    0.794517] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 14 13:55:04 node-4 kernel: [    0.794557] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 14 13:55:04 node-4 kernel: [    0.794559] vesafb: scrolling: redraw
Sep 14 13:55:04 node-4 kernel: [    0.794560] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 14 13:55:04 node-4 kernel: [    0.815225] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 14 13:55:04 node-4 kernel: [    0.823743] Console: switching to colour frame buffer device 80x30
Sep 14 13:55:04 node-4 kernel: [    0.832414] fb0: VESA VGA frame buffer device
Sep 14 13:55:04 node-4 kernel: [    0.832610] intel_idle: MWAIT substates: 0x2120
Sep 14 13:55:04 node-4 kernel: [    0.832611] intel_idle: v0.4 model 0x3F
Sep 14 13:55:04 node-4 kernel: [    0.832611] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 14 13:55:04 node-4 kernel: [    0.832861] ipmi message handler version 39.2
Sep 14 13:55:04 node-4 kernel: [    0.833131] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 14 13:55:04 node-4 kernel: [    0.833566] ACPI: AC Adapter [P111] (on-line)
Sep 14 13:55:04 node-4 kernel: [    0.838780] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 14 13:55:04 node-4 kernel: [    0.849789] ACPI: Power Button [PWRB]
Sep 14 13:55:04 node-4 kernel: [    0.855556] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 14 13:55:04 node-4 kernel: [    0.867164] ACPI: Power Button [PWRF]
Sep 14 13:55:04 node-4 kernel: [    0.892558] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 14 13:55:04 node-4 kernel: [    0.904257] pstore: Registered erst as persistent store backend
Sep 14 13:55:04 node-4 kernel: [    0.910448] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 14 13:55:04 node-4 kernel: [    0.922381] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 14 13:55:04 node-4 kernel: [    0.949125] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 14 13:55:04 node-4 kernel: [    0.982424] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 14 13:55:04 node-4 kernel: [    0.996502] Linux agpgart interface v0.103
Sep 14 13:55:04 node-4 kernel: [    1.004163] brd: module loaded
Sep 14 13:55:04 node-4 kernel: [    1.011207] loop: module loaded
Sep 14 13:55:04 node-4 kernel: [    1.017939] libphy: Fixed MDIO Bus: probed
Sep 14 13:55:04 node-4 kernel: [    1.024425] tun: Universal TUN/TAP device driver, 1.6
Sep 14 13:55:04 node-4 kernel: [    1.030904] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 14 13:55:04 node-4 kernel: [    1.037427] PPP generic driver version 2.4.2
Sep 14 13:55:04 node-4 kernel: [    1.043811] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 14 13:55:04 node-4 kernel: [    1.050265] ehci-pci: EHCI PCI platform driver
Sep 14 13:55:04 node-4 kernel: [    1.056842] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 14 13:55:04 node-4 kernel: [    1.063350] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 14 13:55:04 node-4 kernel: [    1.076030] ehci-pci 0000:00:1a.0: debug port 2
Sep 14 13:55:04 node-4 kernel: [    1.086228] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 14 13:55:04 node-4 kernel: [    1.086246] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 14 13:55:04 node-4 kernel: [    1.102479] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 14 13:55:04 node-4 kernel: [    1.108598] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 14 13:55:04 node-4 kernel: [    1.114783] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 14 13:55:04 node-4 kernel: [    1.126716] usb usb1: Product: EHCI Host Controller
Sep 14 13:55:04 node-4 kernel: [    1.132753] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 14 13:55:04 node-4 kernel: [    1.138810] usb usb1: SerialNumber: 0000:00:1a.0
Sep 14 13:55:04 node-4 kernel: [    1.144765] hub 1-0:1.0: USB hub found
Sep 14 13:55:04 node-4 kernel: [    1.150549] hub 1-0:1.0: 2 ports detected
Sep 14 13:55:04 node-4 kernel: [    1.156368] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 14 13:55:04 node-4 kernel: [    1.161970] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 14 13:55:04 node-4 kernel: [    1.172896] ehci-pci 0000:00:1d.0: debug port 2
Sep 14 13:55:04 node-4 kernel: [    1.182212] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 14 13:55:04 node-4 kernel: [    1.182219] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 14 13:55:04 node-4 kernel: [    1.198398] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 14 13:55:04 node-4 kernel: [    1.203626] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 14 13:55:04 node-4 kernel: [    1.208949] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 14 13:55:04 node-4 kernel: [    1.219562] usb usb2: Product: EHCI Host Controller
Sep 14 13:55:04 node-4 kernel: [    1.225048] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 14 13:55:04 node-4 kernel: [    1.230609] usb usb2: SerialNumber: 0000:00:1d.0
Sep 14 13:55:04 node-4 kernel: [    1.236141] hub 2-0:1.0: USB hub found
Sep 14 13:55:04 node-4 kernel: [    1.241506] hub 2-0:1.0: 2 ports detected
Sep 14 13:55:04 node-4 kernel: [    1.246819] ehci-platform: EHCI generic platform driver
Sep 14 13:55:04 node-4 kernel: [    1.252068] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 14 13:55:04 node-4 kernel: [    1.257399] ohci-pci: OHCI PCI platform driver
Sep 14 13:55:04 node-4 kernel: [    1.262717] ohci-platform: OHCI generic platform driver
Sep 14 13:55:04 node-4 kernel: [    1.267928] uhci_hcd: USB Universal Host Controller Interface driver
Sep 14 13:55:04 node-4 kernel: [    1.273269] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 14 13:55:04 node-4 kernel: [    1.474160] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 14 13:55:04 node-4 kernel: [    1.769922] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 14 13:55:04 node-4 kernel: [    1.786279] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 14 13:55:04 node-4 kernel: [    1.791888] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 14 13:55:04 node-4 kernel: [    1.797673] hub 1-1:1.0: USB hub found
Sep 14 13:55:04 node-4 kernel: [    1.803266] hub 1-1:1.0: 6 ports detected
Sep 14 13:55:04 node-4 kernel: [    1.917786] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 14 13:55:04 node-4 kernel: [    2.311999] i8042: No controller found
Sep 14 13:55:04 node-4 kernel: [    2.317547] mousedev: PS/2 mouse device common for all mice
Sep 14 13:55:04 node-4 kernel: [    2.323264] rtc_cmos 00:02: RTC can wake from S4
Sep 14 13:55:04 node-4 kernel: [    2.326265] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 14 13:55:04 node-4 kernel: [    2.326266] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 14 13:55:04 node-4 kernel: [    2.327021] hub 2-1:1.0: USB hub found
Sep 14 13:55:04 node-4 kernel: [    2.327256] hub 2-1:1.0: 8 ports detected
Sep 14 13:55:04 node-4 kernel: [    2.351588] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 14 13:55:04 node-4 kernel: [    2.357353] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 14 13:55:04 node-4 kernel: [    2.368663] device-mapper: uevent: version 1.0.3
Sep 14 13:55:04 node-4 kernel: [    2.374383] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 14 13:55:04 node-4 kernel: [    2.385770] ledtrig-cpu: registered to indicate activity on CPUs
Sep 14 13:55:04 node-4 kernel: [    2.391743] TCP: cubic registered
Sep 14 13:55:04 node-4 kernel: [    2.397606] NET: Registered protocol family 10
Sep 14 13:55:04 node-4 kernel: [    2.403665] NET: Registered protocol family 17
Sep 14 13:55:04 node-4 kernel: [    2.409422] Key type dns_resolver registered
Sep 14 13:55:04 node-4 kernel: [    2.415475] Loading compiled-in X.509 certificates
Sep 14 13:55:04 node-4 kernel: [    2.421687] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 14 13:55:04 node-4 kernel: [    2.433314] registered taskstats version 1
Sep 14 13:55:04 node-4 kernel: [    2.441365] Key type trusted registered
Sep 14 13:55:04 node-4 kernel: [    2.448985] Key type encrypted registered
Sep 14 13:55:04 node-4 kernel: [    2.454456] AppArmor: AppArmor sha1 policy hashing enabled
Sep 14 13:55:04 node-4 kernel: [    2.459953] IMA: No TPM chip found, activating TPM-bypass!
Sep 14 13:55:04 node-4 kernel: [    2.465987] regulator-dummy: disabling
Sep 14 13:55:04 node-4 kernel: [    2.471486]   Magic number: 0:340:938
Sep 14 13:55:04 node-4 kernel: [    2.477192] rtc_cmos 00:02: setting system clock to 2016-09-14 13:54:31 UTC (1473861271)
Sep 14 13:55:04 node-4 kernel: [    2.489684] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 14 13:55:04 node-4 kernel: [    2.495332] EDD information not available.
Sep 14 13:55:04 node-4 kernel: [    2.500939] PM: Hibernation image not present or could not be loaded.
Sep 14 13:55:04 node-4 kernel: [    2.501804] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 14 13:55:04 node-4 kernel: [    2.513115] Write protecting the kernel read-only data: 12288k
Sep 14 13:55:04 node-4 kernel: [    2.519395] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 14 13:55:04 node-4 kernel: [    2.532339] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 14 13:55:04 node-4 kernel: [    2.564189] device-mapper: multipath: version 1.6.0 loaded
Sep 14 13:55:04 node-4 kernel: [    2.572271] systemd-udevd[215]: starting version 204
Sep 14 13:55:04 node-4 kernel: [    2.592260] md: linear personality registered for level -1
Sep 14 13:55:04 node-4 kernel: [    2.606716] md: multipath personality registered for level -4
Sep 14 13:55:04 node-4 kernel: [    2.614587] md: raid0 personality registered for level 0
Sep 14 13:55:04 node-4 kernel: [    2.621195] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 14 13:55:04 node-4 kernel: [    2.627803] md: raid1 personality registered for level 1
Sep 14 13:55:04 node-4 kernel: [    2.635212] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 14 13:55:04 node-4 kernel: [    2.641799] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 14 13:55:04 node-4 kernel: [    2.641792] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 14 13:55:04 node-4 kernel: [    2.661130] megasas: FW now in Ready state
Sep 14 13:55:04 node-4 kernel: [    2.667678] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.667682] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.667686] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.667690] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.667694] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.667698] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.667705] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.667709] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.667713] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.667717] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.667721] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.667725] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.667729] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.667733] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.667741] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.667745] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.667781] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 14 13:55:04 node-4 kernel: [    2.689171] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Sep 14 13:55:04 node-4 kernel: [    2.702736] 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
Sep 14 13:55:04 node-4 kernel: [    2.716698] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 14 13:55:04 node-4 kernel: [    2.721282] raid6: sse2x1    8091 MB/s
Sep 14 13:55:04 node-4 kernel: [    2.730714] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.730724] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.730727] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.730731] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.730782] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 14 13:55:04 node-4 kernel: [    2.754759] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Sep 14 13:55:04 node-4 kernel: [    2.768820] 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
Sep 14 13:55:04 node-4 kernel: [    2.782913] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 14 13:55:04 node-4 kernel: [    2.789306] raid6: sse2x2   12945 MB/s
Sep 14 13:55:04 node-4 kernel: [    2.857000] raid6: sse2x4   10103 MB/s
Sep 14 13:55:04 node-4 kernel: [    2.928942] raid6: avx2x1   14942 MB/s
Sep 14 13:55:04 node-4 kernel: [    3.000872] raid6: avx2x2   18869 MB/s
Sep 14 13:55:04 node-4 kernel: [    3.072824] raid6: avx2x4   21276 MB/s
Sep 14 13:55:04 node-4 kernel: [    3.079143] raid6: using algorithm avx2x4 (21276 MB/s)
Sep 14 13:55:04 node-4 kernel: [    3.085493] raid6: using avx2x2 recovery algorithm
Sep 14 13:55:04 node-4 kernel: [    3.091825] megasas:IOC Init cmd success
Sep 14 13:55:04 node-4 kernel: [    3.091827] Switched to clocksource tsc
Sep 14 13:55:04 node-4 kernel: [    3.104002] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    3.104008] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    3.104012] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    3.104016] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    3.104071] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 14 13:55:04 node-4 kernel: [    3.116291] xor: automatically using best checksumming function:
Sep 14 13:55:04 node-4 kernel: [    3.123408] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Sep 14 13:55:04 node-4 kernel: [    3.135871] 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
Sep 14 13:55:04 node-4 kernel: [    3.148692] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 14 13:55:04 node-4 kernel: [    3.155140] megasas: INIT adapter done
Sep 14 13:55:04 node-4 kernel: [    3.160722]    avx       : 36705.000 MB/sec
Sep 14 13:55:04 node-4 kernel: [    3.167536] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    3.167540] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    3.167543] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    3.167547] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    3.167588] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 14 13:55:04 node-4 kernel: [    3.179806] async_tx: api initialized (async)
Sep 14 13:55:04 node-4 kernel: [    3.181782] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 14 13:55:04 node-4 kernel: [    3.181783] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 14 13:55:04 node-4 kernel: [    3.181784] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 14 13:55:04 node-4 kernel: [    3.181785] usb 2-1.4: Manufacturer: Avocent
Sep 14 13:55:04 node-4 kernel: [    3.181785] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 14 13:55:04 node-4 kernel: [    3.192206] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Sep 14 13:55:04 node-4 kernel: [    3.192207] 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
Sep 14 13:55:04 node-4 kernel: [    3.192208] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 14 13:55:04 node-4 kernel: [    3.192272] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    3.192312] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    3.192348] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    3.192375] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 14 13:55:04 node-4 kernel: [    3.192459] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 14 13:55:04 node-4 kernel: [    3.240677] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 14 13:55:04 node-4 kernel: [    3.241044] scsi0 : LSI SAS based MegaRAID driver
Sep 14 13:55:04 node-4 kernel: [    3.248177] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 14 13:55:04 node-4 kernel: [    3.259231] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 14 13:55:04 node-4 kernel: [    3.263437] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 14 13:55:04 node-4 kernel: [    3.263576] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 14 13:55:04 node-4 kernel: [    3.263751] sd 0:2:0:0: [sda] Write Protect is off
Sep 14 13:55:04 node-4 kernel: [    3.263753] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 14 13:55:04 node-4 kernel: [    3.263828] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 14 13:55:04 node-4 kernel: [    3.296615]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Sep 14 13:55:04 node-4 kernel: [    3.298068] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 14 13:55:04 node-4 kernel: [    3.353811] hidraw: raw HID events driver (C) Jiri Kosina
Sep 14 13:55:04 node-4 kernel: [    3.362896] usbcore: registered new interface driver usbhid
Sep 14 13:55:04 node-4 kernel: [    3.369220] usbhid: USB HID core driver
Sep 14 13:55:04 node-4 kernel: [    3.375527] md: raid6 personality registered for level 6
Sep 14 13:55:04 node-4 kernel: [    3.381802] md: raid5 personality registered for level 5
Sep 14 13:55:04 node-4 kernel: [    3.387871] md: raid4 personality registered for level 4
Sep 14 13:55:04 node-4 kernel: [    3.393885] 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
Sep 14 13:55:04 node-4 kernel: [    3.406209] 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
Sep 14 13:55:04 node-4 kernel: [    3.418833] 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
Sep 14 13:55:04 node-4 kernel: [    3.431424] md: raid10 personality registered for level 10
Sep 14 13:55:04 node-4 kernel: [    3.431559] 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
Sep 14 13:55:04 node-4 kernel: [    3.433583] 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
Sep 14 13:55:04 node-4 kernel: [    3.434593] 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
Sep 14 13:55:04 node-4 kernel: [    3.489710] random: lvm urandom read with 32 bits of entropy available
Sep 14 13:55:04 node-4 kernel: [    3.532946] multipathd (368): /proc/368/oom_adj is deprecated, please use /proc/368/oom_score_adj instead.
Sep 14 13:55:04 node-4 kernel: [    3.646357] bio: create slab <bio-1> at 1
Sep 14 13:55:04 node-4 kernel: [    4.416379] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 14 13:55:04 node-4 kernel: [    5.060738] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep 14 13:55:04 node-4 kernel: [    5.079688] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 14 13:55:04 node-4 kernel: [    5.260218] random: nonblocking pool is initialized
Sep 14 13:55:04 node-4 kernel: [    5.286234] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 14 13:55:04 node-4 kernel: [    5.322230] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 14 13:55:04 node-4 kernel: [    5.422239] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 14 13:55:04 node-4 kernel: [    5.580289] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 14 13:55:04 node-4 kernel: [    5.621772] XFS (dm-0): Mounting Filesystem
Sep 14 13:55:04 node-4 kernel: [    5.945590] XFS (dm-0): Ending clean mount
Sep 14 13:55:04 node-4 kernel: [    5.994808] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep 14 13:55:04 node-4 kernel: [    6.025612] XFS (dm-1): Mounting Filesystem
Sep 14 13:55:04 node-4 kernel: [    6.123803] XFS (dm-1): Ending clean mount
Sep 14 13:55:04 node-4 kernel: [    7.892905] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 14 13:55:04 node-4 kernel: [    7.919942] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 14 13:55:04 node-4 kernel: [    8.053922] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 14 13:55:04 node-4 kernel: [    8.053928] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 14 13:55:04 node-4 kernel: [    8.053932] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 14 13:55:04 node-4 kernel: [    8.053936] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 14 13:55:04 node-4 kernel: [    8.098149] systemd-udevd[778]: starting version 204
Sep 14 13:55:04 node-4 kernel: [    8.325501] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 14 13:55:04 node-4 kernel: [    8.325508] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 14 13:55:04 node-4 kernel: [    8.325511] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 14 13:55:04 node-4 kernel: [    8.325514] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 14 13:55:04 node-4 kernel: [    8.325609] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 14 13:55:04 node-4 kernel: [    8.328812] power_meter ACPI000D:00: Found ACPI power meter.
Sep 14 13:55:04 node-4 kernel: [    8.328836] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 14 13:55:04 node-4 kernel: [    8.341400] wmi: Mapper loaded
Sep 14 13:55:04 node-4 kernel: [    8.345062] IPMI System Interface driver.
Sep 14 13:55:04 node-4 kernel: [    8.345119] ipmi_si: probing via ACPI
Sep 14 13:55:04 node-4 kernel: [    8.345132] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 14 13:55:04 node-4 kernel: [    8.345133] ipmi_si: Adding ACPI-specified kcs state machine
Sep 14 13:55:04 node-4 kernel: [    8.345163] ipmi_si: probing via SMBIOS
Sep 14 13:55:04 node-4 kernel: [    8.345164] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 14 13:55:04 node-4 kernel: [    8.345165] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 14 13:55:04 node-4 kernel: [    8.345167] ipmi_si: probing via SPMI
Sep 14 13:55:04 node-4 kernel: [    8.345168] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 14 13:55:04 node-4 kernel: [    8.345168] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 14 13:55:04 node-4 kernel: [    8.345170] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 14 13:55:04 node-4 kernel: [    8.349643] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 14 13:55:04 node-4 kernel: [    8.420751] systemd-udevd[826]: renamed network interface eth0 to enp6s0
Sep 14 13:55:04 node-4 kernel: [    8.456757] systemd-udevd[833]: renamed network interface eth1 to enp7s0
Sep 14 13:55:04 node-4 kernel: [    8.480543] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 14 13:55:04 node-4 kernel: [    8.480550] ipmi_si 00:09: IPMI kcs interface initialized
Sep 14 13:55:04 node-4 kernel: [    8.500735] systemd-udevd[819]: renamed network interface eth3 to enp9s0
Sep 14 13:55:04 node-4 kernel: [    8.536560] systemd-udevd[806]: renamed network interface eth2 to enp8s0
Sep 14 13:55:04 node-4 kernel: [    8.747471] type=1400 audit(1473861277.771:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1030 comm="apparmor_parser"
Sep 14 13:55:04 node-4 kernel: [    8.747642] type=1400 audit(1473861277.771:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1030 comm="apparmor_parser"
Sep 14 13:55:04 node-4 kernel: [    8.747767] type=1400 audit(1473861277.771:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1030 comm="apparmor_parser"
Sep 14 13:55:04 node-4 kernel: [    8.758480] type=1400 audit(1473861277.783:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1028 comm="apparmor_parser"
Sep 14 13:55:04 node-4 kernel: [    8.758622] type=1400 audit(1473861277.783:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1028 comm="apparmor_parser"
Sep 14 13:55:04 node-4 kernel: [    8.758741] type=1400 audit(1473861277.783:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1028 comm="apparmor_parser"
Sep 14 13:55:04 node-4 kernel: [    8.765371] type=1400 audit(1473861277.791:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1032 comm="apparmor_parser"
Sep 14 13:55:04 node-4 kernel: [    8.765527] type=1400 audit(1473861277.791:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1032 comm="apparmor_parser"
Sep 14 13:55:04 node-4 kernel: [    8.765646] type=1400 audit(1473861277.791:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1032 comm="apparmor_parser"
Sep 14 13:55:04 node-4 kernel: [    8.773775] type=1400 audit(1473861277.799:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1031 comm="apparmor_parser"
Sep 14 13:55:04 node-4 kernel: [    9.242453] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 14 13:55:04 node-4 kernel: [    9.254162] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 14 13:55:04 node-4 kernel: [    9.426250] enic 0000:06:00.0 enp6s0: Link UP
Sep 14 13:55:04 node-4 kernel: [    9.426673] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 14 13:55:04 node-4 kernel: [    9.426678] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 14 13:55:04 node-4 kernel: [   18.860116] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 14 13:55:04 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 14 13:55:06 node-4 failsafe: Failsafe of 120 seconds reached.
Sep 14 13:55:06 node-4 kernel: [   37.293593] init: failsafe main process (8416) killed by TERM signal
Sep 14 13:55:06 node-4 dbus[8463]: [system] AppArmor D-Bus mediation is enabled
Sep 14 13:55:06 node-4 kernel: [   37.508949] audit_printk_skb: 30 callbacks suppressed
Sep 14 13:55:06 node-4 kernel: [   37.508950] type=1400 audit(1473861306.372:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8545 comm="apparmor_parser"
Sep 14 13:55:06 node-4 kernel: [   37.509941] type=1400 audit(1473861306.372:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8544 comm="apparmor_parser"
Sep 14 13:55:06 node-4 kernel: [   37.509946] type=1400 audit(1473861306.372:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8544 comm="apparmor_parser"
Sep 14 13:55:06 node-4 kernel: [   37.509948] type=1400 audit(1473861306.372:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8544 comm="apparmor_parser"
Sep 14 13:55:06 node-4 kernel: [   37.510163] type=1400 audit(1473861306.372:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8544 comm="apparmor_parser"
Sep 14 13:55:06 node-4 kernel: [   37.510165] type=1400 audit(1473861306.372:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8544 comm="apparmor_parser"
Sep 14 13:55:06 node-4 kernel: [   37.510277] type=1400 audit(1473861306.372:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8544 comm="apparmor_parser"
Sep 14 13:55:06 node-4 kernel: [   37.607716] type=1400 audit(1473861306.472:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8547 comm="apparmor_parser"
Sep 14 13:55:06 node-4 anacron[8609]: Anacron 2.3 started on 2016-09-14
Sep 14 13:55:06 node-4 anacron[8609]: Will run job `cron.daily' in 5 min.
Sep 14 13:55:06 node-4 anacron[8609]: Will run job `cron.weekly' in 10 min.
Sep 14 13:55:06 node-4 anacron[8609]: Will run job `cron.monthly' in 15 min.
Sep 14 13:55:06 node-4 anacron[8609]: Jobs will be executed sequentially
Sep 14 13:55:06 node-4 cron[8575]: (CRON) INFO (pidfile fd = 3)
Sep 14 13:55:06 node-4 cron[8627]: (CRON) STARTUP (fork ok)
Sep 14 13:55:06 node-4 multipathd: path checkers start up
Sep 14 13:55:06 node-4 cron[8627]: (CRON) INFO (Running @reboot jobs)
Sep 14 13:55:07 node-4 postfix/master[8754]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 14 13:55:10 node-4 puppet-agent[8938]: Reopening log files
Sep 14 13:55:11 node-4 puppet-agent[8938]: Could not request certificate: Connection refused - connect(2)
Sep 14 13:55:39 node-4 kernel: [   70.482469] init: plymouth-upstart-bridge main process ended, respawning
Sep 14 13:55:39 node-4 puppet-agent[8938]: Could not run: SIGTERM
Sep 14 13:55:39 node-4 kernel: [   70.800169] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 14 13:55:39 node-4 ec2: 
Sep 14 13:55:39 node-4 ec2: #############################################################
Sep 14 13:55:39 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 14 13:55:39 node-4 ec2: 1024 fb:e1:14:54:b0:11:6a:65:b8:48:68:58:9f:46:c2:e4  root@node-4.domain.tld (DSA)
Sep 14 13:55:39 node-4 ec2: 256 50:05:af:09:db:a0:ad:c7:27:6b:44:0d:c9:cc:5c:be  root@node-4.domain.tld (ECDSA)
Sep 14 13:55:39 node-4 ec2: 256 18:f5:d6:fa:36:23:16:b9:25:43:e6:6f:b7:eb:1b:16  root@node-4.domain.tld (ED25519)
Sep 14 13:55:39 node-4 ec2: 2048 3d:e8:45:3c:c7:c6:66:52:4c:70:6f:b5:1b:64:e7:56  root@node-4.domain.tld (RSA)
Sep 14 13:55:39 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 14 13:55:39 node-4 ec2: #############################################################
Sep 14 13:56:00 node-4 puppet-user[9497]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 14 13:56:00 node-4 puppet-user[9497]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Sep 14 13:56:00 node-4 puppet-user[9497]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 14 13:56:00 node-4 puppet-user[9497]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 14 13:56:00 node-4 puppet-user[9497]: Finished catalog run in 0.41 seconds
Sep 14 13:56:01 node-4 CRON[10068]: (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")
Sep 14 13:56:02 node-4 multipathd: uevent trigger error
Sep 14 13:56:02 node-4 puppet-user[9917]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 14 13:56:02 node-4 puppet-user[9917]: Compiled catalog for node-4.domain.tld in environment production in 0.09 seconds
Sep 14 13:56:02 node-4 puppet-user[9917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 14 13:56:02 node-4 puppet-user[9917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 14 13:56:02 node-4 puppet-user[9917]: (/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"]'
Sep 14 13:56:02 node-4 puppet-user[9917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 14 13:56:02 node-4 puppet-user[9917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 14 13:56:02 node-4 puppet-user[9917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 14 13:56:02 node-4 puppet-user[9917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 14 13:56:02 node-4 puppet-user[9917]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 14 13:56:02 node-4 puppet-user[9917]: Finished catalog run in 0.06 seconds
Sep 14 13:56:03 node-4 puppet-user[10385]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 14 13:56:03 node-4 puppet-user[10385]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Sep 14 13:56:03 node-4 puppet-user[10385]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 14 13:56:03 node-4 puppet-user[10385]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 14 13:56:03 node-4 puppet-user[10385]: Finished catalog run in 0.03 seconds
Sep 14 13:56:05 node-4 puppet-user[10843]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 14 13:56:05 node-4 puppet-user[10843]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Sep 14 13:56:05 node-4 puppet-user[10843]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 14 13:56:05 node-4 puppet-user[10843]: Finished catalog run in 0.04 seconds
Sep 14 13:56:07 node-4 puppet-user[11290]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 14 13:56:07 node-4 puppet-user[11290]: Compiled catalog for node-4.domain.tld in environment production in 0.23 seconds
Sep 14 13:56:07 node-4 puppet-user[11290]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 14 13:56:07 node-4 puppet-user[11290]: (/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
Sep 14 13:56:07 node-4 puppet-user[11290]: Finished catalog run in 0.45 seconds
Sep 14 13:56:09 node-4 puppet-user[11760]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 14 13:56:09 node-4 puppet-user[11760]: Compiled catalog for node-4.domain.tld in environment production in 0.27 seconds
Sep 14 13:56:09 node-4 puppet-user[11760]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 14 13:56:09 node-4 puppet-user[11760]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 14 13:56:10 node-4 puppet-user[11760]: (/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
Sep 14 13:56:10 node-4 puppet-user[11760]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 14 13:56:10 node-4 puppet-user[11760]: Finished catalog run in 0.28 seconds
Sep 14 13:56:12 node-4 puppet-user[12238]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 14 13:56:12 node-4 puppet-user[12238]: Compiled catalog for node-4.domain.tld in environment production in 0.21 seconds
Sep 14 13:56:12 node-4 puppet-user[12238]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 14 13:56:12 node-4 kernel: [  103.884679] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 14 13:56:12 node-4 kernel: [  103.884740] 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.
Sep 14 13:56:12 node-4 puppet-user[12238]: (/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'
Sep 14 13:56:12 node-4 puppet-user[12238]: Finished catalog run in 0.09 seconds
Sep 14 13:56:14 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 14 13:56:14 node-4 nailgun-agent: I, [2016-09-14T13:56:14.902587 #10074]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 14 13:56:15 node-4 puppet-user[12700]: (Scope(Class[main])) MODULAR: sync_time
Sep 14 13:56:15 node-4 puppet-user[12700]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Sep 14 13:56:15 node-4 ntpdate[13236]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 14 13:56:21 node-4 ntpdate[13236]: adjust time server 10.20.0.2 offset 0.071684 sec
Sep 14 13:56:21 node-4 puppet-user[12700]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 14 13:56:21 node-4 puppet-user[12700]: Finished catalog run in 6.19 seconds
Sep 14 13:56:27 node-4 puppet-user[13417]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 14 13:56:27 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 14 13:56:28 node-4 puppet-user[13417]: Compiled catalog for node-4.domain.tld in environment production in 0.11 seconds
Sep 14 13:56:28 node-4 puppet-user[13417]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 14 13:56:28 node-4 nailgun-agent: I, [2016-09-14T13:56:28.189944 #10074]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Sep 14 13:56:28 node-4 puppet-user[13417]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Sep 14 13:56:28 node-4 puppet-user[13417]: Finished catalog run in 0.08 seconds
Sep 14 13:56:30 node-4 puppet-user[14038]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 14 13:56:31 node-4 puppet-user[14038]: Compiled catalog for node-4.domain.tld in environment production in 1.25 seconds
Sep 14 13:56:31 node-4 puppet-user[14038]: (/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
Sep 14 13:56:31 node-4 puppet-user[14038]: (/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
Sep 14 13:56:31 node-4 puppet-user[14038]: (/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
Sep 14 13:56:31 node-4 puppet-user[14038]: (/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
Sep 14 13:56:31 node-4 puppet-user[14038]: (/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
Sep 14 13:56:31 node-4 puppet-user[14038]: (/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
Sep 14 13:56:31 node-4 puppet-user[14038]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 14 13:56:31 node-4 puppet-user[14038]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep 14 13:56:31 node-4 puppet-user[14038]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 14 13:56:31 node-4 puppet-user[14038]: (/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
Sep 14 13:56:31 node-4 puppet-user[14038]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep 14 13:56:31 node-4 puppet-user[14038]: (/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
Sep 14 13:56:31 node-4 puppet-user[14038]: (/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
Sep 14 13:56:31 node-4 puppet-user[14038]: (/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
Sep 14 13:56:31 node-4 puppet-user[14038]: (/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
Sep 14 13:56:31 node-4 puppet-user[14038]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep 14 13:56:40 node-4 puppet-user[14038]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Sep 14 13:56:40 node-4 puppet-user[14038]: Finished catalog run in 9.31 seconds
Sep 14 13:56:42 node-4 puppet-user[14760]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 14 13:56:42 node-4 puppet-user[14760]: Compiled catalog for node-4.domain.tld in environment production in 0.16 seconds
Sep 14 13:56:47 node-4 puppet-user[14760]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 14 13:57:01 node-4 CRON[16318]: (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")
Sep 14 13:57:15 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 14 13:57:15 node-4 nailgun-agent: I, [2016-09-14T13:57:15.388046 #16321]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 14 13:57:17 node-4 puppet-user[14760]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 14 13:57:17 node-4 puppet-user[14760]: Finished catalog run in 34.03 seconds
Sep 14 13:57:19 node-4 puppet-user[17340]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 14 13:57:19 node-4 puppet-user[17340]: Compiled catalog for node-4.domain.tld in environment production in 0.51 seconds
Sep 14 13:57:19 node-4 puppet-user[17340]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 14 13:57:19 node-4 puppet-user[17340]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 14 13:57:19 node-4 puppet-user[17340]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 14 13:57:19 node-4 puppet-user[17340]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 14 13:57:19 node-4 puppet-user[17340]: Finished catalog run in 0.09 seconds
Sep 14 13:57:21 node-4 puppet-user[17802]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 14 13:57:22 node-4 puppet-user[17802]: Compiled catalog for node-4.domain.tld in environment production in 0.81 seconds
Sep 14 13:57:22 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 14 13:57:22 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 14 13:57:22 node-4 crontab[18238]: (root) LIST (root)
Sep 14 13:57:22 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 14 13:57:22 node-4 crontab[18239]: (root) REPLACE (root)
Sep 14 13:57:24 node-4 puppet-user[17802]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/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
Sep 14 13:57:26 node-4 puppet-user[17802]: (/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
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/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
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/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
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/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
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/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
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/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
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/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
Sep 14 13:57:26 node-4 puppet-user[17802]: (/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
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 14 13:57:26 node-4 puppet-user[17802]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep 14 13:57:26 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8390" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 14 13:57:26 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 14 13:57:28 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:28 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:28 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:28 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:28 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:28 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:48 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:48 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:48 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:48 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:48 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:50 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:50 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:50 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:50 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:52 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:52 node-4 multipathd: uevent trigger error
<27>Sep 14 13:57:52 node-4 multipathd: uevent trigger error
<27>Sep 14 13:58:52 node-4 ntpdate[30430]: no servers can be used, exiting
<27>Sep 14 13:58:52 node-4 ntpdate[30645]: no servers can be used, exiting
<27>Sep 14 13:59:24 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:24 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:24 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:24 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:24 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:27 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:27 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:27 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:27 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:27 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:39 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:39 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:39 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:39 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:39 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:42 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:42 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:42 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:42 node-4 multipathd: uevent trigger error
<27>Sep 14 13:59:42 node-4 multipathd: uevent trigger error
<27>Sep 14 14:00:15 node-4 multipathd: uevent trigger error
<27>Sep 14 14:00:15 node-4 multipathd: uevent trigger error
<27>Sep 14 14:00:15 node-4 multipathd: uevent trigger error
<27>Sep 14 14:00:15 node-4 multipathd: uevent trigger error
<27>Sep 14 14:00:15 node-4 multipathd: uevent trigger error
<27>Sep 14 14:00:15 node-4 multipathd: uevent trigger error
<27>Sep 14 14:00:21 node-4 multipathd: uevent trigger error
<27>Sep 14 14:00:21 node-4 multipathd: uevent trigger error
<27>Sep 14 14:00:21 node-4 multipathd: uevent trigger error
<27>Sep 14 14:00:21 node-4 multipathd: uevent trigger error
<27>Sep 14 14:00:21 node-4 multipathd: uevent trigger error
<43>Sep 14 14:00:37 node-4 apache2_error [Wed Sep 14 14:00:33.488039 2016] [mpm_event:notice] [pid 14189:tid 140617065916288] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 14 14:00:37 node-4 apache2_error [Wed Sep 14 14:00:33.488140 2016] [core:notice] [pid 14189:tid 140617065916288] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 14 14:00:37 node-4 apache2_error [Wed Sep 14 14:00:36.518022 2016] [mpm_event:notice] [pid 14189:tid 140617065916288] AH00491: caught SIGTERM, shutting down
<27>Sep 14 14:00:41 node-4 multipathd: uevent trigger error
<27>Sep 14 14:00:41 node-4 multipathd: uevent trigger error
<27>Sep 14 14:00:41 node-4 multipathd: uevent trigger error
<27>Sep 14 14:00:41 node-4 multipathd: uevent trigger error
<27>Sep 14 14:00:41 node-4 multipathd: uevent trigger error
<43>Sep 14 14:00:47 node-4 apache2_error [Wed Sep 14 14:00:37.600432 2016] [mpm_worker:notice] [pid 14578:tid 139838989404032] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 14 14:00:47 node-4 apache2_error [Wed Sep 14 14:00:37.600506 2016] [core:notice] [pid 14578:tid 139838989404032] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 14 14:01:17 node-4 apache2_error [Wed Sep 14 14:01:15.274943 2016] [mpm_worker:notice] [pid 14578:tid 139838989404032] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 14 14:01:17 node-4 apache2_error [Wed Sep 14 14:01:15.283351 2016] [mpm_worker:warn] [pid 14578:tid 139838989404032] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 14 14:01:17 node-4 apache2_error [Wed Sep 14 14:01:15.284240 2016] [mpm_worker:notice] [pid 14578:tid 139838989404032] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 14 14:01:17 node-4 apache2_error [Wed Sep 14 14:01:15.284253 2016] [core:notice] [pid 14578:tid 139838989404032] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 14 14:01:18 node-4 multipathd: uevent trigger error
<27>Sep 14 14:01:18 node-4 multipathd: uevent trigger error
<27>Sep 14 14:01:18 node-4 multipathd: uevent trigger error
<27>Sep 14 14:01:18 node-4 multipathd: uevent trigger error
<27>Sep 14 14:01:18 node-4 multipathd: uevent trigger error
<27>Sep 14 14:01:52 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Sep 14 14:01:56 node-4 multipathd: uevent trigger error
<27>Sep 14 14:01:57 node-4 multipathd: uevent trigger error
<27>Sep 14 14:01:57 node-4 multipathd: uevent trigger error
<27>Sep 14 14:01:57 node-4 multipathd: uevent trigger error
<27>Sep 14 14:01:57 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:00 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:01 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:01 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:01 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:01 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:15 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:15 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:15 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:15 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:15 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:20 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:20 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:20 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:20 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:20 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:20 node-4 multipathd: uevent trigger error
<129>Sep 14 14:02:22 node-4 haproxy[28653]: 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>Sep 14 14:02:25 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:25 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:25 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:25 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:25 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:25 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:29 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:29 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:29 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:29 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:29 node-4 multipathd: uevent trigger error
<129>Sep 14 14:02:31 node-4 haproxy[31003]: 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>Sep 14 14:02:32 node-4 haproxy[31007]: 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>Sep 14 14:02:34 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:34 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:34 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:34 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:34 node-4 multipathd: uevent trigger error
<129>Sep 14 14:02:37 node-4 haproxy[32143]: 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>Sep 14 14:02:37 node-4 haproxy[32143]: 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>Sep 14 14:02:38 node-4 haproxy[32143]: 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>Sep 14 14:02:39 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:40 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:40 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:40 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:40 node-4 multipathd: uevent trigger error
<129>Sep 14 14:02:42 node-4 haproxy[879]: 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>Sep 14 14:02:42 node-4 haproxy[879]: 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>Sep 14 14:02:43 node-4 haproxy[883]: 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>Sep 14 14:02:43 node-4 haproxy[883]: 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>Sep 14 14:02:44 node-4 haproxy[883]: 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>Sep 14 14:02:45 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:45 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:45 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:45 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:45 node-4 multipathd: uevent trigger error
<129>Sep 14 14:02:47 node-4 haproxy[2031]: 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>Sep 14 14:02:48 node-4 haproxy[2035]: 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>Sep 14 14:02:48 node-4 haproxy[2035]: 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>Sep 14 14:02:48 node-4 haproxy[2035]: 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>Sep 14 14:02:49 node-4 haproxy[2035]: 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>Sep 14 14:02:49 node-4 haproxy[2035]: 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>Sep 14 14:02:50 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:50 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:50 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:50 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:50 node-4 multipathd: uevent trigger error
<129>Sep 14 14:02:51 node-4 haproxy[2035]: Server aodh/node-2 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>Sep 14 14:02:51 node-4 haproxy[2035]: Server aodh/node-5 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>Sep 14 14:02:51 node-4 haproxy[2035]: proxy aodh has no server available!
<129>Sep 14 14:02:53 node-4 haproxy[3166]: 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>Sep 14 14:02:53 node-4 haproxy[3166]: 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>Sep 14 14:02:53 node-4 haproxy[3166]: 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>Sep 14 14:02:54 node-4 haproxy[3170]: 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>Sep 14 14:02:54 node-4 haproxy[3170]: 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>Sep 14 14:02:54 node-4 haproxy[3170]: 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>Sep 14 14:02:54 node-4 haproxy[3170]: 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>Sep 14 14:02:56 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:56 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:56 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:56 node-4 multipathd: uevent trigger error
<27>Sep 14 14:02:56 node-4 multipathd: uevent trigger error
<129>Sep 14 14:02:56 node-4 haproxy[3170]: Server aodh/node-2 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>Sep 14 14:02:56 node-4 haproxy[3170]: Server aodh/node-5 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>Sep 14 14:02:56 node-4 haproxy[3170]: proxy aodh has no server available!
<129>Sep 14 14:02:56 node-4 haproxy[3170]: Server ceilometer/node-2 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>Sep 14 14:02:56 node-4 haproxy[3170]: Server ceilometer/node-5 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>Sep 14 14:02:56 node-4 haproxy[3170]: proxy ceilometer has no server available!
<129>Sep 14 14:02:58 node-4 haproxy[4316]: 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>Sep 14 14:02:58 node-4 haproxy[4316]: 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>Sep 14 14:02:59 node-4 haproxy[4320]: 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>Sep 14 14:02:59 node-4 haproxy[4320]: 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>Sep 14 14:02:59 node-4 haproxy[4320]: 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>Sep 14 14:02:59 node-4 haproxy[4320]: 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>Sep 14 14:03:00 node-4 haproxy[4320]: 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>Sep 14 14:03:01 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:01 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:01 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:01 node-4 multipathd: uevent trigger error
<129>Sep 14 14:03:01 node-4 haproxy[4320]: Server aodh/node-2 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>Sep 14 14:03:02 node-4 haproxy[4320]: Server aodh/node-5 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>Sep 14 14:03:02 node-4 haproxy[4320]: proxy aodh has no server available!
<129>Sep 14 14:03:02 node-4 haproxy[4320]: Server ceilometer/node-2 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>Sep 14 14:03:02 node-4 haproxy[4320]: Server ceilometer/node-5 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>Sep 14 14:03:02 node-4 haproxy[4320]: proxy ceilometer has no server available!
<129>Sep 14 14:03:04 node-4 haproxy[5462]: 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>Sep 14 14:03:04 node-4 haproxy[5462]: 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>Sep 14 14:03:04 node-4 haproxy[5462]: 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>Sep 14 14:03:04 node-4 haproxy[5462]: 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>Sep 14 14:03:05 node-4 haproxy[5462]: 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>Sep 14 14:03:05 node-4 haproxy[5462]: 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>Sep 14 14:03:05 node-4 haproxy[5462]: 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>Sep 14 14:03:05 node-4 haproxy[5462]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 14:03:06 node-4 haproxy[5462]: Server horizon/node-5 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>Sep 14 14:03:06 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:06 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:06 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:06 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:06 node-4 multipathd: uevent trigger error
<129>Sep 14 14:03:07 node-4 haproxy[5462]: Server aodh/node-2 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>Sep 14 14:03:07 node-4 haproxy[5462]: Server aodh/node-5 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>Sep 14 14:03:07 node-4 haproxy[5462]: proxy aodh has no server available!
<129>Sep 14 14:03:07 node-4 haproxy[5462]: Server ceilometer/node-2 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>Sep 14 14:03:07 node-4 haproxy[5462]: Server ceilometer/node-5 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>Sep 14 14:03:07 node-4 haproxy[5462]: proxy ceilometer has no server available!
<129>Sep 14 14:03:09 node-4 haproxy[6789]: 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>Sep 14 14:03:09 node-4 haproxy[6789]: 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>Sep 14 14:03:10 node-4 haproxy[6793]: 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>Sep 14 14:03:10 node-4 haproxy[6793]: 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>Sep 14 14:03:10 node-4 haproxy[6793]: 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>Sep 14 14:03:10 node-4 haproxy[6793]: 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.
<27>Sep 14 14:03:10 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Sep 14 14:03:10 node-4 haproxy[6793]: 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>Sep 14 14:03:11 node-4 haproxy[6793]: 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>Sep 14 14:03:11 node-4 haproxy[6793]: 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>Sep 14 14:03:11 node-4 haproxy[6793]: 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>Sep 14 14:03:11 node-4 haproxy[6793]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 14:03:11 node-4 haproxy[6793]: Server horizon/node-5 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>Sep 14 14:03:12 node-4 haproxy[6793]: Server glance-registry/node-2 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>Sep 14 14:03:12 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:12 node-4 multipathd: uevent trigger error
<129>Sep 14 14:03:12 node-4 haproxy[6793]: Server glance-registry/node-5 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>Sep 14 14:03:12 node-4 haproxy[6793]: proxy glance-registry has no server available!
<27>Sep 14 14:03:12 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:12 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:12 node-4 multipathd: uevent trigger error
<129>Sep 14 14:03:13 node-4 haproxy[6793]: Server aodh/node-2 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>Sep 14 14:03:13 node-4 haproxy[6793]: Server aodh/node-5 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>Sep 14 14:03:13 node-4 haproxy[6793]: proxy aodh has no server available!
<129>Sep 14 14:03:13 node-4 haproxy[6793]: Server ceilometer/node-2 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>Sep 14 14:03:13 node-4 haproxy[6793]: Server ceilometer/node-5 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>Sep 14 14:03:13 node-4 haproxy[6793]: proxy ceilometer has no server available!
<129>Sep 14 14:03:15 node-4 haproxy[8010]: 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>Sep 14 14:03:15 node-4 haproxy[8010]: 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>Sep 14 14:03:15 node-4 haproxy[8010]: 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>Sep 14 14:03:15 node-4 haproxy[8010]: 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>Sep 14 14:03:15 node-4 haproxy[8010]: 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>Sep 14 14:03:16 node-4 haproxy[8014]: 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>Sep 14 14:03:16 node-4 haproxy[8014]: 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>Sep 14 14:03:16 node-4 haproxy[8014]: 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>Sep 14 14:03:16 node-4 haproxy[8014]: 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>Sep 14 14:03:16 node-4 haproxy[8014]: 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>Sep 14 14:03:16 node-4 haproxy[8014]: 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>Sep 14 14:03:16 node-4 haproxy[8014]: 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>Sep 14 14:03:17 node-4 haproxy[8014]: 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>Sep 14 14:03:17 node-4 haproxy[8014]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 14:03:17 node-4 haproxy[8014]: Server horizon/node-5 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>Sep 14 14:03:18 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:18 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:18 node-4 multipathd: uevent trigger error
<129>Sep 14 14:03:18 node-4 haproxy[8014]: Server glance-registry/node-2 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>Sep 14 14:03:18 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:18 node-4 multipathd: uevent trigger error
<129>Sep 14 14:03:18 node-4 haproxy[8014]: Server glance-registry/node-5 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>Sep 14 14:03:18 node-4 haproxy[8014]: proxy glance-registry has no server available!
<129>Sep 14 14:03:18 node-4 haproxy[8014]: Server aodh/node-2 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>Sep 14 14:03:18 node-4 haproxy[8014]: Server aodh/node-5 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>Sep 14 14:03:18 node-4 haproxy[8014]: proxy aodh has no server available!
<129>Sep 14 14:03:18 node-4 haproxy[8014]: Server ceilometer/node-2 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>Sep 14 14:03:18 node-4 haproxy[8014]: Server ceilometer/node-5 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>Sep 14 14:03:18 node-4 haproxy[8014]: proxy ceilometer has no server available!
<129>Sep 14 14:03:19 node-4 haproxy[8014]: Server nova-novncproxy/node-2 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>Sep 14 14:03:19 node-4 haproxy[8014]: Server nova-novncproxy/node-5 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>Sep 14 14:03:19 node-4 haproxy[8014]: proxy nova-novncproxy has no server available!
<129>Sep 14 14:03:20 node-4 haproxy[9181]: 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>Sep 14 14:03:20 node-4 haproxy[9181]: 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>Sep 14 14:03:20 node-4 haproxy[9181]: 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>Sep 14 14:03:21 node-4 haproxy[9185]: 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>Sep 14 14:03:21 node-4 haproxy[9185]: 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>Sep 14 14:03:21 node-4 haproxy[9185]: 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>Sep 14 14:03:21 node-4 haproxy[9185]: 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>Sep 14 14:03:21 node-4 haproxy[9185]: 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>Sep 14 14:03:21 node-4 haproxy[9185]: 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>Sep 14 14:03:21 node-4 haproxy[9185]: 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>Sep 14 14:03:22 node-4 haproxy[9185]: 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>Sep 14 14:03:22 node-4 haproxy[9185]: 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>Sep 14 14:03:22 node-4 haproxy[9185]: 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>Sep 14 14:03:22 node-4 haproxy[9185]: 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>Sep 14 14:03:22 node-4 haproxy[9185]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 14:03:22 node-4 haproxy[9185]: Server horizon/node-5 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>Sep 14 14:03:23 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:23 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:23 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:23 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:23 node-4 multipathd: uevent trigger error
<129>Sep 14 14:03:23 node-4 haproxy[9185]: Server glance-registry/node-2 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>Sep 14 14:03:23 node-4 haproxy[9185]: Server glance-registry/node-5 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>Sep 14 14:03:23 node-4 haproxy[9185]: proxy glance-registry has no server available!
<129>Sep 14 14:03:24 node-4 haproxy[9185]: Server aodh/node-2 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>Sep 14 14:03:24 node-4 haproxy[9185]: Server aodh/node-5 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>Sep 14 14:03:24 node-4 haproxy[9185]: proxy aodh has no server available!
<129>Sep 14 14:03:24 node-4 haproxy[9185]: Server ceilometer/node-2 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>Sep 14 14:03:24 node-4 haproxy[9185]: Server ceilometer/node-5 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>Sep 14 14:03:24 node-4 haproxy[9185]: proxy ceilometer has no server available!
<129>Sep 14 14:03:24 node-4 haproxy[9185]: Server nova-novncproxy/node-2 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>Sep 14 14:03:24 node-4 haproxy[9185]: Server nova-novncproxy/node-5 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>Sep 14 14:03:24 node-4 haproxy[9185]: proxy nova-novncproxy has no server available!
<129>Sep 14 14:03:26 node-4 haproxy[10598]: 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>Sep 14 14:03:26 node-4 haproxy[10598]: 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>Sep 14 14:03:26 node-4 haproxy[10598]: 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>Sep 14 14:03:26 node-4 haproxy[10598]: 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>Sep 14 14:03:26 node-4 haproxy[10598]: 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>Sep 14 14:03:27 node-4 haproxy[10604]: 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>Sep 14 14:03:27 node-4 haproxy[10604]: 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>Sep 14 14:03:27 node-4 haproxy[10604]: 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>Sep 14 14:03:27 node-4 haproxy[10604]: 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>Sep 14 14:03:27 node-4 haproxy[10604]: 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>Sep 14 14:03:27 node-4 haproxy[10604]: 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>Sep 14 14:03:27 node-4 haproxy[10604]: 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>Sep 14 14:03:27 node-4 haproxy[10604]: 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>Sep 14 14:03:27 node-4 haproxy[10604]: 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>Sep 14 14:03:28 node-4 haproxy[10604]: 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>Sep 14 14:03:28 node-4 haproxy[10604]: 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>Sep 14 14:03:28 node-4 haproxy[10604]: 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>Sep 14 14:03:28 node-4 haproxy[10604]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 14:03:28 node-4 haproxy[10604]: Server horizon/node-5 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>Sep 14 14:03:29 node-4 haproxy[10604]: Server glance-registry/node-2 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>Sep 14 14:03:29 node-4 haproxy[10604]: Server glance-registry/node-5 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>Sep 14 14:03:29 node-4 haproxy[10604]: proxy glance-registry has no server available!
<27>Sep 14 14:03:29 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:29 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:29 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:29 node-4 multipathd: uevent trigger error
<129>Sep 14 14:03:29 node-4 haproxy[10604]: Server aodh/node-2 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>Sep 14 14:03:29 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:29 node-4 multipathd: uevent trigger error
<129>Sep 14 14:03:29 node-4 haproxy[10604]: Server aodh/node-5 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>Sep 14 14:03:29 node-4 haproxy[10604]: proxy aodh has no server available!
<129>Sep 14 14:03:29 node-4 haproxy[10604]: Server ceilometer/node-2 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>Sep 14 14:03:29 node-4 haproxy[10604]: Server ceilometer/node-5 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>Sep 14 14:03:29 node-4 haproxy[10604]: proxy ceilometer has no server available!
<129>Sep 14 14:03:30 node-4 haproxy[10604]: Server nova-novncproxy/node-2 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>Sep 14 14:03:30 node-4 haproxy[10604]: Server nova-novncproxy/node-5 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>Sep 14 14:03:30 node-4 haproxy[10604]: proxy nova-novncproxy has no server available!
<27>Sep 14 14:03:32 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:32 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:32 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:32 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:32 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:36 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:36 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:36 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:36 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:36 node-4 multipathd: uevent trigger error
<129>Sep 14 14:03:36 node-4 haproxy[10604]: Server keystone-1/node-2 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>Sep 14 14:03:36 node-4 haproxy[10604]: Server keystone-1/node-5 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>Sep 14 14:03:36 node-4 haproxy[10604]: proxy keystone-1 has no server available!
<129>Sep 14 14:03:36 node-4 haproxy[10604]: Server keystone-2/node-2 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>Sep 14 14:03:36 node-4 haproxy[10604]: Server keystone-2/node-5 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>Sep 14 14:03:36 node-4 haproxy[10604]: proxy keystone-2 has no server available!
<129>Sep 14 14:03:36 node-4 haproxy[10604]: Server nova-api/node-2 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>Sep 14 14:03:36 node-4 haproxy[10604]: Server nova-api/node-5 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>Sep 14 14:03:36 node-4 haproxy[10604]: proxy nova-api has no server available!
<129>Sep 14 14:03:36 node-4 haproxy[10604]: Server nova-metadata-api/node-2 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>Sep 14 14:03:36 node-4 haproxy[10604]: Server nova-metadata-api/node-5 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>Sep 14 14:03:36 node-4 haproxy[10604]: proxy nova-metadata-api has no server available!
<129>Sep 14 14:03:36 node-4 haproxy[10604]: Server cinder-api/node-2 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>Sep 14 14:03:36 node-4 haproxy[10604]: Backup Server cinder-api/node-5 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>Sep 14 14:03:36 node-4 haproxy[10604]: proxy cinder-api has no server available!
<129>Sep 14 14:03:37 node-4 haproxy[10604]: Server glance-api/node-2 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>Sep 14 14:03:37 node-4 haproxy[10604]: Server glance-api/node-5 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>Sep 14 14:03:37 node-4 haproxy[10604]: proxy glance-api has no server available!
<129>Sep 14 14:03:37 node-4 haproxy[10604]: Server glance-glare/node-2 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>Sep 14 14:03:37 node-4 haproxy[10604]: Server glance-glare/node-5 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>Sep 14 14:03:37 node-4 haproxy[10604]: proxy glance-glare has no server available!
<129>Sep 14 14:03:37 node-4 haproxy[10604]: Server neutron/node-2 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>Sep 14 14:03:37 node-4 haproxy[10604]: Server neutron/node-5 is DOWN, reason: Layer4 timeout, check duration: 10002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 14 14:03:37 node-4 haproxy[10604]: proxy neutron has no server available!
<129>Sep 14 14:03:37 node-4 haproxy[10604]: Server mysqld/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 14 14:03:37 node-4 haproxy[10604]: Backup Server mysqld/node-5 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>Sep 14 14:03:37 node-4 haproxy[10604]: proxy mysqld has no server available!
<129>Sep 14 14:03:37 node-4 haproxy[10604]: Server object-storage/node-2 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>Sep 14 14:03:37 node-4 haproxy[10604]: Server object-storage/node-5 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>Sep 14 14:03:37 node-4 haproxy[10604]: proxy object-storage has no server available!
<129>Sep 14 14:03:37 node-4 haproxy[10604]: Server heat-api/node-2 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>Sep 14 14:03:37 node-4 haproxy[10604]: Server heat-api/node-5 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>Sep 14 14:03:37 node-4 haproxy[10604]: proxy heat-api has no server available!
<129>Sep 14 14:03:37 node-4 haproxy[10604]: Server heat-api-cfn/node-2 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>Sep 14 14:03:38 node-4 haproxy[10604]: Server heat-api-cfn/node-5 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>Sep 14 14:03:38 node-4 haproxy[10604]: proxy heat-api-cfn has no server available!
<129>Sep 14 14:03:38 node-4 haproxy[10604]: Server heat-api-cloudwatch/node-2 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>Sep 14 14:03:38 node-4 haproxy[10604]: Server heat-api-cloudwatch/node-5 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>Sep 14 14:03:38 node-4 haproxy[10604]: proxy heat-api-cloudwatch has no server available!
<27>Sep 14 14:03:40 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:40 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:40 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:40 node-4 multipathd: uevent trigger error
<27>Sep 14 14:03:58 node-4 multipathd: uevent trigger error
<27>Sep 14 14:04:04 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 14 14:04:04 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 14 14:04:13 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 14 14:04:13 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 14 14:04:13 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 14 14:04:29 node-4 multipathd: uevent trigger error
<27>Sep 14 14:04:29 node-4 multipathd: uevent trigger error
<27>Sep 14 14:04:29 node-4 multipathd: uevent trigger error
<27>Sep 14 14:04:29 node-4 multipathd: uevent trigger error
<27>Sep 14 14:04:29 node-4 multipathd: uevent trigger error
<27>Sep 14 14:04:39 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 14 14:05:41 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>Sep 14 14:05:43 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 14 14:06:58 node-4 multipathd: uevent trigger error
<27>Sep 14 14:06:58 node-4 multipathd: uevent trigger error
<27>Sep 14 14:06:58 node-4 multipathd: uevent trigger error
<27>Sep 14 14:06:58 node-4 multipathd: uevent trigger error
<27>Sep 14 14:06:58 node-4 multipathd: uevent trigger error
<11>Sep 14 14:08:06 node-4 epmd: epmd: node name already occupied rabbitmq-cli-03
<27>Sep 14 14:10:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:10:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:10:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:10:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:10:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:10:07 node-4 multipathd: uevent trigger error
<43>Sep 14 14:11:17 node-4 apache2_error [Wed Sep 14 14:11:16.032966 2016] [mpm_worker:notice] [pid 14578:tid 139838989404032] AH00295: caught SIGTERM, shutting down
<43>Sep 14 14:11:17 node-4 apache2_error [Wed Sep 14 14:11:16.787128 2016] [mpm_worker:notice] [pid 17749:tid 140443037521792] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 14 14:11:17 node-4 apache2_error [Wed Sep 14 14:11:16.787181 2016] [core:notice] [pid 17749:tid 140443037521792] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 14 14:11:54 node-4 multipathd: uevent trigger error
<27>Sep 14 14:11:54 node-4 multipathd: uevent trigger error
<27>Sep 14 14:11:54 node-4 multipathd: uevent trigger error
<27>Sep 14 14:11:54 node-4 multipathd: uevent trigger error
<27>Sep 14 14:11:54 node-4 multipathd: uevent trigger error
<27>Sep 14 14:11:54 node-4 multipathd: uevent trigger error
<43>Sep 14 14:11:58 node-4 apache2_error [Wed Sep 14 14:11:48.738022 2016] [mpm_worker:notice] [pid 17749:tid 140443037521792] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 14 14:11:58 node-4 apache2_error [Wed Sep 14 14:11:48.746930 2016] [mpm_worker:warn] [pid 17749:tid 140443037521792] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 14 14:11:58 node-4 apache2_error [Wed Sep 14 14:11:48.751991 2016] [mpm_worker:notice] [pid 17749:tid 140443037521792] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 14 14:11:58 node-4 apache2_error [Wed Sep 14 14:11:48.752016 2016] [core:notice] [pid 17749:tid 140443037521792] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 14 14:12:57 node-4 multipathd: uevent trigger error
<27>Sep 14 14:12:57 node-4 multipathd: uevent trigger error
<27>Sep 14 14:12:57 node-4 multipathd: uevent trigger error
<27>Sep 14 14:12:57 node-4 multipathd: uevent trigger error
<27>Sep 14 14:12:57 node-4 multipathd: uevent trigger error
<27>Sep 14 14:14:12 node-4 multipathd: uevent trigger error
<27>Sep 14 14:14:12 node-4 multipathd: uevent trigger error
<27>Sep 14 14:14:12 node-4 multipathd: uevent trigger error
<27>Sep 14 14:14:12 node-4 multipathd: uevent trigger error
<27>Sep 14 14:14:12 node-4 multipathd: uevent trigger error
<11>Sep 14 14:14:14 node-4 epmd: epmd: node name already occupied rabbitmq-cli-03
<11>Sep 14 14:15:30 node-4 epmd: epmd: node name already occupied rabbitmq-cli-03
<27>Sep 14 14:18:02 node-4 multipathd: uevent trigger error
<27>Sep 14 14:18:02 node-4 multipathd: uevent trigger error
<27>Sep 14 14:18:02 node-4 multipathd: uevent trigger error
<27>Sep 14 14:18:02 node-4 multipathd: uevent trigger error
<27>Sep 14 14:18:02 node-4 multipathd: uevent trigger error
<27>Sep 14 14:20:06 node-4 multipathd: uevent trigger error
<27>Sep 14 14:20:06 node-4 multipathd: uevent trigger error
<27>Sep 14 14:20:06 node-4 multipathd: uevent trigger error
<27>Sep 14 14:20:06 node-4 multipathd: uevent trigger error
<27>Sep 14 14:20:06 node-4 multipathd: uevent trigger error
<27>Sep 14 14:21:15 node-4 multipathd: uevent trigger error
<27>Sep 14 14:21:15 node-4 multipathd: uevent trigger error
<27>Sep 14 14:21:15 node-4 multipathd: uevent trigger error
<27>Sep 14 14:21:15 node-4 multipathd: uevent trigger error
<27>Sep 14 14:21:15 node-4 multipathd: uevent trigger error
<27>Sep 14 14:21:15 node-4 multipathd: uevent trigger error
<11>Sep 14 14:21:37 node-4 epmd: epmd: node name already occupied rabbitmq-cli-03
<27>Sep 14 14:21:51 node-4 multipathd: uevent trigger error
<27>Sep 14 14:21:51 node-4 multipathd: uevent trigger error
<27>Sep 14 14:21:51 node-4 multipathd: uevent trigger error
<27>Sep 14 14:21:51 node-4 multipathd: uevent trigger error
<27>Sep 14 14:21:51 node-4 multipathd: uevent trigger error
<27>Sep 14 14:22:01 node-4 multipathd: uevent trigger error
<27>Sep 14 14:22:01 node-4 multipathd: uevent trigger error
<27>Sep 14 14:22:01 node-4 multipathd: uevent trigger error
<27>Sep 14 14:22:01 node-4 multipathd: uevent trigger error
<27>Sep 14 14:22:01 node-4 multipathd: uevent trigger error
<27>Sep 14 14:22:01 node-4 multipathd: uevent trigger error
<27>Sep 14 14:22:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:22:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:22:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:22:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:22:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:22:12 node-4 multipathd: uevent trigger error
<27>Sep 14 14:22:12 node-4 multipathd: uevent trigger error
<27>Sep 14 14:22:12 node-4 multipathd: uevent trigger error
<27>Sep 14 14:22:12 node-4 multipathd: uevent trigger error
<27>Sep 14 14:22:12 node-4 multipathd: uevent trigger error
<43>Sep 14 14:23:08 node-4 apache2_error [Wed Sep 14 14:22:59.559606 2016] [mpm_worker:notice] [pid 17749:tid 140443037521792] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 14 14:23:08 node-4 apache2_error [Wed Sep 14 14:22:59.945802 2016] [mpm_worker:warn] [pid 17749:tid 140443037521792] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 14 14:23:08 node-4 apache2_error [Wed Sep 14 14:22:59.950183 2016] [mpm_worker:notice] [pid 17749:tid 140443037521792] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 14 14:23:08 node-4 apache2_error [Wed Sep 14 14:22:59.950199 2016] [core:notice] [pid 17749:tid 140443037521792] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 14 14:23:38 node-4 apache2_error [Wed Sep 14 14:23:36.850536 2016] [mpm_worker:notice] [pid 17749:tid 140443037521792] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 14 14:23:38 node-4 apache2_error [Wed Sep 14 14:23:37.044932 2016] [mpm_worker:warn] [pid 17749:tid 140443037521792] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 14 14:23:38 node-4 apache2_error [Wed Sep 14 14:23:37.053083 2016] [mpm_worker:notice] [pid 17749:tid 140443037521792] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 14 14:23:38 node-4 apache2_error [Wed Sep 14 14:23:37.053118 2016] [core:notice] [pid 17749:tid 140443037521792] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 14 14:23:41 node-4 multipathd: uevent trigger error
<27>Sep 14 14:23:41 node-4 multipathd: uevent trigger error
<27>Sep 14 14:23:41 node-4 multipathd: uevent trigger error
<27>Sep 14 14:23:41 node-4 multipathd: uevent trigger error
<27>Sep 14 14:23:41 node-4 multipathd: uevent trigger error
<27>Sep 14 14:23:41 node-4 multipathd: uevent trigger error
<27>Sep 14 14:24:33 node-4 multipathd: uevent trigger error
<27>Sep 14 14:24:33 node-4 multipathd: uevent trigger error
<27>Sep 14 14:24:33 node-4 multipathd: uevent trigger error
<27>Sep 14 14:24:33 node-4 multipathd: uevent trigger error
<27>Sep 14 14:24:33 node-4 multipathd: uevent trigger error
<27>Sep 14 14:24:46 node-4 multipathd: uevent trigger error
<27>Sep 14 14:24:46 node-4 multipathd: uevent trigger error
<27>Sep 14 14:24:46 node-4 multipathd: uevent trigger error
<27>Sep 14 14:24:46 node-4 multipathd: uevent trigger error
<11>Sep 14 14:24:51 node-4 epmd: epmd: node name already occupied rabbitmq-cli-03
<27>Sep 14 14:26:23 node-4 multipathd: uevent trigger error
<27>Sep 14 14:26:23 node-4 multipathd: uevent trigger error
<27>Sep 14 14:26:23 node-4 multipathd: uevent trigger error
<27>Sep 14 14:26:23 node-4 multipathd: uevent trigger error
<27>Sep 14 14:26:23 node-4 multipathd: uevent trigger error
<11>Sep 14 14:26:49 node-4 epmd: epmd: node name already occupied rabbitmq-cli-03
<27>Sep 14 14:27:12 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:12 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:12 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:12 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:12 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:25 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:25 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:25 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:25 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:25 node-4 multipathd: uevent trigger error
<11>Sep 14 14:27:34 node-4 liberasurecode[11683]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:34 node-4 liberasurecode[11683]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:34 node-4 liberasurecode[11683]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:34 node-4 liberasurecode[11683]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:34 node-4 liberasurecode[11729]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:34 node-4 liberasurecode[11729]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:34 node-4 liberasurecode[11729]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:34 node-4 liberasurecode[11729]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:36 node-4 liberasurecode[12694]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:36 node-4 liberasurecode[12694]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:36 node-4 liberasurecode[12694]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:36 node-4 liberasurecode[12694]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[13344]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[13344]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[13344]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[13344]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[13380]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[13380]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[13380]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[13380]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14307]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14307]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14307]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14307]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14367]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14367]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14367]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14367]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14379]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14379]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14379]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14379]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14391]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14391]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14391]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14391]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14403]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14403]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14403]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:27:42 node-4 liberasurecode[14403]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 14 14:27:49 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:49 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:49 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:49 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:49 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:54 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:54 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:54 node-4 multipathd: uevent trigger error
<27>Sep 14 14:27:54 node-4 multipathd: uevent trigger error
<11>Sep 14 14:28:12 node-4 epmd: epmd: node name already occupied rabbitmq-cli-03
<11>Sep 14 14:28:13 node-4 epmd: epmd: node name already occupied rabbitmq-cli-03
<27>Sep 14 14:28:58 node-4 multipathd: uevent trigger error
<27>Sep 14 14:28:58 node-4 multipathd: uevent trigger error
<27>Sep 14 14:28:58 node-4 multipathd: uevent trigger error
<27>Sep 14 14:28:58 node-4 multipathd: uevent trigger error
<11>Sep 14 14:30:01 node-4 liberasurecode[2217]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:30:01 node-4 liberasurecode[2217]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:30:01 node-4 liberasurecode[2217]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:30:01 node-4 liberasurecode[2217]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 14 14:31:03 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:03 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:03 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:03 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:04 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:08 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:08 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:08 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:08 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:08 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:22 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:22 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:22 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:22 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:35 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:35 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:35 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:35 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:35 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:40 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:40 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:40 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:40 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:40 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:40 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:53 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:53 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:53 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:53 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:53 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:53 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:58 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:58 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:58 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:58 node-4 multipathd: uevent trigger error
<27>Sep 14 14:31:58 node-4 multipathd: uevent trigger error
<27>Sep 14 14:32:02 node-4 multipathd: uevent trigger error
<27>Sep 14 14:32:02 node-4 multipathd: uevent trigger error
<27>Sep 14 14:32:02 node-4 multipathd: uevent trigger error
<27>Sep 14 14:32:02 node-4 multipathd: uevent trigger error
<27>Sep 14 14:32:02 node-4 multipathd: uevent trigger error
<27>Sep 14 14:32:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:32:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:32:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:32:07 node-4 multipathd: uevent trigger error
<27>Sep 14 14:32:07 node-4 multipathd: uevent trigger error
<11>Sep 14 14:32:20 node-4 epmd: epmd: node name already occupied rabbitmq-cli-03
<11>Sep 14 14:35:01 node-4 liberasurecode[21774]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:35:01 node-4 liberasurecode[21774]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:35:01 node-4 liberasurecode[21774]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 14 14:35:01 node-4 liberasurecode[21774]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
