Sep 22 16:58:02 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8422" x-info="http://www.rsyslog.com"] start
Sep 22 16:58:02 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 22 16:58:02 node-4 rsyslogd: rsyslogd's groupid changed to 104
Sep 22 16:58:02 node-4 rsyslogd: rsyslogd's userid changed to 101
Sep 22 16:58:02 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 22 16:58:02 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 22 16:58:02 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 22 16:58:02 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 22 16:58:02 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=ad8d3264-a915-4372-8c72-624d195dffbf nomdmonddf nomdmonisw
Sep 22 16:58:02 node-4 kernel: [    0.000000] KERNEL supported cpus:
Sep 22 16:58:02 node-4 kernel: [    0.000000]   Intel GenuineIntel
Sep 22 16:58:02 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Sep 22 16:58:02 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Sep 22 16:58:02 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 22 16:58:02 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 22 16:58:02 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 22 16:58:02 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 22 16:58:02 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 22 16:58:02 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 22 16:58:02 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 22 16:58:02 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 22 16:58:02 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 22 16:58:02 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 22 16:58:02 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 22 16:58:02 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 22 16:58:02 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 22 16:58:02 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 22 16:58:02 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 22 16:58:02 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 22 16:58:02 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 22 16:58:02 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 22 16:58:02 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 22 16:58:02 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 22 16:58:02 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 22 16:58:02 node-4 kernel: [    0.000000] No AGP bridge found
Sep 22 16:58:02 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 22 16:58:02 node-4 kernel: [    0.000000] MTRR default type: write-back
Sep 22 16:58:02 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 22 16:58:02 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Sep 22 16:58:02 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 22 16:58:02 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 22 16:58:02 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 22 16:58:02 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 22 16:58:02 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 22 16:58:02 node-4 kernel: [    0.000000]   2 disabled
Sep 22 16:58:02 node-4 kernel: [    0.000000]   3 disabled
Sep 22 16:58:02 node-4 kernel: [    0.000000]   4 disabled
Sep 22 16:58:02 node-4 kernel: [    0.000000]   5 disabled
Sep 22 16:58:02 node-4 kernel: [    0.000000]   6 disabled
Sep 22 16:58:02 node-4 kernel: [    0.000000]   7 disabled
Sep 22 16:58:02 node-4 kernel: [    0.000000]   8 disabled
Sep 22 16:58:02 node-4 kernel: [    0.000000]   9 disabled
Sep 22 16:58:02 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 22 16:58:02 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 22 16:58:02 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 22 16:58:02 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 22 16:58:02 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 22 16:58:02 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Sep 22 16:58:02 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 22 16:58:02 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 22 16:58:02 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 22 16:58:02 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 22 16:58:02 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 22 16:58:02 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 22 16:58:02 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 22 16:58:02 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 22 16:58:02 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 22 16:58:02 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 22 16:58:02 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 22 16:58:02 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 22 16:58:02 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 22 16:58:02 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 22 16:58:02 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 22 16:58:02 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 22 16:58:02 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 22 16:58:02 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 22 16:58:02 node-4 kernel: [    0.000000] Zone ranges:
Sep 22 16:58:02 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] Movable zone start for each node
Sep 22 16:58:02 node-4 kernel: [    0.000000] Early memory node ranges
Sep 22 16:58:02 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 22 16:58:02 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 22 16:58:02 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 22 16:58:02 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 22 16:58:02 node-4 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 22 16:58:02 node-4 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 22 16:58:02 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 22 16:58:02 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 22 16:58:02 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 22 16:58:02 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 22 16:58:02 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 22 16:58:02 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 22 16:58:02 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 22 16:58:02 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 22 16:58:02 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 22 16:58:02 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 22 16:58:02 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 22 16:58:02 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 22 16:58:02 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 22 16:58:02 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 22 16:58:02 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 22 16:58:02 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 22 16:58:02 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 22 16:58:02 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 22 16:58:02 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 22 16:58:02 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 22 16:58:02 node-4 kernel: [    0.000000] Policy zone: Normal
Sep 22 16:58:02 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=ad8d3264-a915-4372-8c72-624d195dffbf nomdmonddf nomdmonisw
Sep 22 16:58:02 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 22 16:58:02 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 22 16:58:02 node-4 kernel: [    0.000000] Checking aperture...
Sep 22 16:58:02 node-4 kernel: [    0.000000] No AGP bridge found
Sep 22 16:58:02 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 22 16:58:02 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 22 16:58:02 node-4 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Sep 22 16:58:02 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 22 16:58:02 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 22 16:58:02 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 22 16:58:02 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 22 16:58:02 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 22 16:58:02 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 22 16:58:02 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 22 16:58:02 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 22 16:58:02 node-4 kernel: [    0.000000] console [tty0] enabled
Sep 22 16:58:02 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 22 16:58:02 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 22 16:58:02 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 22 16:58:02 node-4 kernel: [    0.000000] hpet clockevent registered
Sep 22 16:58:02 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 22 16:58:02 node-4 kernel: [    0.004000] tsc: Detected 3492.188 MHz processor
Sep 22 16:58:02 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.37 BogoMIPS (lpj=13968752)
Sep 22 16:58:02 node-4 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Sep 22 16:58:02 node-4 kernel: [    0.000043] Security Framework initialized
Sep 22 16:58:02 node-4 kernel: [    0.000062] AppArmor: AppArmor initialized
Sep 22 16:58:02 node-4 kernel: [    0.000064] Yama: becoming mindful.
Sep 22 16:58:02 node-4 kernel: [    0.001458] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 22 16:58:02 node-4 kernel: [    0.006374] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 22 16:58:02 node-4 kernel: [    0.008301] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 22 16:58:02 node-4 kernel: [    0.008329] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 22 16:58:02 node-4 kernel: [    0.008619] Initializing cgroup subsys memory
Sep 22 16:58:02 node-4 kernel: [    0.008628] Initializing cgroup subsys devices
Sep 22 16:58:02 node-4 kernel: [    0.008629] Initializing cgroup subsys freezer
Sep 22 16:58:02 node-4 kernel: [    0.008631] Initializing cgroup subsys blkio
Sep 22 16:58:02 node-4 kernel: [    0.008633] Initializing cgroup subsys perf_event
Sep 22 16:58:02 node-4 kernel: [    0.008635] Initializing cgroup subsys hugetlb
Sep 22 16:58:02 node-4 kernel: [    0.008655] CPU: Physical Processor ID: 0
Sep 22 16:58:02 node-4 kernel: [    0.008656] CPU: Processor Core ID: 0
Sep 22 16:58:02 node-4 kernel: [    0.008660] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 22 16:58:02 node-4 kernel: [    0.008660] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 22 16:58:02 node-4 kernel: [    0.009353] mce: CPU supports 22 MCE banks
Sep 22 16:58:02 node-4 kernel: [    0.009381] CPU0: Thermal monitoring enabled (TM1)
Sep 22 16:58:02 node-4 kernel: [    0.009402] process: using mwait in idle threads
Sep 22 16:58:02 node-4 kernel: [    0.009405] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 22 16:58:02 node-4 kernel: [    0.009405] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 22 16:58:02 node-4 kernel: [    0.009405] tlb_flushall_shift: 6
Sep 22 16:58:02 node-4 kernel: [    0.009493] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 22 16:58:02 node-4 kernel: [    0.010217] ACPI: Core revision 20131115
Sep 22 16:58:02 node-4 kernel: [    0.022901] ACPI: All ACPI Tables successfully acquired
Sep 22 16:58:02 node-4 kernel: [    0.023061] ftrace: allocating 28617 entries in 112 pages
Sep 22 16:58:02 node-4 kernel: [    0.032043] dmar: Host address width 46
Sep 22 16:58:02 node-4 kernel: [    0.032046] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 22 16:58:02 node-4 kernel: [    0.032052] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 22 16:58:02 node-4 kernel: [    0.032053] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 22 16:58:02 node-4 kernel: [    0.032057] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 22 16:58:02 node-4 kernel: [    0.032059] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 22 16:58:02 node-4 kernel: [    0.032060] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 22 16:58:02 node-4 kernel: [    0.032061] dmar: ATSR flags: 0x0
Sep 22 16:58:02 node-4 kernel: [    0.032062] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 22 16:58:02 node-4 kernel: [    0.032063] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 22 16:58:02 node-4 kernel: [    0.032179] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 22 16:58:02 node-4 kernel: [    0.032180] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 22 16:58:02 node-4 kernel: [    0.032181] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 22 16:58:02 node-4 kernel: [    0.032182] HPET id 0 under DRHD base 0xc7ffc000
Sep 22 16:58:02 node-4 kernel: [    0.032183] Your BIOS is broken and requested that x2apic be disabled.
Sep 22 16:58:02 node-4 kernel: [    0.032183] This will slightly decrease performance.
Sep 22 16:58:02 node-4 kernel: [    0.032183] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 22 16:58:02 node-4 kernel: [    0.032617] Enabled IRQ remapping in xapic mode
Sep 22 16:58:02 node-4 kernel: [    0.032618] x2apic not enabled, IRQ remapping is in xapic mode
Sep 22 16:58:02 node-4 kernel: [    0.032621] Switched APIC routing to physical flat.
Sep 22 16:58:02 node-4 kernel: [    0.033245] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 22 16:58:02 node-4 kernel: [    0.072898] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 22 16:58:02 node-4 kernel: [    0.072904] TSC deadline timer enabled
Sep 22 16:58:02 node-4 kernel: [    0.072911] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 22 16:58:02 node-4 kernel: [    0.072917] ... version:                3
Sep 22 16:58:02 node-4 kernel: [    0.072918] ... bit width:              48
Sep 22 16:58:02 node-4 kernel: [    0.072919] ... generic registers:      4
Sep 22 16:58:02 node-4 kernel: [    0.072920] ... value mask:             0000ffffffffffff
Sep 22 16:58:02 node-4 kernel: [    0.072921] ... max period:             0000ffffffffffff
Sep 22 16:58:02 node-4 kernel: [    0.072922] ... fixed-purpose events:   3
Sep 22 16:58:02 node-4 kernel: [    0.072923] ... event mask:             000000070000000f
Sep 22 16:58:02 node-4 kernel: [    0.074302] x86: Booting SMP configuration:
Sep 22 16:58:02 node-4 kernel: [    0.088408] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 22 16:58:02 node-4 kernel: [    0.074304] .... node  #0, CPUs:        #1  #2  #3
Sep 22 16:58:02 node-4 kernel: [    0.116324] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 22 16:58:02 node-4 kernel: [    0.270466] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 22 16:58:02 node-4 kernel: [    0.326092] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 22 16:58:02 node-4 kernel: [    0.382947] x86: Booted up 2 nodes, 16 CPUs
Sep 22 16:58:02 node-4 kernel: [    0.382950] smpboot: Total of 16 processors activated (111761.37 BogoMIPS)
Sep 22 16:58:02 node-4 kernel: [    0.406688] devtmpfs: initialized
Sep 22 16:58:02 node-4 kernel: [    0.409792] EVM: security.selinux
Sep 22 16:58:02 node-4 kernel: [    0.409794] EVM: security.SMACK64
Sep 22 16:58:02 node-4 kernel: [    0.409795] EVM: security.ima
Sep 22 16:58:02 node-4 kernel: [    0.409796] EVM: security.capability
Sep 22 16:58:02 node-4 kernel: [    0.409846] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 22 16:58:02 node-4 kernel: [    0.410509] pinctrl core: initialized pinctrl subsystem
Sep 22 16:58:02 node-4 kernel: [    0.410572] regulator-dummy: no parameters
Sep 22 16:58:02 node-4 kernel: [    0.410605] RTC time: 16:57:24, date: 09/22/16
Sep 22 16:58:02 node-4 kernel: [    0.410640] NET: Registered protocol family 16
Sep 22 16:58:02 node-4 kernel: [    0.410725] cpuidle: using governor ladder
Sep 22 16:58:02 node-4 kernel: [    0.410726] cpuidle: using governor menu
Sep 22 16:58:02 node-4 kernel: [    0.410763] ACPI: bus type PCI registered
Sep 22 16:58:02 node-4 kernel: [    0.410764] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 22 16:58:02 node-4 kernel: [    0.410810] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 22 16:58:02 node-4 kernel: [    0.410812] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 22 16:58:02 node-4 kernel: [    0.424541] PCI: Using configuration type 1 for base access
Sep 22 16:58:02 node-4 kernel: [    0.425550] bio: create slab <bio-0> at 0
Sep 22 16:58:02 node-4 kernel: [    0.425826] ACPI: Added _OSI(Module Device)
Sep 22 16:58:02 node-4 kernel: [    0.425828] ACPI: Added _OSI(Processor Device)
Sep 22 16:58:02 node-4 kernel: [    0.425829] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 22 16:58:02 node-4 kernel: [    0.425830] ACPI: Added _OSI(Processor Aggregator Device)
Sep 22 16:58:02 node-4 kernel: [    0.438484] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 22 16:58:02 node-4 kernel: [    0.448985] ACPI: Interpreter enabled
Sep 22 16:58:02 node-4 kernel: [    0.448991] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 22 16:58:02 node-4 kernel: [    0.448995] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 22 16:58:02 node-4 kernel: [    0.448997] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 22 16:58:02 node-4 kernel: [    0.449004] ACPI: (supports S0 S4 S5)
Sep 22 16:58:02 node-4 kernel: [    0.449005] ACPI: Using IOAPIC for interrupt routing
Sep 22 16:58:02 node-4 kernel: [    0.449046] HEST: Table parsing has been initialized.
Sep 22 16:58:02 node-4 kernel: [    0.449048] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 22 16:58:02 node-4 kernel: [    0.449600] ACPI: No dock devices found.
Sep 22 16:58:02 node-4 kernel: [    0.461185] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 22 16:58:02 node-4 kernel: [    0.461190] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 22 16:58:02 node-4 kernel: [    0.461193] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 22 16:58:02 node-4 kernel: [    0.461220] PCI host bridge to bus 0000:ff
Sep 22 16:58:02 node-4 kernel: [    0.461222] pci_bus 0000:ff: root bus resource [bus ff]
Sep 22 16:58:02 node-4 kernel: [    0.461230] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461268] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 22 16:58:02 node-4 kernel: [    0.461298] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461333] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461363] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 22 16:58:02 node-4 kernel: [    0.461393] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 22 16:58:02 node-4 kernel: [    0.461424] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461453] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461484] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461513] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461539] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461566] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461594] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461621] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461648] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461675] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461703] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461733] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461760] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 22 16:58:02 node-4 kernel: [    0.461788] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461815] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 22 16:58:02 node-4 kernel: [    0.461840] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461867] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461897] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 22 16:58:02 node-4 kernel: [    0.461932] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461963] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.461993] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462027] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462060] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462093] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462123] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462154] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462184] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462217] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462249] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462282] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462315] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462346] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462373] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462406] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462439] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462475] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462510] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462543] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462572] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462601] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462631] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462662] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462693] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462724] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462756] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462786] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462816] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462846] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462876] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462909] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462941] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.462999] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 22 16:58:02 node-4 kernel: [    0.463002] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 22 16:58:02 node-4 kernel: [    0.463005] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 22 16:58:02 node-4 kernel: [    0.463023] PCI host bridge to bus 0000:7f
Sep 22 16:58:02 node-4 kernel: [    0.463025] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 22 16:58:02 node-4 kernel: [    0.463030] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463058] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 22 16:58:02 node-4 kernel: [    0.463087] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463117] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463139] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 22 16:58:02 node-4 kernel: [    0.463164] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 22 16:58:02 node-4 kernel: [    0.463191] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463218] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463243] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463265] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463294] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463319] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463346] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463371] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463397] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463424] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463446] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463469] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463493] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 22 16:58:02 node-4 kernel: [    0.463516] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463539] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 22 16:58:02 node-4 kernel: [    0.463561] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463584] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463611] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 22 16:58:02 node-4 kernel: [    0.463645] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463671] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463698] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463726] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463752] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463780] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463806] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463834] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463859] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463886] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463914] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463943] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463972] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.463997] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464022] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464051] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464076] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464103] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464134] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464161] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464188] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464214] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464240] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464267] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464295] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464324] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464355] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464381] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464404] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464431] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464457] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464488] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.464515] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.465771] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 22 16:58:02 node-4 kernel: [    0.465774] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 22 16:58:02 node-4 kernel: [    0.466891] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 22 16:58:02 node-4 kernel: [    0.467404] PCI host bridge to bus 0000:00
Sep 22 16:58:02 node-4 kernel: [    0.467407] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 22 16:58:02 node-4 kernel: [    0.467409] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 22 16:58:02 node-4 kernel: [    0.467410] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 22 16:58:02 node-4 kernel: [    0.467411] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 22 16:58:02 node-4 kernel: [    0.467413] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 22 16:58:02 node-4 kernel: [    0.467414] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 22 16:58:02 node-4 kernel: [    0.467415] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 22 16:58:02 node-4 kernel: [    0.467421] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 22 16:58:02 node-4 kernel: [    0.467504] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 22 16:58:02 node-4 kernel: [    0.467535] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 22 16:58:02 node-4 kernel: [    0.467576] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 22 16:58:02 node-4 kernel: [    0.467595] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 22 16:58:02 node-4 kernel: [    0.467624] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 22 16:58:02 node-4 kernel: [    0.467665] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 22 16:58:02 node-4 kernel: [    0.467683] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 22 16:58:02 node-4 kernel: [    0.467713] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 22 16:58:02 node-4 kernel: [    0.467755] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 22 16:58:02 node-4 kernel: [    0.467773] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.467844] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.467921] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.467998] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 22 16:58:02 node-4 kernel: [    0.468003] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 22 16:58:02 node-4 kernel: [    0.468088] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 22 16:58:02 node-4 kernel: [    0.468237] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 22 16:58:02 node-4 kernel: [    0.468255] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 22 16:58:02 node-4 kernel: [    0.468333] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 22 16:58:02 node-4 kernel: [    0.468387] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 22 16:58:02 node-4 kernel: [    0.468409] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 22 16:58:02 node-4 kernel: [    0.468465] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 22 16:58:02 node-4 kernel: [    0.468508] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 22 16:58:02 node-4 kernel: [    0.468536] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 22 16:58:02 node-4 kernel: [    0.468593] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 22 16:58:02 node-4 kernel: [    0.468636] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 22 16:58:02 node-4 kernel: [    0.468661] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 22 16:58:02 node-4 kernel: [    0.468678] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 22 16:58:02 node-4 kernel: [    0.468756] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 22 16:58:02 node-4 kernel: [    0.468806] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 22 16:58:02 node-4 kernel: [    0.468833] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 22 16:58:02 node-4 kernel: [    0.469083] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 22 16:58:02 node-4 kernel: [    0.469088] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 22 16:58:02 node-4 kernel: [    0.469095] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 22 16:58:02 node-4 kernel: [    0.469100] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 22 16:58:02 node-4 kernel: [    0.469108] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 22 16:58:02 node-4 kernel: [    0.469138] pci 0000:01:00.0: supports D1 D2
Sep 22 16:58:02 node-4 kernel: [    0.479284] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 22 16:58:02 node-4 kernel: [    0.479291] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 22 16:58:02 node-4 kernel: [    0.479295] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 22 16:58:02 node-4 kernel: [    0.479559] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 22 16:58:02 node-4 kernel: [    0.479619] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 22 16:58:02 node-4 kernel: [    0.487283] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 22 16:58:02 node-4 kernel: [    0.487290] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 22 16:58:02 node-4 kernel: [    0.487294] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 22 16:58:02 node-4 kernel: [    0.487378] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 22 16:58:02 node-4 kernel: [    0.487460] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 22 16:58:02 node-4 kernel: [    0.487536] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 22 16:58:02 node-4 kernel: [    0.487581] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 22 16:58:02 node-4 kernel: [    0.487585] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 22 16:58:02 node-4 kernel: [    0.487587] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 22 16:58:02 node-4 kernel: [    0.487639] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 22 16:58:02 node-4 kernel: [    0.487782] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 22 16:58:02 node-4 kernel: [    0.487836] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 22 16:58:02 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 22 16:58:02 node-4 kernel: [    0.487838] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 22 16:58:02 node-4 kernel: [    0.487840] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 22 16:58:02 node-4 kernel: [    0.487890] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 22 16:58:02 node-4 kernel: [    0.488009] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 22 16:58:02 node-4 kernel: [    0.488047] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 22 16:58:02 node-4 kernel: [    0.488170] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 22 16:58:02 node-4 kernel: [    0.488208] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 22 16:58:02 node-4 kernel: [    0.488328] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 22 16:58:02 node-4 kernel: [    0.488366] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 22 16:58:02 node-4 kernel: [    0.488485] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 22 16:58:02 node-4 kernel: [    0.488529] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 22 16:58:02 node-4 kernel: [    0.488531] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 22 16:58:02 node-4 kernel: [    0.488533] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 22 16:58:02 node-4 kernel: [    0.488592] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 22 16:58:02 node-4 kernel: [    0.488654] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 22 16:58:02 node-4 kernel: [    0.488731] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 22 16:58:02 node-4 kernel: [    0.488773] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 22 16:58:02 node-4 kernel: [    0.488852] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 22 16:58:02 node-4 kernel: [    0.488960] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 22 16:58:02 node-4 kernel: [    0.488962] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 22 16:58:02 node-4 kernel: [    0.488964] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 22 16:58:02 node-4 kernel: [    0.489020] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 22 16:58:02 node-4 kernel: [    0.489074] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 22 16:58:02 node-4 kernel: [    0.489126] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 22 16:58:02 node-4 kernel: [    0.489339] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 22 16:58:02 node-4 kernel: [    0.489343] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 22 16:58:02 node-4 kernel: [    0.489408] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 22 16:58:02 node-4 kernel: [    0.489460] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 22 16:58:02 node-4 kernel: [    0.489509] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 22 16:58:02 node-4 kernel: [    0.489738] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 22 16:58:02 node-4 kernel: [    0.489742] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 22 16:58:02 node-4 kernel: [    0.489801] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 22 16:58:02 node-4 kernel: [    0.489865] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 22 16:58:02 node-4 kernel: [    0.489917] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 22 16:58:02 node-4 kernel: [    0.490140] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 22 16:58:02 node-4 kernel: [    0.490143] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 22 16:58:02 node-4 kernel: [    0.490321] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 22 16:58:02 node-4 kernel: [    0.490359] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 22 16:58:02 node-4 kernel: [    0.490435] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 22 16:58:02 node-4 kernel: [    0.490453] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 22 16:58:02 node-4 kernel: [    0.490467] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 22 16:58:02 node-4 kernel: [    0.490480] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 22 16:58:02 node-4 kernel: [    0.490530] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 22 16:58:02 node-4 kernel: [    0.495296] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 22 16:58:02 node-4 kernel: [    0.495305] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 22 16:58:02 node-4 kernel: [    0.495358] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 22 16:58:02 node-4 kernel: [    0.496115] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 22 16:58:02 node-4 kernel: [    0.496118] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 22 16:58:02 node-4 kernel: [    0.496242] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 22 16:58:02 node-4 kernel: [    0.496350] PCI host bridge to bus 0000:80
Sep 22 16:58:02 node-4 kernel: [    0.496352] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 22 16:58:02 node-4 kernel: [    0.496354] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 22 16:58:02 node-4 kernel: [    0.496355] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 22 16:58:02 node-4 kernel: [    0.496363] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.496428] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.496496] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 22 16:58:02 node-4 kernel: [    0.496560] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 22 16:58:02 node-4 kernel: [    0.496565] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 22 16:58:02 node-4 kernel: [    0.496638] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 22 16:58:02 node-4 kernel: [    0.496939] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 22 16:58:02 node-4 kernel: [    0.496971] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 22 16:58:02 node-4 kernel: [    0.497000] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 22 16:58:02 node-4 kernel: [    0.497030] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 22 16:58:02 node-4 kernel: [    0.497059] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 22 16:58:02 node-4 kernel: [    0.497089] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 22 16:58:02 node-4 kernel: [    0.497119] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 22 16:58:02 node-4 kernel: [    0.497149] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 22 16:58:02 node-4 kernel: [    0.497235] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 22 16:58:02 node-4 kernel: [    0.497239] ACPI: \_SB_.UNC1: notify handler is installed
Sep 22 16:58:02 node-4 kernel: [    0.497240] ACPI: \_SB_.UNC0: notify handler is installed
Sep 22 16:58:02 node-4 kernel: [    0.497256] ACPI: \_SB_.PCI0: notify handler is installed
Sep 22 16:58:02 node-4 kernel: [    0.497308] ACPI: \_SB_.PCI1: notify handler is installed
Sep 22 16:58:02 node-4 kernel: [    0.497388] Found 4 acpi root devices
Sep 22 16:58:02 node-4 kernel: [    0.497494] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 22 16:58:02 node-4 kernel: [    0.497496] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 22 16:58:02 node-4 kernel: [    0.497497] vgaarb: loaded
Sep 22 16:58:02 node-4 kernel: [    0.497499] vgaarb: bridge control possible 0000:0c:00.0
Sep 22 16:58:02 node-4 kernel: [    0.497616] SCSI subsystem initialized
Sep 22 16:58:02 node-4 kernel: [    0.497687] libata version 3.00 loaded.
Sep 22 16:58:02 node-4 kernel: [    0.497702] ACPI: bus type USB registered
Sep 22 16:58:02 node-4 kernel: [    0.497712] usbcore: registered new interface driver usbfs
Sep 22 16:58:02 node-4 kernel: [    0.497717] usbcore: registered new interface driver hub
Sep 22 16:58:02 node-4 kernel: [    0.497740] usbcore: registered new device driver usb
Sep 22 16:58:02 node-4 kernel: [    0.497922] PCI: Using ACPI for IRQ routing
Sep 22 16:58:02 node-4 kernel: [    0.501543] PCI: pci_cache_line_size set to 64 bytes
Sep 22 16:58:02 node-4 kernel: [    0.501755] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 22 16:58:02 node-4 kernel: [    0.501756] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 22 16:58:02 node-4 kernel: [    0.501756] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 22 16:58:02 node-4 kernel: [    0.501821] NetLabel: Initializing
Sep 22 16:58:02 node-4 kernel: [    0.501822] NetLabel:  domain hash size = 128
Sep 22 16:58:02 node-4 kernel: [    0.501823] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 22 16:58:02 node-4 kernel: [    0.501833] NetLabel:  unlabeled traffic allowed by default
Sep 22 16:58:02 node-4 kernel: [    0.501902] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 22 16:58:02 node-4 kernel: [    0.501907] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 22 16:58:02 node-4 kernel: [    0.503975] Switched to clocksource hpet
Sep 22 16:58:02 node-4 kernel: [    0.508456] AppArmor: AppArmor Filesystem Enabled
Sep 22 16:58:02 node-4 kernel: [    0.508496] pnp: PnP ACPI init
Sep 22 16:58:02 node-4 kernel: [    0.508508] ACPI: bus type PNP registered
Sep 22 16:58:02 node-4 kernel: [    0.508689] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 22 16:58:02 node-4 kernel: [    0.508700] pnp 00:01: [dma 4]
Sep 22 16:58:02 node-4 kernel: [    0.508719] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 22 16:58:02 node-4 kernel: [    0.508754] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 22 16:58:02 node-4 kernel: [    0.508778] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 22 16:58:02 node-4 kernel: [    0.508799] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 22 16:58:02 node-4 kernel: [    0.508848] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 22 16:58:02 node-4 kernel: [    0.508963] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 22 16:58:02 node-4 kernel: [    0.508965] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 22 16:58:02 node-4 kernel: [    0.508967] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 22 16:58:02 node-4 kernel: [    0.508968] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 22 16:58:02 node-4 kernel: [    0.508970] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 22 16:58:02 node-4 kernel: [    0.508971] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 22 16:58:02 node-4 kernel: [    0.508975] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 22 16:58:02 node-4 kernel: [    0.508976] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 22 16:58:02 node-4 kernel: [    0.508978] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 22 16:58:02 node-4 kernel: [    0.508980] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 22 16:58:02 node-4 kernel: [    0.508981] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 22 16:58:02 node-4 kernel: [    0.508983] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 22 16:58:02 node-4 kernel: [    0.508987] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 22 16:58:02 node-4 kernel: [    0.508990] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 22 16:58:02 node-4 kernel: [    0.509088] pnp 00:07: [dma 0 disabled]
Sep 22 16:58:02 node-4 kernel: [    0.509121] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 22 16:58:02 node-4 kernel: [    0.509202] pnp 00:08: [dma 0 disabled]
Sep 22 16:58:02 node-4 kernel: [    0.509238] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 22 16:58:02 node-4 kernel: [    0.509297] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 22 16:58:02 node-4 kernel: [    0.509743] pnp: PnP ACPI: found 10 devices
Sep 22 16:58:02 node-4 kernel: [    0.509745] ACPI: bus type PNP unregistered
Sep 22 16:58:02 node-4 kernel: [    0.515789] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 22 16:58:02 node-4 kernel: [    0.515793] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 22 16:58:02 node-4 kernel: [    0.515796] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 22 16:58:02 node-4 kernel: [    0.515801] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 22 16:58:02 node-4 kernel: [    0.515803] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 22 16:58:02 node-4 kernel: [    0.515818] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 22 16:58:02 node-4 kernel: [    0.515848] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 22 16:58:02 node-4 kernel: [    0.515862] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 22 16:58:02 node-4 kernel: [    0.515891] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 22 16:58:02 node-4 kernel: [    0.515906] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 22 16:58:02 node-4 kernel: [    0.515935] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 22 16:58:02 node-4 kernel: [    0.515954] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 22 16:58:02 node-4 kernel: [    0.515983] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 22 16:58:02 node-4 kernel: [    0.515985] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 22 16:58:02 node-4 kernel: [    0.516000] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 22 16:58:02 node-4 kernel: [    0.516029] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 22 16:58:02 node-4 kernel: [    0.516031] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 22 16:58:02 node-4 kernel: [    0.516045] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 22 16:58:02 node-4 kernel: [    0.516074] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 22 16:58:02 node-4 kernel: [    0.516076] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 22 16:58:02 node-4 kernel: [    0.516079] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 22 16:58:02 node-4 kernel: [    0.516084] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 22 16:58:02 node-4 kernel: [    0.516085] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 22 16:58:02 node-4 kernel: [    0.516088] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 22 16:58:02 node-4 kernel: [    0.516093] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 22 16:58:02 node-4 kernel: [    0.516099] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 22 16:58:02 node-4 kernel: [    0.516108] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 22 16:58:02 node-4 kernel: [    0.516111] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 22 16:58:02 node-4 kernel: [    0.516119] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 22 16:58:02 node-4 kernel: [    0.516120] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 22 16:58:02 node-4 kernel: [    0.516121] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 22 16:58:02 node-4 kernel: [    0.516122] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 22 16:58:02 node-4 kernel: [    0.516123] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 22 16:58:02 node-4 kernel: [    0.516124] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 22 16:58:02 node-4 kernel: [    0.516125] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 22 16:58:02 node-4 kernel: [    0.516125] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 22 16:58:02 node-4 kernel: [    0.516127] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 22 16:58:02 node-4 kernel: [    0.516128] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 22 16:58:02 node-4 kernel: [    0.516129] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 22 16:58:02 node-4 kernel: [    0.516129] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 22 16:58:02 node-4 kernel: [    0.516130] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 22 16:58:02 node-4 kernel: [    0.516131] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 22 16:58:02 node-4 kernel: [    0.516132] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 22 16:58:02 node-4 kernel: [    0.516133] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 22 16:58:02 node-4 kernel: [    0.516134] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 22 16:58:02 node-4 kernel: [    0.516135] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 22 16:58:02 node-4 kernel: [    0.516136] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 22 16:58:02 node-4 kernel: [    0.516138] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 22 16:58:02 node-4 kernel: [    0.516139] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 22 16:58:02 node-4 kernel: [    0.516140] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 22 16:58:02 node-4 kernel: [    0.516142] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 22 16:58:02 node-4 kernel: [    0.516143] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 22 16:58:02 node-4 kernel: [    0.516185] NET: Registered protocol family 2
Sep 22 16:58:02 node-4 kernel: [    0.516492] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 22 16:58:02 node-4 kernel: [    0.516862] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 22 16:58:02 node-4 kernel: [    0.517030] TCP: Hash tables configured (established 262144 bind 65536)
Sep 22 16:58:02 node-4 kernel: [    0.517076] TCP: reno registered
Sep 22 16:58:02 node-4 kernel: [    0.517107] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 22 16:58:02 node-4 kernel: [    0.517213] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 22 16:58:02 node-4 kernel: [    0.517388] NET: Registered protocol family 1
Sep 22 16:58:02 node-4 kernel: [    0.556052] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 22 16:58:02 node-4 kernel: [    0.556060] PCI: CLS 64 bytes, default 64
Sep 22 16:58:02 node-4 kernel: [    0.556099] Trying to unpack rootfs image as initramfs...
Sep 22 16:58:02 node-4 kernel: [    0.779022] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Sep 22 16:58:02 node-4 kernel: [    0.779069] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 22 16:58:02 node-4 kernel: [    0.779072] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 22 16:58:02 node-4 kernel: [    0.779482] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 22 16:58:02 node-4 kernel: [    0.779490] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 22 16:58:02 node-4 kernel: [    0.779498] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 22 16:58:02 node-4 kernel: [    0.779505] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 22 16:58:02 node-4 kernel: [    0.779513] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 22 16:58:02 node-4 kernel: [    0.779521] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 22 16:58:02 node-4 kernel: [    0.779528] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 22 16:58:02 node-4 kernel: [    0.779535] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 22 16:58:02 node-4 kernel: [    0.779542] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 22 16:58:02 node-4 kernel: [    0.779548] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 22 16:58:02 node-4 kernel: [    0.779558] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 22 16:58:02 node-4 kernel: [    0.779564] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 22 16:58:02 node-4 kernel: [    0.779571] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 22 16:58:02 node-4 kernel: [    0.779576] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 22 16:58:02 node-4 kernel: [    0.779581] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 22 16:58:02 node-4 kernel: [    0.779586] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 22 16:58:02 node-4 kernel: [    0.779633] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 22 16:58:02 node-4 kernel: [    0.779636] Scanning for low memory corruption every 60 seconds
Sep 22 16:58:02 node-4 kernel: [    0.779996] Initialise system trusted keyring
Sep 22 16:58:02 node-4 kernel: [    0.780045] audit: initializing netlink socket (disabled)
Sep 22 16:58:02 node-4 kernel: [    0.780060] type=2000 audit(1474563443.736:1): initialized
Sep 22 16:58:02 node-4 kernel: [    0.797828] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 22 16:58:02 node-4 kernel: [    0.799274] zbud: loaded
Sep 22 16:58:02 node-4 kernel: [    0.799392] VFS: Disk quotas dquot_6.5.2
Sep 22 16:58:02 node-4 kernel: [    0.799426] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 22 16:58:02 node-4 kernel: [    0.799818] fuse init (API version 7.22)
Sep 22 16:58:02 node-4 kernel: [    0.799870] msgmni has been set to 32768
Sep 22 16:58:02 node-4 kernel: [    0.799921] Key type big_key registered
Sep 22 16:58:02 node-4 kernel: [    0.800376] Key type asymmetric registered
Sep 22 16:58:02 node-4 kernel: [    0.800377] Asymmetric key parser 'x509' registered
Sep 22 16:58:02 node-4 kernel: [    0.800398] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 22 16:58:02 node-4 kernel: [    0.800464] io scheduler noop registered
Sep 22 16:58:02 node-4 kernel: [    0.800465] io scheduler deadline registered (default)
Sep 22 16:58:02 node-4 kernel: [    0.800483] io scheduler cfq registered
Sep 22 16:58:02 node-4 kernel: [    0.800964] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    0.801150] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    0.801264] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    0.801387] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    0.801505] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    0.801599] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    0.802014] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 22 16:58:02 node-4 kernel: [    0.802040] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 22 16:58:02 node-4 kernel: [    0.802057] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 22 16:58:02 node-4 kernel: [    0.802069] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802071] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802074] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 22 16:58:02 node-4 kernel: [    0.802079] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802081] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802082] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802083] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802085] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802087] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802088] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802090] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802091] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802093] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802094] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802096] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802098] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 22 16:58:02 node-4 kernel: [    0.802103] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802106] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 22 16:58:02 node-4 kernel: [    0.802117] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802121] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 22 16:58:02 node-4 kernel: [    0.802132] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802134] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 22 16:58:02 node-4 kernel: [    0.802137] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 22 16:58:02 node-4 kernel: [    0.802164] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 22 16:58:02 node-4 kernel: [    0.802170] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 22 16:58:02 node-4 kernel: [    0.802173] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 22 16:58:02 node-4 kernel: [    0.802188] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 22 16:58:02 node-4 kernel: [    0.802225] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 22 16:58:02 node-4 kernel: [    0.802226] vesafb: scrolling: redraw
Sep 22 16:58:02 node-4 kernel: [    0.802228] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 22 16:58:02 node-4 kernel: [    0.822550] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 22 16:58:02 node-4 kernel: [    0.831052] Console: switching to colour frame buffer device 80x30
Sep 22 16:58:02 node-4 kernel: [    0.839719] fb0: VESA VGA frame buffer device
Sep 22 16:58:02 node-4 kernel: [    0.839910] intel_idle: MWAIT substates: 0x2120
Sep 22 16:58:02 node-4 kernel: [    0.839911] intel_idle: v0.4 model 0x3F
Sep 22 16:58:02 node-4 kernel: [    0.839912] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 22 16:58:02 node-4 kernel: [    0.840145] ipmi message handler version 39.2
Sep 22 16:58:02 node-4 kernel: [    0.840427] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 22 16:58:02 node-4 kernel: [    0.840859] ACPI: AC Adapter [P111] (on-line)
Sep 22 16:58:02 node-4 kernel: [    0.846082] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 22 16:58:02 node-4 kernel: [    0.857071] ACPI: Power Button [PWRB]
Sep 22 16:58:02 node-4 kernel: [    0.862828] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 22 16:58:02 node-4 kernel: [    0.874453] ACPI: Power Button [PWRF]
Sep 22 16:58:02 node-4 kernel: [    0.889535] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 22 16:58:02 node-4 kernel: [    0.901191] pstore: Registered erst as persistent store backend
Sep 22 16:58:02 node-4 kernel: [    0.907401] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 22 16:58:02 node-4 kernel: [    0.919487] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 22 16:58:02 node-4 kernel: [    0.946220] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 22 16:58:02 node-4 kernel: [    0.979489] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 22 16:58:02 node-4 kernel: [    0.993582] Linux agpgart interface v0.103
Sep 22 16:58:02 node-4 kernel: [    1.001211] brd: module loaded
Sep 22 16:58:02 node-4 kernel: [    1.008395] loop: module loaded
Sep 22 16:58:02 node-4 kernel: [    1.015160] libphy: Fixed MDIO Bus: probed
Sep 22 16:58:02 node-4 kernel: [    1.021650] tun: Universal TUN/TAP device driver, 1.6
Sep 22 16:58:02 node-4 kernel: [    1.028153] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 22 16:58:02 node-4 kernel: [    1.034789] PPP generic driver version 2.4.2
Sep 22 16:58:02 node-4 kernel: [    1.041198] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 22 16:58:02 node-4 kernel: [    1.047682] ehci-pci: EHCI PCI platform driver
Sep 22 16:58:02 node-4 kernel: [    1.054259] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 22 16:58:02 node-4 kernel: [    1.060765] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 22 16:58:02 node-4 kernel: [    1.073458] ehci-pci 0000:00:1a.0: debug port 2
Sep 22 16:58:02 node-4 kernel: [    1.083730] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 22 16:58:02 node-4 kernel: [    1.083749] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 22 16:58:02 node-4 kernel: [    1.099463] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 22 16:58:02 node-4 kernel: [    1.105537] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 22 16:58:02 node-4 kernel: [    1.111713] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 22 16:58:02 node-4 kernel: [    1.123672] usb usb1: Product: EHCI Host Controller
Sep 22 16:58:02 node-4 kernel: [    1.129738] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 22 16:58:02 node-4 kernel: [    1.135787] usb usb1: SerialNumber: 0000:00:1a.0
Sep 22 16:58:02 node-4 kernel: [    1.141738] hub 1-0:1.0: USB hub found
Sep 22 16:58:02 node-4 kernel: [    1.147521] hub 1-0:1.0: 2 ports detected
Sep 22 16:58:02 node-4 kernel: [    1.153316] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 22 16:58:02 node-4 kernel: [    1.158912] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 22 16:58:02 node-4 kernel: [    1.169822] ehci-pci 0000:00:1d.0: debug port 2
Sep 22 16:58:02 node-4 kernel: [    1.179133] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 22 16:58:02 node-4 kernel: [    1.179136] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 22 16:58:02 node-4 kernel: [    1.195381] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 22 16:58:02 node-4 kernel: [    1.200606] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 22 16:58:02 node-4 kernel: [    1.205913] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 22 16:58:02 node-4 kernel: [    1.216477] usb usb2: Product: EHCI Host Controller
Sep 22 16:58:02 node-4 kernel: [    1.221948] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 22 16:58:02 node-4 kernel: [    1.227501] usb usb2: SerialNumber: 0000:00:1d.0
Sep 22 16:58:02 node-4 kernel: [    1.233039] hub 2-0:1.0: USB hub found
Sep 22 16:58:02 node-4 kernel: [    1.238395] hub 2-0:1.0: 2 ports detected
Sep 22 16:58:02 node-4 kernel: [    1.243708] ehci-platform: EHCI generic platform driver
Sep 22 16:58:02 node-4 kernel: [    1.248969] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 22 16:58:02 node-4 kernel: [    1.254303] ohci-pci: OHCI PCI platform driver
Sep 22 16:58:02 node-4 kernel: [    1.259610] ohci-platform: OHCI generic platform driver
Sep 22 16:58:02 node-4 kernel: [    1.264816] uhci_hcd: USB Universal Host Controller Interface driver
Sep 22 16:58:02 node-4 kernel: [    1.270161] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 22 16:58:02 node-4 kernel: [    1.463161] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 22 16:58:02 node-4 kernel: [    1.774945] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 22 16:58:02 node-4 kernel: [    1.791210] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 22 16:58:02 node-4 kernel: [    1.796824] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 22 16:58:02 node-4 kernel: [    1.802475] hub 1-1:1.0: USB hub found
Sep 22 16:58:02 node-4 kernel: [    1.808069] hub 1-1:1.0: 6 ports detected
Sep 22 16:58:02 node-4 kernel: [    1.922793] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 22 16:58:02 node-4 kernel: [    2.309138] i8042: No controller found
Sep 22 16:58:02 node-4 kernel: [    2.314650] mousedev: PS/2 mouse device common for all mice
Sep 22 16:58:02 node-4 kernel: [    2.320361] rtc_cmos 00:02: RTC can wake from S4
Sep 22 16:58:02 node-4 kernel: [    2.323202] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 22 16:58:02 node-4 kernel: [    2.323203] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 22 16:58:02 node-4 kernel: [    2.323854] hub 2-1:1.0: USB hub found
Sep 22 16:58:02 node-4 kernel: [    2.324063] hub 2-1:1.0: 8 ports detected
Sep 22 16:58:02 node-4 kernel: [    2.348657] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 22 16:58:02 node-4 kernel: [    2.354427] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 22 16:58:02 node-4 kernel: [    2.365750] device-mapper: uevent: version 1.0.3
Sep 22 16:58:02 node-4 kernel: [    2.371452] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 22 16:58:02 node-4 kernel: [    2.382820] ledtrig-cpu: registered to indicate activity on CPUs
Sep 22 16:58:02 node-4 kernel: [    2.388788] TCP: cubic registered
Sep 22 16:58:02 node-4 kernel: [    2.394648] NET: Registered protocol family 10
Sep 22 16:58:02 node-4 kernel: [    2.400696] NET: Registered protocol family 17
Sep 22 16:58:02 node-4 kernel: [    2.406473] Key type dns_resolver registered
Sep 22 16:58:02 node-4 kernel: [    2.412507] Loading compiled-in X.509 certificates
Sep 22 16:58:02 node-4 kernel: [    2.418727] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 22 16:58:02 node-4 kernel: [    2.430341] registered taskstats version 1
Sep 22 16:58:02 node-4 kernel: [    2.438404] Key type trusted registered
Sep 22 16:58:02 node-4 kernel: [    2.446043] Key type encrypted registered
Sep 22 16:58:02 node-4 kernel: [    2.451530] AppArmor: AppArmor sha1 policy hashing enabled
Sep 22 16:58:02 node-4 kernel: [    2.457038] IMA: No TPM chip found, activating TPM-bypass!
Sep 22 16:58:02 node-4 kernel: [    2.463110] regulator-dummy: disabling
Sep 22 16:58:02 node-4 kernel: [    2.468604]   Magic number: 0:811:995
Sep 22 16:58:02 node-4 kernel: [    2.474062] machinecheck machinecheck8: hash matches
Sep 22 16:58:02 node-4 kernel: [    2.479739] memory memory38: hash matches
Sep 22 16:58:02 node-4 kernel: [    2.485163] rtc_cmos 00:02: setting system clock to 2016-09-22 16:57:26 UTC (1474563446)
Sep 22 16:58:02 node-4 kernel: [    2.497534] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 22 16:58:02 node-4 kernel: [    2.503101] EDD information not available.
Sep 22 16:58:02 node-4 kernel: [    2.508665] PM: Hibernation image not present or could not be loaded.
Sep 22 16:58:02 node-4 kernel: [    2.509534] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 22 16:58:02 node-4 kernel: [    2.520858] Write protecting the kernel read-only data: 12288k
Sep 22 16:58:02 node-4 kernel: [    2.527182] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 22 16:58:02 node-4 kernel: [    2.539920] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 22 16:58:02 node-4 kernel: [    2.571607] device-mapper: multipath: version 1.6.0 loaded
Sep 22 16:58:02 node-4 kernel: [    2.579382] systemd-udevd[217]: starting version 204
Sep 22 16:58:02 node-4 kernel: [    2.598217] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 22 16:58:02 node-4 kernel: [    2.606144] md: linear personality registered for level -1
Sep 22 16:58:02 node-4 kernel: [    2.621242] md: multipath personality registered for level -4
Sep 22 16:58:02 node-4 kernel: [    2.629312] md: raid0 personality registered for level 0
Sep 22 16:58:02 node-4 kernel: [    2.637544] md: raid1 personality registered for level 1
Sep 22 16:58:02 node-4 kernel: [    2.648008] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 22 16:58:02 node-4 kernel: [    2.654248] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 22 16:58:02 node-4 kernel: [    2.654627] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 22 16:58:02 node-4 kernel: [    2.666940] megasas: FW now in Ready state
Sep 22 16:58:02 node-4 kernel: [    2.667302] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Sep 22 16:58:02 node-4 kernel: [    2.667325] 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 22 16:58:02 node-4 kernel: [    2.667345] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 22 16:58:02 node-4 kernel: [    2.667982] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.668095] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.668176] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.668285] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.668529] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.686216] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Sep 22 16:58:02 node-4 kernel: [    2.686228] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Sep 22 16:58:02 node-4 kernel: [    2.686229] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 22 16:58:02 node-4 kernel: [    2.686484] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.686635] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.686746] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.686854] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.686978] enic 0000:07:00.0: irq 104 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.687108] enic 0000:07:00.0: irq 105 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.687384] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.704649] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Sep 22 16:58:02 node-4 kernel: [    2.704655] 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 22 16:58:02 node-4 kernel: [    2.704673] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 22 16:58:02 node-4 kernel: [    2.704942] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.705071] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.705165] enic 0000:08:00.0: irq 108 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.705271] enic 0000:08:00.0: irq 109 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.705461] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.710188] raid6: sse2x1   11088 MB/s
Sep 22 16:58:02 node-4 kernel: [    2.722189] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Sep 22 16:58:02 node-4 kernel: [    2.722193] 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 22 16:58:02 node-4 kernel: [    2.722194] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 22 16:58:02 node-4 kernel: [    2.722420] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.722548] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.722657] enic 0000:09:00.0: irq 112 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.722773] enic 0000:09:00.0: irq 113 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.722998] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 22 16:58:02 node-4 kernel: [    2.738256] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 22 16:58:02 node-4 kernel: [    2.738259] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 22 16:58:02 node-4 kernel: [    2.738275] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 22 16:58:02 node-4 kernel: [    2.738276] usb 2-1.4: Manufacturer: Avocent
Sep 22 16:58:02 node-4 kernel: [    2.738277] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 22 16:58:02 node-4 kernel: [    2.778243] raid6: sse2x2   14186 MB/s
Sep 22 16:58:02 node-4 kernel: [    2.846278] raid6: sse2x4    9536 MB/s
Sep 22 16:58:02 node-4 kernel: [    2.914113] raid6: avx2x1   14034 MB/s
Sep 22 16:58:02 node-4 kernel: [    2.981880] raid6: avx2x2   18632 MB/s
Sep 22 16:58:02 node-4 kernel: [    3.053816] raid6: avx2x4   21321 MB/s
Sep 22 16:58:02 node-4 kernel: [    3.059469] raid6: using algorithm avx2x4 (21321 MB/s)
Sep 22 16:58:02 node-4 kernel: [    3.065064] raid6: using avx2x2 recovery algorithm
Sep 22 16:58:02 node-4 kernel: [    3.070733] Switched to clocksource tsc
Sep 22 16:58:02 node-4 kernel: [    3.071269] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    3.071408] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    3.071510] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    3.071544] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    3.071650] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    3.071760] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    3.071887] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    3.072030] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    3.072117] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    3.072221] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    3.072371] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    3.072484] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    3.072601] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    3.072707] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    3.072967] megaraid_sas 0000:01:00.0: irq 128 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    3.073138] megaraid_sas 0000:01:00.0: irq 129 for MSI/MSI-X
Sep 22 16:58:02 node-4 kernel: [    3.073828] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 22 16:58:02 node-4 kernel: [    3.088159] xor: automatically using best checksumming function:
Sep 22 16:58:02 node-4 kernel: [    3.103731] hidraw: raw HID events driver (C) Jiri Kosina
Sep 22 16:58:02 node-4 kernel: [    3.112002] usbcore: registered new interface driver usbhid
Sep 22 16:58:02 node-4 kernel: [    3.117432] usbhid: USB HID core driver
Sep 22 16:58:02 node-4 kernel: [    3.123843] 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 22 16:58:02 node-4 kernel: [    3.129729]    avx       : 36575.000 MB/sec
Sep 22 16:58:02 node-4 kernel: [    3.140762] 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 22 16:58:02 node-4 kernel: [    3.152134] async_tx: api initialized (async)
Sep 22 16:58:02 node-4 kernel: [    3.152169] 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 22 16:58:02 node-4 kernel: [    3.152697] 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 22 16:58:02 node-4 kernel: [    3.152838] 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 22 16:58:02 node-4 kernel: [    3.153321] 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 22 16:58:02 node-4 kernel: [    3.209291] md: raid6 personality registered for level 6
Sep 22 16:58:02 node-4 kernel: [    3.215666] md: raid5 personality registered for level 5
Sep 22 16:58:02 node-4 kernel: [    3.221911] md: raid4 personality registered for level 4
Sep 22 16:58:02 node-4 kernel: [    3.231065] md: raid10 personality registered for level 10
Sep 22 16:58:02 node-4 kernel: [    3.285987] multipathd (354): /proc/354/oom_adj is deprecated, please use /proc/354/oom_score_adj instead.
Sep 22 16:58:02 node-4 kernel: [    3.465466] megasas:IOC Init cmd success
Sep 22 16:58:02 node-4 kernel: [    3.493450] megasas: INIT adapter done
Sep 22 16:58:02 node-4 kernel: [    3.617342] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 22 16:58:02 node-4 kernel: [    3.624321] scsi0 : LSI SAS based MegaRAID driver
Sep 22 16:58:02 node-4 kernel: [    3.631655] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 22 16:58:02 node-4 kernel: [    3.650051] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 22 16:58:02 node-4 kernel: [    3.665693] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 22 16:58:02 node-4 kernel: [    3.672256] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 22 16:58:02 node-4 kernel: [    3.685401] sd 0:2:0:0: [sda] Write Protect is off
Sep 22 16:58:02 node-4 kernel: [    3.691773] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 22 16:58:02 node-4 kernel: [    3.691793] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 22 16:58:02 node-4 kernel: [    3.732192]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Sep 22 16:58:02 node-4 kernel: [    3.738918] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 22 16:58:02 node-4 kernel: [    3.871228] random: lvm urandom read with 27 bits of entropy available
Sep 22 16:58:02 node-4 kernel: [    4.046722] bio: create slab <bio-1> at 1
Sep 22 16:58:02 node-4 kernel: [    4.918252] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Sep 22 16:58:02 node-4 kernel: [    5.381710] random: nonblocking pool is initialized
Sep 22 16:58:02 node-4 kernel: [    5.555547] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Sep 22 16:58:02 node-4 kernel: [    5.604010] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 22 16:58:02 node-4 kernel: [    5.743291] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 22 16:58:02 node-4 kernel: [    5.785171] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 22 16:58:02 node-4 kernel: [    5.932780] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 22 16:58:02 node-4 kernel: [    6.140727] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 22 16:58:02 node-4 kernel: [    6.188709] XFS (dm-1): Mounting Filesystem
Sep 22 16:58:02 node-4 kernel: [    6.395044] XFS (dm-1): Ending clean mount
Sep 22 16:58:02 node-4 kernel: [    6.483703] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 22 16:58:02 node-4 kernel: [    6.528147] XFS (dm-2): Mounting Filesystem
Sep 22 16:58:02 node-4 kernel: [    6.635524] XFS (dm-2): Ending clean mount
Sep 22 16:58:02 node-4 kernel: [    6.744259] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Sep 22 16:58:02 node-4 kernel: [    8.499840] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 22 16:58:02 node-4 kernel: [    8.524950] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 22 16:58:02 node-4 kernel: [    8.664982] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 22 16:58:02 node-4 kernel: [    8.664987] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 22 16:58:02 node-4 kernel: [    8.664991] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 22 16:58:02 node-4 kernel: [    8.664995] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 22 16:58:02 node-4 kernel: [    8.723841] systemd-udevd[802]: starting version 204
Sep 22 16:58:02 node-4 kernel: [    8.934547] power_meter ACPI000D:00: Found ACPI power meter.
Sep 22 16:58:02 node-4 kernel: [    8.934567] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 22 16:58:02 node-4 kernel: [    8.957204] wmi: Mapper loaded
Sep 22 16:58:02 node-4 kernel: [    8.964812] IPMI System Interface driver.
Sep 22 16:58:02 node-4 kernel: [    8.964887] ipmi_si: probing via ACPI
Sep 22 16:58:02 node-4 kernel: [    8.964900] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 22 16:58:02 node-4 kernel: [    8.964901] ipmi_si: Adding ACPI-specified kcs state machine
Sep 22 16:58:02 node-4 kernel: [    8.964917] ipmi_si: probing via SMBIOS
Sep 22 16:58:02 node-4 kernel: [    8.964919] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 22 16:58:02 node-4 kernel: [    8.964920] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 22 16:58:02 node-4 kernel: [    8.964922] ipmi_si: probing via SPMI
Sep 22 16:58:02 node-4 kernel: [    8.964923] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 22 16:58:02 node-4 kernel: [    8.964924] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 22 16:58:02 node-4 kernel: [    8.964926] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 22 16:58:02 node-4 kernel: [    8.989838] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 22 16:58:02 node-4 kernel: [    8.989843] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 22 16:58:02 node-4 kernel: [    8.989846] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 22 16:58:02 node-4 kernel: [    8.989847] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 22 16:58:02 node-4 kernel: [    8.989859] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 22 16:58:02 node-4 kernel: [    8.994375] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 22 16:58:02 node-4 kernel: [    9.057199] systemd-udevd[820]: renamed network interface eth0 to enp6s0
Sep 22 16:58:02 node-4 kernel: [    9.077074] systemd-udevd[823]: renamed network interface eth1 to enp7s0
Sep 22 16:58:02 node-4 kernel: [    9.111971] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 22 16:58:02 node-4 kernel: [    9.111977] ipmi_si 00:09: IPMI kcs interface initialized
Sep 22 16:58:02 node-4 kernel: [    9.121090] systemd-udevd[821]: renamed network interface eth2 to enp8s0
Sep 22 16:58:02 node-4 kernel: [    9.157044] systemd-udevd[825]: renamed network interface eth3 to enp9s0
Sep 22 16:58:02 node-4 kernel: [    9.467726] type=1400 audit(1474563453.482:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1084 comm="apparmor_parser"
Sep 22 16:58:02 node-4 kernel: [    9.467883] type=1400 audit(1474563453.482:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1084 comm="apparmor_parser"
Sep 22 16:58:02 node-4 kernel: [    9.468012] type=1400 audit(1474563453.482:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1084 comm="apparmor_parser"
Sep 22 16:58:02 node-4 kernel: [    9.478190] type=1400 audit(1474563453.494:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1088 comm="apparmor_parser"
Sep 22 16:58:02 node-4 kernel: [    9.478337] type=1400 audit(1474563453.494:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1088 comm="apparmor_parser"
Sep 22 16:58:02 node-4 kernel: [    9.478459] type=1400 audit(1474563453.494:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1088 comm="apparmor_parser"
Sep 22 16:58:02 node-4 kernel: [    9.486640] type=1400 audit(1474563453.502:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1089 comm="apparmor_parser"
Sep 22 16:58:02 node-4 kernel: [    9.486785] type=1400 audit(1474563453.502:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1089 comm="apparmor_parser"
Sep 22 16:58:02 node-4 kernel: [    9.486911] type=1400 audit(1474563453.502:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1089 comm="apparmor_parser"
Sep 22 16:58:02 node-4 kernel: [    9.488137] type=1400 audit(1474563453.502:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1090 comm="apparmor_parser"
Sep 22 16:58:02 node-4 kernel: [   10.066899] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 22 16:58:02 node-4 kernel: [   10.068175] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 22 16:58:02 node-4 kernel: [   10.122898] init: ureadahead-other main process (1213) terminated with status 2
Sep 22 16:58:02 node-4 kernel: [   10.311146] enic 0000:06:00.0 enp6s0: Link UP
Sep 22 16:58:02 node-4 kernel: [   10.314165] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 22 16:58:02 node-4 kernel: [   10.314171] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 22 16:58:02 node-4 kernel: [   21.016722] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 22 16:58:02 node-4 failsafe: Failsafe of 120 seconds reached.
Sep 22 16:58:03 node-4 kernel: [   39.792769] init: failsafe main process (8449) killed by TERM signal
Sep 22 16:58:03 node-4 dbus[8497]: [system] AppArmor D-Bus mediation is enabled
Sep 22 16:58:03 node-4 kernel: [   40.000704] audit_printk_skb: 30 callbacks suppressed
Sep 22 16:58:03 node-4 kernel: [   40.000706] type=1400 audit(1474563483.309:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8575 comm="apparmor_parser"
Sep 22 16:58:03 node-4 kernel: [   40.000979] type=1400 audit(1474563483.309:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8574 comm="apparmor_parser"
Sep 22 16:58:03 node-4 kernel: [   40.000983] type=1400 audit(1474563483.309:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8574 comm="apparmor_parser"
Sep 22 16:58:03 node-4 kernel: [   40.000985] type=1400 audit(1474563483.309:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8574 comm="apparmor_parser"
Sep 22 16:58:03 node-4 kernel: [   40.001217] type=1400 audit(1474563483.309:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8574 comm="apparmor_parser"
Sep 22 16:58:03 node-4 kernel: [   40.001219] type=1400 audit(1474563483.309:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8574 comm="apparmor_parser"
Sep 22 16:58:03 node-4 kernel: [   40.001332] type=1400 audit(1474563483.309:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8574 comm="apparmor_parser"
Sep 22 16:58:03 node-4 kernel: [   40.092299] type=1400 audit(1474563483.401:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8577 comm="apparmor_parser"
Sep 22 16:58:03 node-4 cron[8607]: (CRON) INFO (pidfile fd = 3)
Sep 22 16:58:03 node-4 anacron[8624]: Anacron 2.3 started on 2016-09-22
Sep 22 16:58:03 node-4 cron[8643]: (CRON) STARTUP (fork ok)
Sep 22 16:58:03 node-4 anacron[8624]: Will run job `cron.daily' in 5 min.
Sep 22 16:58:03 node-4 anacron[8624]: Will run job `cron.weekly' in 10 min.
Sep 22 16:58:03 node-4 anacron[8624]: Will run job `cron.monthly' in 15 min.
Sep 22 16:58:03 node-4 anacron[8624]: Jobs will be executed sequentially
Sep 22 16:58:03 node-4 cron[8643]: (CRON) INFO (Running @reboot jobs)
Sep 22 16:58:03 node-4 multipathd: path checkers start up
Sep 22 16:58:03 node-4 postfix/master[8786]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 22 16:58:07 node-4 puppet-agent[9099]: Reopening log files
Sep 22 16:58:10 node-4 puppet-agent[9099]: Could not request certificate: Connection refused - connect(2)
Sep 22 16:58:18 node-4 puppet-user[9178]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 22 16:58:18 node-4 puppet-user[9178]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Sep 22 16:58:18 node-4 puppet-user[9178]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 22 16:58:18 node-4 puppet-user[9178]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 22 16:58:18 node-4 puppet-user[9178]: Finished catalog run in 0.59 seconds
Sep 22 16:58:20 node-4 multipathd: uevent trigger error
Sep 22 16:58:20 node-4 puppet-user[9790]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 22 16:58:20 node-4 puppet-user[9790]: Compiled catalog for node-4.domain.tld in environment production in 0.08 seconds
Sep 22 16:58:20 node-4 puppet-user[9790]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 22 16:58:20 node-4 puppet-user[9790]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 22 16:58:20 node-4 puppet-user[9790]: (/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 22 16:58:20 node-4 puppet-user[9790]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 22 16:58:20 node-4 puppet-user[9790]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 22 16:58:20 node-4 puppet-user[9790]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 22 16:58:20 node-4 puppet-user[9790]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 22 16:58:20 node-4 puppet-user[9790]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 22 16:58:20 node-4 puppet-user[9790]: Finished catalog run in 0.07 seconds
Sep 22 16:58:21 node-4 puppet-user[10249]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 22 16:58:21 node-4 puppet-user[10249]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Sep 22 16:58:22 node-4 puppet-user[10249]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 22 16:58:22 node-4 puppet-user[10249]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 22 16:58:22 node-4 puppet-user[10249]: Finished catalog run in 0.03 seconds
Sep 22 16:58:23 node-4 puppet-user[10709]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 22 16:58:23 node-4 puppet-user[10709]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Sep 22 16:58:23 node-4 puppet-user[10709]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 22 16:58:23 node-4 puppet-user[10709]: Finished catalog run in 0.06 seconds
Sep 22 16:58:24 node-4 puppet-user[11158]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 22 16:58:25 node-4 puppet-user[11158]: Compiled catalog for node-4.domain.tld in environment production in 0.17 seconds
Sep 22 16:58:25 node-4 puppet-user[11158]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 22 16:58:25 node-4 puppet-user[11158]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Sep 22 16:58:25 node-4 puppet-user[11158]: Finished catalog run in 0.43 seconds
Sep 22 16:58:26 node-4 puppet-user[11629]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 22 16:58:26 node-4 puppet-user[11629]: Compiled catalog for node-4.domain.tld in environment production in 0.19 seconds
Sep 22 16:58:27 node-4 puppet-user[11629]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Sep 22 16:58:27 node-4 puppet-user[11629]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 22 16:58:27 node-4 puppet-user[11629]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 22 16:58:27 node-4 puppet-user[11629]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 22 16:58:27 node-4 puppet-user[11629]: Finished catalog run in 0.24 seconds
Sep 22 16:58:28 node-4 puppet-user[12104]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 22 16:58:28 node-4 puppet-user[12104]: Compiled catalog for node-4.domain.tld in environment production in 0.14 seconds
Sep 22 16:58:28 node-4 puppet-user[12104]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 22 16:58:28 node-4 kernel: [   65.284850] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 22 16:58:28 node-4 kernel: [   65.284898] 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 22 16:58:28 node-4 puppet-user[12104]: (/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 22 16:58:29 node-4 puppet-user[12104]: Finished catalog run in 0.05 seconds
Sep 22 16:58:30 node-4 kernel: [   67.057231] init: plymouth-upstart-bridge main process ended, respawning
Sep 22 16:58:30 node-4 puppet-agent[9099]: Could not run: SIGTERM
Sep 22 16:58:31 node-4 kernel: [   67.324600] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 22 16:58:31 node-4 ec2: 
Sep 22 16:58:31 node-4 ec2: #############################################################
Sep 22 16:58:31 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 22 16:58:31 node-4 ec2: 1024 6d:ec:e5:16:27:d1:31:28:e9:d2:4b:a2:2f:53:ab:5b  root@node-4.domain.tld (DSA)
Sep 22 16:58:31 node-4 ec2: 256 10:71:5b:f1:d5:67:36:10:c3:9d:f5:8e:38:6b:0d:98  root@node-4.domain.tld (ECDSA)
Sep 22 16:58:31 node-4 ec2: 256 b2:62:52:f3:30:aa:81:7a:22:ce:ad:7b:f0:c5:95:38  root@node-4.domain.tld (ED25519)
Sep 22 16:58:31 node-4 ec2: 2048 e7:63:f5:02:43:f3:ff:31:27:de:c0:46:02:c6:32:12  root@node-4.domain.tld (RSA)
Sep 22 16:58:31 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 22 16:58:31 node-4 ec2: #############################################################
Sep 22 16:58:31 node-4 puppet-user[12573]: (Scope(Class[main])) MODULAR: sync_time
Sep 22 16:58:31 node-4 puppet-user[12573]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Sep 22 16:58:31 node-4 ntpdate[13157]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 22 16:58:37 node-4 ntpdate[13157]: adjust time server 10.20.0.2 offset 0.000902 sec
Sep 22 16:58:37 node-4 puppet-user[12573]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 22 16:58:37 node-4 puppet-user[12573]: Finished catalog run in 6.18 seconds
Sep 22 16:58:44 node-4 puppet-user[13359]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 22 16:58:44 node-4 puppet-user[13359]: Compiled catalog for node-4.domain.tld in environment production in 0.08 seconds
Sep 22 16:58:44 node-4 puppet-user[13359]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 22 16:58:44 node-4 puppet-user[13359]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs"]'
Sep 22 16:58:44 node-4 puppet-user[13359]: Finished catalog run in 0.07 seconds
Sep 22 16:58:46 node-4 puppet-user[13819]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 22 16:58:46 node-4 puppet-user[13819]: Compiled catalog for node-4.domain.tld in environment production in 0.51 seconds
Sep 22 16:58:46 node-4 puppet-user[13819]: (/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 22 16:58:46 node-4 puppet-user[13819]: (/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 22 16:58:46 node-4 puppet-user[13819]: (/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 22 16:58:46 node-4 puppet-user[13819]: (/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 22 16:58:46 node-4 puppet-user[13819]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 22 16:58:46 node-4 puppet-user[13819]: (/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 22 16:58:46 node-4 puppet-user[13819]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 22 16:58:46 node-4 puppet-user[13819]: (/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 22 16:58:46 node-4 puppet-user[13819]: (/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 22 16:58:47 node-4 puppet-user[13819]: (/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 22 16:58:47 node-4 puppet-user[13819]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 22 16:58:47 node-4 puppet-user[13819]: Finished catalog run in 0.83 seconds
Sep 22 16:58:49 node-4 puppet-user[14331]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 22 16:58:49 node-4 puppet-user[14331]: Compiled catalog for node-4.domain.tld in environment production in 0.11 seconds
Sep 22 16:58:53 node-4 puppet-user[14331]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 22 16:59:02 node-4 CRON[16204]: (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 22 16:59:21 node-4 puppet-user[14331]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 22 16:59:21 node-4 puppet-user[14331]: Finished catalog run in 31.93 seconds
Sep 22 16:59:23 node-4 puppet-user[17213]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 22 16:59:23 node-4 puppet-user[17213]: Compiled catalog for node-4.domain.tld in environment production in 0.60 seconds
Sep 22 16:59:23 node-4 puppet-user[17213]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 22 16:59:24 node-4 puppet-user[17213]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 22 16:59:24 node-4 puppet-user[17213]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 22 16:59:24 node-4 puppet-user[17213]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 22 16:59:24 node-4 puppet-user[17213]: Finished catalog run in 0.10 seconds
Sep 22 16:59:25 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 22 16:59:25 node-4 nailgun-agent: I, [2016-09-22T16:59:25.155757 #16207]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 22 16:59:25 node-4 puppet-user[17677]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 22 16:59:26 node-4 puppet-user[17677]: Compiled catalog for node-4.domain.tld in environment production in 0.91 seconds
Sep 22 16:59:27 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 22 16:59:27 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 22 16:59:27 node-4 crontab[18262]: (root) LIST (root)
Sep 22 16:59:27 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 22 16:59:27 node-4 crontab[18263]: (root) REPLACE (root)
Sep 22 16:59:28 node-4 puppet-user[17677]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/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 22 16:59:29 node-4 puppet-user[17677]: (/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 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/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 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/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 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/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 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 22 16:59:29 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 22 16:59:30 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 22 16:59:30 node-4 puppet-user[17677]: (/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 22 16:59:30 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 22 16:59:30 node-4 puppet-user[17677]: (/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 22 16:59:30 node-4 puppet-user[17677]: (/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 22 16:59:30 node-4 puppet-user[17677]: (/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 22 16:59:30 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 22 16:59:30 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 22 16:59:30 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 22 16:59:30 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 22 16:59:30 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 22 16:59:30 node-4 puppet-user[17677]: (/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 22 16:59:30 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 22 16:59:30 node-4 puppet-user[17677]: (/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 22 16:59:30 node-4 puppet-user[17677]: (/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 22 16:59:30 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 22 16:59:30 node-4 puppet-user[17677]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 22 16:59:30 node-4 puppet-user[17677]: (/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 22 16:59:30 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8422" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 22 16:59:30 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 22 16:59:32 node-4 multipathd: uevent trigger error
<27>Sep 22 16:59:32 node-4 multipathd: uevent trigger error
<27>Sep 22 16:59:32 node-4 multipathd: uevent trigger error
<27>Sep 22 16:59:32 node-4 multipathd: uevent trigger error
<27>Sep 22 16:59:32 node-4 multipathd: uevent trigger error
<27>Sep 22 16:59:32 node-4 multipathd: uevent trigger error
<27>Sep 22 16:59:45 node-4 multipathd: uevent trigger error
<27>Sep 22 16:59:45 node-4 multipathd: uevent trigger error
<27>Sep 22 16:59:45 node-4 multipathd: uevent trigger error
<27>Sep 22 16:59:45 node-4 multipathd: uevent trigger error
<27>Sep 22 16:59:45 node-4 multipathd: uevent trigger error
<27>Sep 22 16:59:45 node-4 multipathd: uevent trigger error
<27>Sep 22 17:00:34 node-4 ntpdate[28537]: no servers can be used, exiting
<27>Sep 22 17:00:34 node-4 ntpdate[28670]: no servers can be used, exiting
<27>Sep 22 17:00:35 node-4 ntpdate[28897]: no servers can be used, exiting
<27>Sep 22 17:01:06 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:06 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:06 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:06 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:06 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:09 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:09 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:09 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:09 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:09 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:09 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:09 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:21 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:21 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:21 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:21 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:21 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:24 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:24 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:24 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:24 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:24 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:30 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:30 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:30 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:30 node-4 multipathd: uevent trigger error
<27>Sep 22 17:01:30 node-4 multipathd: uevent trigger error
<27>Sep 22 17:02:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:02:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:02:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:02:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:02:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:02:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:02:30 node-4 multipathd: uevent trigger error
<27>Sep 22 17:02:30 node-4 multipathd: uevent trigger error
<27>Sep 22 17:02:30 node-4 multipathd: uevent trigger error
<27>Sep 22 17:02:30 node-4 multipathd: uevent trigger error
<27>Sep 22 17:02:30 node-4 multipathd: uevent trigger error
<27>Sep 22 17:02:30 node-4 multipathd: uevent trigger error
<43>Sep 22 17:02:30 node-4 apache2_error [Thu Sep 22 17:02:21.961007 2016] [mpm_event:notice] [pid 9336:tid 139780409694080] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 22 17:02:30 node-4 apache2_error [Thu Sep 22 17:02:21.961153 2016] [core:notice] [pid 9336:tid 139780409694080] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 22 17:02:30 node-4 apache2_error [Thu Sep 22 17:02:25.090248 2016] [mpm_event:notice] [pid 9336:tid 139780409694080] AH00491: caught SIGTERM, shutting down
<43>Sep 22 17:02:30 node-4 apache2_error [Thu Sep 22 17:02:26.179424 2016] [mpm_worker:notice] [pid 9641:tid 139710317741952] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 22 17:02:30 node-4 apache2_error [Thu Sep 22 17:02:26.179498 2016] [core:notice] [pid 9641:tid 139710317741952] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 22 17:03:02 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Sep 22 17:03:06 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:06 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:06 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:06 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:06 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:16 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:16 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:16 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:16 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:16 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:24 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:24 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:24 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:24 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:24 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:24 node-4 multipathd: uevent trigger error
<129>Sep 22 17:03:27 node-4 haproxy[20526]: 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 22 17:03:29 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:29 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:29 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:29 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:29 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:29 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:32 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:32 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:32 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:32 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:32 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:32 node-4 multipathd: uevent trigger error
<129>Sep 22 17:03:36 node-4 haproxy[22964]: 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 22 17:03:37 node-4 haproxy[22964]: 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 22 17:03:38 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:38 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:38 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:38 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:38 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:38 node-4 multipathd: uevent trigger error
<129>Sep 22 17:03:41 node-4 haproxy[24164]: 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 22 17:03:41 node-4 haproxy[24164]: 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 22 17:03:42 node-4 haproxy[24164]: 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 22 17:03:43 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:43 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:43 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:43 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:43 node-4 multipathd: uevent trigger error
<129>Sep 22 17:03:46 node-4 haproxy[25390]: 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 22 17:03:46 node-4 haproxy[25390]: 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 22 17:03:47 node-4 haproxy[25394]: 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 22 17:03:47 node-4 haproxy[25394]: 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 22 17:03:48 node-4 haproxy[25394]: 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 22 17:03:49 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:49 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:49 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:49 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:49 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:49 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:49 node-4 multipathd: uevent trigger error
<129>Sep 22 17:03:51 node-4 haproxy[26579]: 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 22 17:03:51 node-4 haproxy[26579]: 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 22 17:03:52 node-4 haproxy[26583]: 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 22 17:03:52 node-4 haproxy[26583]: 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 22 17:03:52 node-4 haproxy[26583]: 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 22 17:03:53 node-4 haproxy[26583]: 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 22 17:03:54 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:54 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:54 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:54 node-4 multipathd: uevent trigger error
<27>Sep 22 17:03:54 node-4 multipathd: uevent trigger error
<129>Sep 22 17:03:54 node-4 haproxy[26583]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:03:55 node-4 haproxy[26583]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:03:55 node-4 haproxy[26583]: proxy aodh has no server available!
<129>Sep 22 17:03:57 node-4 haproxy[27779]: 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 22 17:03:57 node-4 haproxy[27779]: 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 22 17:03:57 node-4 haproxy[27779]: 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 22 17:03:57 node-4 haproxy[27779]: 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 22 17:03:58 node-4 haproxy[27779]: 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 22 17:03:58 node-4 haproxy[27779]: 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 22 17:03:58 node-4 haproxy[27779]: 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 22 17:04:00 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:00 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:00 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:00 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:00 node-4 multipathd: uevent trigger error
<129>Sep 22 17:04:00 node-4 haproxy[27779]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:00 node-4 haproxy[27779]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:00 node-4 haproxy[27779]: proxy aodh has no server available!
<129>Sep 22 17:04:00 node-4 haproxy[27779]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:00 node-4 haproxy[27779]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:00 node-4 haproxy[27779]: proxy ceilometer has no server available!
<129>Sep 22 17:04:02 node-4 haproxy[28952]: 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 22 17:04:02 node-4 haproxy[28952]: 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 22 17:04:03 node-4 haproxy[28961]: 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 22 17:04:03 node-4 haproxy[28961]: 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 22 17:04:03 node-4 haproxy[28961]: 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 22 17:04:03 node-4 haproxy[28961]: 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 22 17:04:04 node-4 haproxy[28961]: 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 22 17:04:05 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:05 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:05 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:05 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:05 node-4 multipathd: uevent trigger error
<129>Sep 22 17:04:05 node-4 haproxy[28961]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:05 node-4 haproxy[28961]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:05 node-4 haproxy[28961]: proxy aodh has no server available!
<129>Sep 22 17:04:05 node-4 haproxy[28961]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:06 node-4 haproxy[28961]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:06 node-4 haproxy[28961]: proxy ceilometer has no server available!
<129>Sep 22 17:04:07 node-4 haproxy[30253]: 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 22 17:04:08 node-4 haproxy[30257]: 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 22 17:04:08 node-4 haproxy[30257]: 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 22 17:04:08 node-4 haproxy[30257]: 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 22 17:04:08 node-4 haproxy[30257]: 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 22 17:04:09 node-4 haproxy[30257]: 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 22 17:04:09 node-4 haproxy[30257]: 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 22 17:04:09 node-4 haproxy[30257]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:09 node-4 haproxy[30257]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 22 17:04:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:10 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:10 node-4 multipathd: uevent trigger error
<129>Sep 22 17:04:10 node-4 haproxy[30257]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:11 node-4 haproxy[30257]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:11 node-4 haproxy[30257]: proxy aodh has no server available!
<129>Sep 22 17:04:11 node-4 haproxy[30257]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:11 node-4 haproxy[30257]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:11 node-4 haproxy[30257]: proxy ceilometer has no server available!
<129>Sep 22 17:04:13 node-4 haproxy[31480]: 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 22 17:04:13 node-4 haproxy[31480]: 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 22 17:04:13 node-4 haproxy[31480]: 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 22 17:04:13 node-4 haproxy[31480]: 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 22 17:04:14 node-4 haproxy[31484]: 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 22 17:04:14 node-4 haproxy[31484]: 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 22 17:04:14 node-4 haproxy[31484]: 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 22 17:04:14 node-4 haproxy[31484]: 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 22 17:04:14 node-4 haproxy[31484]: 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 22 17:04:14 node-4 haproxy[31484]: 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 22 17:04:15 node-4 haproxy[31484]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:15 node-4 haproxy[31484]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 22 17:04:16 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:16 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:16 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:16 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:16 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:16 node-4 multipathd: uevent trigger error
<129>Sep 22 17:04:16 node-4 haproxy[31484]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:16 node-4 haproxy[31484]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:16 node-4 haproxy[31484]: proxy glance-registry has no server available!
<129>Sep 22 17:04:16 node-4 haproxy[31484]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:16 node-4 haproxy[31484]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:16 node-4 haproxy[31484]: proxy aodh has no server available!
<129>Sep 22 17:04:16 node-4 haproxy[31484]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:16 node-4 haproxy[31484]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:16 node-4 haproxy[31484]: proxy ceilometer has no server available!
<129>Sep 22 17:04:18 node-4 haproxy[389]: 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 22 17:04:18 node-4 haproxy[389]: 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 22 17:04:19 node-4 haproxy[397]: 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 22 17:04:19 node-4 haproxy[397]: 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 22 17:04:19 node-4 haproxy[397]: 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 22 17:04:19 node-4 haproxy[397]: 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 22 17:04:19 node-4 haproxy[397]: 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 22 17:04:19 node-4 haproxy[397]: 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 22 17:04:19 node-4 haproxy[397]: 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 22 17:04:20 node-4 haproxy[397]: 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 22 17:04:20 node-4 haproxy[397]: 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 22 17:04:20 node-4 haproxy[397]: 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 22 17:04:20 node-4 haproxy[397]: 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 22 17:04:20 node-4 haproxy[397]: Server horizon/node-1 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 22 17:04:20 node-4 haproxy[397]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 22 17:04:21 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:21 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:21 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:21 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:21 node-4 multipathd: uevent trigger error
<129>Sep 22 17:04:21 node-4 haproxy[397]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:21 node-4 haproxy[397]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:21 node-4 haproxy[397]: proxy glance-registry has no server available!
<129>Sep 22 17:04:22 node-4 haproxy[397]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:22 node-4 haproxy[397]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:22 node-4 haproxy[397]: proxy aodh has no server available!
<129>Sep 22 17:04:22 node-4 haproxy[397]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:22 node-4 haproxy[397]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:22 node-4 haproxy[397]: proxy ceilometer has no server available!
<129>Sep 22 17:04:22 node-4 haproxy[397]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:22 node-4 haproxy[397]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:22 node-4 haproxy[397]: proxy nova-novncproxy has no server available!
<129>Sep 22 17:04:24 node-4 haproxy[1638]: 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 22 17:04:24 node-4 haproxy[1638]: 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 22 17:04:24 node-4 haproxy[1638]: 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 22 17:04:24 node-4 haproxy[1638]: 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 22 17:04:24 node-4 haproxy[1638]: 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 22 17:04:24 node-4 haproxy[1638]: 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 22 17:04:24 node-4 haproxy[1638]: 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 22 17:04:24 node-4 haproxy[1638]: 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 22 17:04:25 node-4 haproxy[1638]: 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 22 17:04:25 node-4 haproxy[1638]: 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 22 17:04:25 node-4 haproxy[1638]: 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 22 17:04:25 node-4 haproxy[1638]: 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 22 17:04:25 node-4 haproxy[1638]: 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 22 17:04:25 node-4 haproxy[1638]: 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 22 17:04:25 node-4 haproxy[1638]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:25 node-4 haproxy[1638]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 22 17:04:26 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:26 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:26 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:26 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:27 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:27 node-4 multipathd: uevent trigger error
<129>Sep 22 17:04:27 node-4 haproxy[1638]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:27 node-4 haproxy[1638]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:27 node-4 haproxy[1638]: proxy glance-registry has no server available!
<129>Sep 22 17:04:27 node-4 haproxy[1638]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:27 node-4 haproxy[1638]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:27 node-4 haproxy[1638]: proxy aodh has no server available!
<129>Sep 22 17:04:27 node-4 haproxy[1638]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:27 node-4 haproxy[1638]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:27 node-4 haproxy[1638]: proxy ceilometer has no server available!
<129>Sep 22 17:04:27 node-4 haproxy[1638]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:27 node-4 haproxy[1638]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:27 node-4 haproxy[1638]: proxy nova-novncproxy has no server available!
<27>Sep 22 17:04:27 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Sep 22 17:04:29 node-4 haproxy[2891]: 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 22 17:04:29 node-4 haproxy[2891]: 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 22 17:04:30 node-4 haproxy[2895]: 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 22 17:04:30 node-4 haproxy[2895]: 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 22 17:04:30 node-4 haproxy[2895]: 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 22 17:04:30 node-4 haproxy[2895]: 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 22 17:04:30 node-4 haproxy[2895]: 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 22 17:04:30 node-4 haproxy[2895]: 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 22 17:04:30 node-4 haproxy[2895]: 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 22 17:04:30 node-4 haproxy[2895]: 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 22 17:04:30 node-4 haproxy[2895]: 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 22 17:04:31 node-4 haproxy[2895]: 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 22 17:04:31 node-4 haproxy[2895]: 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 22 17:04:31 node-4 haproxy[2895]: 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 22 17:04:31 node-4 haproxy[2895]: 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 22 17:04:31 node-4 haproxy[2895]: 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 22 17:04:31 node-4 haproxy[2895]: 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 22 17:04:31 node-4 haproxy[2895]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:31 node-4 haproxy[2895]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:32 node-4 haproxy[2895]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:32 node-4 haproxy[2895]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:32 node-4 haproxy[2895]: proxy glance-registry has no server available!
<27>Sep 22 17:04:32 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:32 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:32 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:32 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:32 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:32 node-4 multipathd: uevent trigger error
<129>Sep 22 17:04:33 node-4 haproxy[2895]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:33 node-4 haproxy[2895]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:33 node-4 haproxy[2895]: proxy aodh has no server available!
<129>Sep 22 17:04:33 node-4 haproxy[2895]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:33 node-4 haproxy[2895]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:33 node-4 haproxy[2895]: proxy ceilometer has no server available!
<129>Sep 22 17:04:33 node-4 haproxy[2895]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:33 node-4 haproxy[2895]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:33 node-4 haproxy[2895]: proxy nova-novncproxy has no server available!
<27>Sep 22 17:04:35 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:35 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:35 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:35 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:35 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:35 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:39 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:39 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:39 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:39 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:39 node-4 multipathd: uevent trigger error
<27>Sep 22 17:04:39 node-4 multipathd: uevent trigger error
<129>Sep 22 17:04:39 node-4 haproxy[2895]: Server keystone-1/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:39 node-4 haproxy[2895]: Server keystone-1/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:39 node-4 haproxy[2895]: proxy keystone-1 has no server available!
<129>Sep 22 17:04:39 node-4 haproxy[2895]: Server keystone-2/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:39 node-4 haproxy[2895]: Server keystone-2/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:39 node-4 haproxy[2895]: proxy keystone-2 has no server available!
<129>Sep 22 17:04:40 node-4 haproxy[2895]: Server nova-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:40 node-4 haproxy[2895]: Server nova-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:40 node-4 haproxy[2895]: proxy nova-api has no server available!
<129>Sep 22 17:04:40 node-4 haproxy[2895]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:40 node-4 haproxy[2895]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:40 node-4 haproxy[2895]: proxy nova-metadata-api has no server available!
<129>Sep 22 17:04:40 node-4 haproxy[2895]: Server cinder-api/node-1 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 22 17:04:40 node-4 haproxy[2895]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:40 node-4 haproxy[2895]: proxy cinder-api has no server available!
<129>Sep 22 17:04:40 node-4 haproxy[2895]: Server glance-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:40 node-4 haproxy[2895]: Server glance-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:40 node-4 haproxy[2895]: proxy glance-api has no server available!
<129>Sep 22 17:04:40 node-4 haproxy[2895]: Server glance-glare/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:40 node-4 haproxy[2895]: Server glance-glare/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:40 node-4 haproxy[2895]: proxy glance-glare has no server available!
<129>Sep 22 17:04:40 node-4 haproxy[2895]: Server neutron/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:40 node-4 haproxy[2895]: Server neutron/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:40 node-4 haproxy[2895]: proxy neutron has no server available!
<129>Sep 22 17:04:40 node-4 haproxy[2895]: Server mysqld/node-1 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 22 17:04:40 node-4 haproxy[2895]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:40 node-4 haproxy[2895]: proxy mysqld has no server available!
<129>Sep 22 17:04:40 node-4 haproxy[2895]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:40 node-4 haproxy[2895]: Server object-storage/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:40 node-4 haproxy[2895]: proxy object-storage has no server available!
<129>Sep 22 17:04:41 node-4 haproxy[2895]: Server heat-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:41 node-4 haproxy[2895]: Server heat-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:41 node-4 haproxy[2895]: proxy heat-api has no server available!
<129>Sep 22 17:04:41 node-4 haproxy[2895]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:41 node-4 haproxy[2895]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:41 node-4 haproxy[2895]: proxy heat-api-cfn has no server available!
<129>Sep 22 17:04:41 node-4 haproxy[2895]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 22 17:04:41 node-4 haproxy[2895]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 22 17:04:41 node-4 haproxy[2895]: proxy heat-api-cloudwatch has no server available!
<27>Sep 22 17:05:15 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:15 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:15 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:15 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:15 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:20 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:20 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:20 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:20 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:20 node-4 multipathd: uevent trigger error
<43>Sep 22 17:05:20 node-4 apache2_error [Thu Sep 22 17:05:12.525409 2016] [mpm_worker:notice] [pid 9641:tid 139710317741952] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 22 17:05:20 node-4 apache2_error [Thu Sep 22 17:05:12.533673 2016] [mpm_worker:warn] [pid 9641:tid 139710317741952] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 22 17:05:20 node-4 apache2_error [Thu Sep 22 17:05:12.534349 2016] [mpm_worker:notice] [pid 9641:tid 139710317741952] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 22 17:05:20 node-4 apache2_error [Thu Sep 22 17:05:12.534361 2016] [core:notice] [pid 9641:tid 139710317741952] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 22 17:05:21 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 22 17:05:21 node-4 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 22 17:05:39 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:45 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 22 17:05:52 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:52 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:52 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:53 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:53 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:53 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:58 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:58 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:58 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:58 node-4 multipathd: uevent trigger error
<27>Sep 22 17:05:58 node-4 multipathd: uevent trigger error
<27>Sep 22 17:06:06 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 22 17:07:05 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 22 17:07:07 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 22 17:08:22 node-4 multipathd: uevent trigger error
<27>Sep 22 17:08:22 node-4 multipathd: uevent trigger error
<27>Sep 22 17:08:22 node-4 multipathd: uevent trigger error
<27>Sep 22 17:08:22 node-4 multipathd: uevent trigger error
<27>Sep 22 17:08:22 node-4 multipathd: uevent trigger error
<27>Sep 22 17:08:22 node-4 multipathd: uevent trigger error
<27>Sep 22 17:11:20 node-4 multipathd: uevent trigger error
<27>Sep 22 17:11:20 node-4 multipathd: uevent trigger error
<27>Sep 22 17:11:20 node-4 multipathd: uevent trigger error
<27>Sep 22 17:11:20 node-4 multipathd: uevent trigger error
<27>Sep 22 17:11:20 node-4 multipathd: uevent trigger error
<43>Sep 22 17:12:31 node-4 apache2_error [Thu Sep 22 17:12:25.885435 2016] [mpm_worker:notice] [pid 9641:tid 139710317741952] AH00295: caught SIGTERM, shutting down
<43>Sep 22 17:12:31 node-4 apache2_error [Thu Sep 22 17:12:26.628700 2016] [mpm_worker:notice] [pid 7028:tid 140129321199488] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 22 17:12:31 node-4 apache2_error [Thu Sep 22 17:12:26.628739 2016] [core:notice] [pid 7028:tid 140129321199488] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 22 17:13:01 node-4 apache2_error [Thu Sep 22 17:12:58.442134 2016] [mpm_worker:notice] [pid 7028:tid 140129321199488] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 22 17:13:01 node-4 apache2_error [Thu Sep 22 17:12:58.452698 2016] [mpm_worker:warn] [pid 7028:tid 140129321199488] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 22 17:13:01 node-4 apache2_error [Thu Sep 22 17:12:58.456608 2016] [mpm_worker:notice] [pid 7028:tid 140129321199488] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 22 17:13:01 node-4 apache2_error [Thu Sep 22 17:12:58.456631 2016] [core:notice] [pid 7028:tid 140129321199488] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 22 17:13:04 node-4 multipathd: uevent trigger error
<27>Sep 22 17:13:04 node-4 multipathd: uevent trigger error
<27>Sep 22 17:13:04 node-4 multipathd: uevent trigger error
<27>Sep 22 17:13:04 node-4 multipathd: uevent trigger error
<27>Sep 22 17:13:04 node-4 multipathd: uevent trigger error
<27>Sep 22 17:13:04 node-4 multipathd: uevent trigger error
<27>Sep 22 17:13:58 node-4 multipathd: uevent trigger error
<27>Sep 22 17:13:58 node-4 multipathd: uevent trigger error
<27>Sep 22 17:13:59 node-4 multipathd: uevent trigger error
<27>Sep 22 17:13:59 node-4 multipathd: uevent trigger error
<27>Sep 22 17:13:59 node-4 multipathd: uevent trigger error
<27>Sep 22 17:15:11 node-4 multipathd: uevent trigger error
<27>Sep 22 17:15:11 node-4 multipathd: uevent trigger error
<27>Sep 22 17:15:11 node-4 multipathd: uevent trigger error
<27>Sep 22 17:15:11 node-4 multipathd: uevent trigger error
<27>Sep 22 17:15:11 node-4 multipathd: uevent trigger error
<27>Sep 22 17:15:11 node-4 multipathd: uevent trigger error
<27>Sep 22 17:19:39 node-4 multipathd: uevent trigger error
<27>Sep 22 17:19:39 node-4 multipathd: uevent trigger error
<27>Sep 22 17:19:40 node-4 multipathd: uevent trigger error
<27>Sep 22 17:19:40 node-4 multipathd: uevent trigger error
<27>Sep 22 17:19:40 node-4 multipathd: uevent trigger error
<27>Sep 22 17:19:40 node-4 multipathd: uevent trigger error
<27>Sep 22 17:21:48 node-4 multipathd: uevent trigger error
<27>Sep 22 17:21:48 node-4 multipathd: uevent trigger error
<27>Sep 22 17:21:48 node-4 multipathd: uevent trigger error
<27>Sep 22 17:21:48 node-4 multipathd: uevent trigger error
<27>Sep 22 17:21:48 node-4 multipathd: uevent trigger error
<27>Sep 22 17:22:49 node-4 multipathd: uevent trigger error
<27>Sep 22 17:22:49 node-4 multipathd: uevent trigger error
<27>Sep 22 17:22:49 node-4 multipathd: uevent trigger error
<27>Sep 22 17:22:49 node-4 multipathd: uevent trigger error
<27>Sep 22 17:22:50 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:23 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:23 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:23 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:23 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:23 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:33 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:33 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:33 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:33 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:33 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:44 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-prv" in table Interface
<27>Sep 22 17:23:45 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-prv" in table Port
<27>Sep 22 17:23:45 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-prv" in table Port
<27>Sep 22 17:23:46 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Sep 22 17:23:46 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Sep 22 17:23:46 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Sep 22 17:23:47 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:47 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:47 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:47 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:47 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:47 node-4 multipathd: uevent trigger error
<27>Sep 22 17:23:47 node-4 multipathd: uevent trigger error
<27>Sep 22 17:24:04 node-4 multipathd: uevent trigger error
<27>Sep 22 17:24:04 node-4 multipathd: uevent trigger error
<27>Sep 22 17:24:04 node-4 multipathd: uevent trigger error
<27>Sep 22 17:24:04 node-4 multipathd: uevent trigger error
<27>Sep 22 17:24:04 node-4 multipathd: uevent trigger error
<27>Sep 22 17:24:04 node-4 multipathd: uevent trigger error
<27>Sep 22 17:24:14 node-4 multipathd: uevent trigger error
<27>Sep 22 17:24:14 node-4 multipathd: uevent trigger error
<27>Sep 22 17:24:14 node-4 multipathd: uevent trigger error
<27>Sep 22 17:24:14 node-4 multipathd: uevent trigger error
<27>Sep 22 17:24:14 node-4 multipathd: uevent trigger error
<27>Sep 22 17:24:14 node-4 multipathd: uevent trigger error
<43>Sep 22 17:25:02 node-4 apache2_error [Thu Sep 22 17:25:01.413297 2016] [mpm_worker:notice] [pid 7028:tid 140129321199488] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 22 17:25:02 node-4 apache2_error [Thu Sep 22 17:25:01.802800 2016] [mpm_worker:warn] [pid 7028:tid 140129321199488] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 22 17:25:02 node-4 apache2_error [Thu Sep 22 17:25:01.809838 2016] [mpm_worker:notice] [pid 7028:tid 140129321199488] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 22 17:25:02 node-4 apache2_error [Thu Sep 22 17:25:01.809875 2016] [core:notice] [pid 7028:tid 140129321199488] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 22 17:25:42 node-4 apache2_error [Thu Sep 22 17:25:38.472399 2016] [mpm_worker:notice] [pid 7028:tid 140129321199488] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 22 17:25:42 node-4 apache2_error [Thu Sep 22 17:25:38.854998 2016] [mpm_worker:warn] [pid 7028:tid 140129321199488] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 22 17:25:42 node-4 apache2_error [Thu Sep 22 17:25:38.870219 2016] [mpm_worker:notice] [pid 7028:tid 140129321199488] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 22 17:25:42 node-4 apache2_error [Thu Sep 22 17:25:38.870243 2016] [core:notice] [pid 7028:tid 140129321199488] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 22 17:25:42 node-4 multipathd: uevent trigger error
<27>Sep 22 17:25:42 node-4 multipathd: uevent trigger error
<27>Sep 22 17:25:42 node-4 multipathd: uevent trigger error
<27>Sep 22 17:25:42 node-4 multipathd: uevent trigger error
<27>Sep 22 17:25:42 node-4 multipathd: uevent trigger error
<27>Sep 22 17:26:15 node-4 multipathd: uevent trigger error
<27>Sep 22 17:26:15 node-4 multipathd: uevent trigger error
<27>Sep 22 17:26:15 node-4 multipathd: uevent trigger error
<27>Sep 22 17:26:15 node-4 multipathd: uevent trigger error
<27>Sep 22 17:26:15 node-4 multipathd: uevent trigger error
<27>Sep 22 17:26:26 node-4 multipathd: uevent trigger error
<27>Sep 22 17:26:26 node-4 multipathd: uevent trigger error
<27>Sep 22 17:26:26 node-4 multipathd: uevent trigger error
<27>Sep 22 17:26:26 node-4 multipathd: uevent trigger error
<27>Sep 22 17:26:26 node-4 multipathd: uevent trigger error
<27>Sep 22 17:28:02 node-4 multipathd: uevent trigger error
<27>Sep 22 17:28:02 node-4 multipathd: uevent trigger error
<27>Sep 22 17:28:02 node-4 multipathd: uevent trigger error
<27>Sep 22 17:28:02 node-4 multipathd: uevent trigger error
<27>Sep 22 17:28:02 node-4 multipathd: uevent trigger error
<27>Sep 22 17:28:49 node-4 multipathd: uevent trigger error
<27>Sep 22 17:28:49 node-4 multipathd: uevent trigger error
<27>Sep 22 17:28:49 node-4 multipathd: uevent trigger error
<27>Sep 22 17:28:49 node-4 multipathd: uevent trigger error
<27>Sep 22 17:28:49 node-4 multipathd: uevent trigger error
<27>Sep 22 17:29:00 node-4 multipathd: uevent trigger error
<27>Sep 22 17:29:00 node-4 multipathd: uevent trigger error
<27>Sep 22 17:29:00 node-4 multipathd: uevent trigger error
<27>Sep 22 17:29:00 node-4 multipathd: uevent trigger error
<27>Sep 22 17:29:00 node-4 multipathd: uevent trigger error
<11>Sep 22 17:29:09 node-4 liberasurecode[32128]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:09 node-4 liberasurecode[32128]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:09 node-4 liberasurecode[32128]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:09 node-4 liberasurecode[32128]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:09 node-4 liberasurecode[32240]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:09 node-4 liberasurecode[32240]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:09 node-4 liberasurecode[32240]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:09 node-4 liberasurecode[32240]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:11 node-4 liberasurecode[1027]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:11 node-4 liberasurecode[1027]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:11 node-4 liberasurecode[1027]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:11 node-4 liberasurecode[1027]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:15 node-4 liberasurecode[2259]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:15 node-4 liberasurecode[2259]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:15 node-4 liberasurecode[2259]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:15 node-4 liberasurecode[2259]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2300]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2300]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2300]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2300]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2348]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2348]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2348]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2348]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2410]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2410]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2410]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2410]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2424]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2424]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2424]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2424]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2436]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2436]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2436]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2436]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2449]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2449]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2449]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:29:16 node-4 liberasurecode[2449]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 22 17:29:23 node-4 multipathd: uevent trigger error
<27>Sep 22 17:29:23 node-4 multipathd: uevent trigger error
<27>Sep 22 17:29:23 node-4 multipathd: uevent trigger error
<27>Sep 22 17:29:23 node-4 multipathd: uevent trigger error
<27>Sep 22 17:29:28 node-4 multipathd: uevent trigger error
<27>Sep 22 17:29:28 node-4 multipathd: uevent trigger error
<27>Sep 22 17:29:28 node-4 multipathd: uevent trigger error
<27>Sep 22 17:29:28 node-4 multipathd: uevent trigger error
<27>Sep 22 17:29:28 node-4 multipathd: uevent trigger error
<27>Sep 22 17:29:28 node-4 multipathd: uevent trigger error
<11>Sep 22 17:30:01 node-4 liberasurecode[10934]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:30:01 node-4 liberasurecode[10934]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:30:01 node-4 liberasurecode[10934]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:30:01 node-4 liberasurecode[10934]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 22 17:30:31 node-4 multipathd: uevent trigger error
<27>Sep 22 17:30:31 node-4 multipathd: uevent trigger error
<27>Sep 22 17:30:31 node-4 multipathd: uevent trigger error
<27>Sep 22 17:30:31 node-4 multipathd: uevent trigger error
<27>Sep 22 17:30:31 node-4 multipathd: uevent trigger error
<27>Sep 22 17:32:40 node-4 multipathd: uevent trigger error
<27>Sep 22 17:32:40 node-4 multipathd: uevent trigger error
<27>Sep 22 17:32:40 node-4 multipathd: uevent trigger error
<27>Sep 22 17:32:40 node-4 multipathd: uevent trigger error
<27>Sep 22 17:32:40 node-4 multipathd: uevent trigger error
<27>Sep 22 17:32:45 node-4 multipathd: uevent trigger error
<27>Sep 22 17:32:45 node-4 multipathd: uevent trigger error
<27>Sep 22 17:32:45 node-4 multipathd: uevent trigger error
<27>Sep 22 17:32:45 node-4 multipathd: uevent trigger error
<27>Sep 22 17:32:45 node-4 multipathd: uevent trigger error
<27>Sep 22 17:32:58 node-4 multipathd: uevent trigger error
<27>Sep 22 17:32:58 node-4 multipathd: uevent trigger error
<27>Sep 22 17:32:58 node-4 multipathd: uevent trigger error
<27>Sep 22 17:32:58 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:03 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:03 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:03 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:03 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:03 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:18 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:18 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:18 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:18 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:18 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:18 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:25 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:25 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:25 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:25 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:25 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:29 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:29 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:29 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:29 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:29 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:33 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:33 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:33 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:33 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:34 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:38 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:38 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:38 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:38 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:38 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:38 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:43 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:43 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:43 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:43 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:43 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:47 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:47 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:47 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:47 node-4 multipathd: uevent trigger error
<27>Sep 22 17:33:47 node-4 multipathd: uevent trigger error
<27>Sep 22 17:34:19 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 22 17:34:19 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<11>Sep 22 17:35:01 node-4 liberasurecode[29602]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:35:01 node-4 liberasurecode[29602]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:35:01 node-4 liberasurecode[29602]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 22 17:35:01 node-4 liberasurecode[29602]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
