Jul 26 21:10:01 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8372" x-info="http://www.rsyslog.com"] start
Jul 26 21:10:01 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 26 21:10:01 node-4 rsyslogd: rsyslogd's groupid changed to 104
Jul 26 21:10:01 node-4 rsyslogd: rsyslogd's userid changed to 101
Jul 26 21:10:01 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 26 21:10:01 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 26 21:10:01 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 26 21:10:01 node-4 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 26 21:10:01 node-4 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=d6a4002d-fcf3-4b0b-8dec-ac0a764030af nomdmonddf nomdmonisw
Jul 26 21:10:01 node-4 kernel: [    0.000000] KERNEL supported cpus:
Jul 26 21:10:01 node-4 kernel: [    0.000000]   Intel GenuineIntel
Jul 26 21:10:01 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Jul 26 21:10:01 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Jul 26 21:10:01 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 26 21:10:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 26 21:10:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 26 21:10:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 26 21:10:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 26 21:10:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 26 21:10:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 26 21:10:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 26 21:10:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 26 21:10:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 26 21:10:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 26 21:10:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 26 21:10:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 26 21:10:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 26 21:10:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 26 21:10:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 26 21:10:01 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 26 21:10:01 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 26 21:10:01 node-4 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 26 21:10:01 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 26 21:10:01 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 26 21:10:01 node-4 kernel: [    0.000000] No AGP bridge found
Jul 26 21:10:01 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 26 21:10:01 node-4 kernel: [    0.000000] MTRR default type: write-back
Jul 26 21:10:01 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 26 21:10:01 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Jul 26 21:10:01 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 26 21:10:01 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 26 21:10:01 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 26 21:10:01 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 26 21:10:01 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 26 21:10:01 node-4 kernel: [    0.000000]   2 disabled
Jul 26 21:10:01 node-4 kernel: [    0.000000]   3 disabled
Jul 26 21:10:01 node-4 kernel: [    0.000000]   4 disabled
Jul 26 21:10:01 node-4 kernel: [    0.000000]   5 disabled
Jul 26 21:10:01 node-4 kernel: [    0.000000]   6 disabled
Jul 26 21:10:01 node-4 kernel: [    0.000000]   7 disabled
Jul 26 21:10:01 node-4 kernel: [    0.000000]   8 disabled
Jul 26 21:10:01 node-4 kernel: [    0.000000]   9 disabled
Jul 26 21:10:01 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 26 21:10:01 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 26 21:10:01 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 26 21:10:01 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 26 21:10:01 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 26 21:10:01 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Jul 26 21:10:01 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 26 21:10:01 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 26 21:10:01 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 26 21:10:01 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 26 21:10:01 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 26 21:10:01 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 26 21:10:01 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 26 21:10:01 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 26 21:10:01 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 26 21:10:01 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 26 21:10:01 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 26 21:10:01 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 26 21:10:01 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 26 21:10:01 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 26 21:10:01 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 26 21:10:01 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 26 21:10:01 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 26 21:10:01 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 26 21:10:01 node-4 kernel: [    0.000000] Zone ranges:
Jul 26 21:10:01 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] Movable zone start for each node
Jul 26 21:10:01 node-4 kernel: [    0.000000] Early memory node ranges
Jul 26 21:10:01 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 26 21:10:01 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 26 21:10:01 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 26 21:10:01 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 26 21:10:01 node-4 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 26 21:10:01 node-4 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 26 21:10:01 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 26 21:10:01 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 26 21:10:01 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 26 21:10:01 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 26 21:10:01 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 26 21:10:01 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 26 21:10:01 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 26 21:10:01 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 26 21:10:01 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 26 21:10:01 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 26 21:10:01 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 26 21:10:01 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 26 21:10:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 26 21:10:01 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 26 21:10:01 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 26 21:10:01 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 26 21:10:01 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 26 21:10:01 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 26 21:10:01 node-4 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 26 21:10:01 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 26 21:10:01 node-4 kernel: [    0.000000] Policy zone: Normal
Jul 26 21:10:01 node-4 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=d6a4002d-fcf3-4b0b-8dec-ac0a764030af nomdmonddf nomdmonisw
Jul 26 21:10:01 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 26 21:10:01 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 26 21:10:01 node-4 kernel: [    0.000000] Checking aperture...
Jul 26 21:10:01 node-4 kernel: [    0.000000] No AGP bridge found
Jul 26 21:10:01 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 26 21:10:01 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 26 21:10:01 node-4 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 26 21:10:01 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 26 21:10:01 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 26 21:10:01 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 26 21:10:01 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 26 21:10:01 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 26 21:10:01 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 26 21:10:01 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 26 21:10:01 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 26 21:10:01 node-4 kernel: [    0.000000] console [tty0] enabled
Jul 26 21:10:01 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 26 21:10:01 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 26 21:10:01 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 26 21:10:01 node-4 kernel: [    0.000000] hpet clockevent registered
Jul 26 21:10:01 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 26 21:10:01 node-4 kernel: [    0.004000] tsc: Detected 3492.261 MHz processor
Jul 26 21:10:01 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.52 BogoMIPS (lpj=13969044)
Jul 26 21:10:01 node-4 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 26 21:10:01 node-4 kernel: [    0.000043] Security Framework initialized
Jul 26 21:10:01 node-4 kernel: [    0.000061] AppArmor: AppArmor initialized
Jul 26 21:10:01 node-4 kernel: [    0.000062] Yama: becoming mindful.
Jul 26 21:10:01 node-4 kernel: [    0.001447] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 26 21:10:01 node-4 kernel: [    0.006328] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 26 21:10:01 node-4 kernel: [    0.008257] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 26 21:10:01 node-4 kernel: [    0.008285] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 26 21:10:01 node-4 kernel: [    0.008574] Initializing cgroup subsys memory
Jul 26 21:10:01 node-4 kernel: [    0.008582] Initializing cgroup subsys devices
Jul 26 21:10:01 node-4 kernel: [    0.008584] Initializing cgroup subsys freezer
Jul 26 21:10:01 node-4 kernel: [    0.008586] Initializing cgroup subsys blkio
Jul 26 21:10:01 node-4 kernel: [    0.008587] Initializing cgroup subsys perf_event
Jul 26 21:10:01 node-4 kernel: [    0.008590] Initializing cgroup subsys hugetlb
Jul 26 21:10:01 node-4 kernel: [    0.008609] CPU: Physical Processor ID: 0
Jul 26 21:10:01 node-4 kernel: [    0.008610] CPU: Processor Core ID: 0
Jul 26 21:10:01 node-4 kernel: [    0.008614] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 26 21:10:01 node-4 kernel: [    0.008614] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 26 21:10:01 node-4 kernel: [    0.009307] mce: CPU supports 22 MCE banks
Jul 26 21:10:01 node-4 kernel: [    0.009335] CPU0: Thermal monitoring enabled (TM1)
Jul 26 21:10:01 node-4 kernel: [    0.009356] process: using mwait in idle threads
Jul 26 21:10:01 node-4 kernel: [    0.009359] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 26 21:10:01 node-4 kernel: [    0.009359] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 26 21:10:01 node-4 kernel: [    0.009359] tlb_flushall_shift: 6
Jul 26 21:10:01 node-4 kernel: [    0.009447] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 26 21:10:01 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 26 21:10:01 node-4 kernel: [    0.010172] ACPI: Core revision 20131115
Jul 26 21:10:01 node-4 kernel: [    0.022854] ACPI: All ACPI Tables successfully acquired
Jul 26 21:10:01 node-4 kernel: [    0.023024] ftrace: allocating 28617 entries in 112 pages
Jul 26 21:10:01 node-4 kernel: [    0.031843] dmar: Host address width 46
Jul 26 21:10:01 node-4 kernel: [    0.031846] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 26 21:10:01 node-4 kernel: [    0.031852] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 26 21:10:01 node-4 kernel: [    0.031854] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 26 21:10:01 node-4 kernel: [    0.031858] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 26 21:10:01 node-4 kernel: [    0.031859] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 26 21:10:01 node-4 kernel: [    0.031861] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 26 21:10:01 node-4 kernel: [    0.031862] dmar: ATSR flags: 0x0
Jul 26 21:10:01 node-4 kernel: [    0.031863] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 26 21:10:01 node-4 kernel: [    0.031864] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 26 21:10:01 node-4 kernel: [    0.031979] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 26 21:10:01 node-4 kernel: [    0.031980] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 26 21:10:01 node-4 kernel: [    0.031981] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 26 21:10:01 node-4 kernel: [    0.031982] HPET id 0 under DRHD base 0xc7ffc000
Jul 26 21:10:01 node-4 kernel: [    0.031983] Your BIOS is broken and requested that x2apic be disabled.
Jul 26 21:10:01 node-4 kernel: [    0.031983] This will slightly decrease performance.
Jul 26 21:10:01 node-4 kernel: [    0.031983] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 26 21:10:01 node-4 kernel: [    0.032415] Enabled IRQ remapping in xapic mode
Jul 26 21:10:01 node-4 kernel: [    0.032416] x2apic not enabled, IRQ remapping is in xapic mode
Jul 26 21:10:01 node-4 kernel: [    0.032420] Switched APIC routing to physical flat.
Jul 26 21:10:01 node-4 kernel: [    0.033039] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 26 21:10:01 node-4 kernel: [    0.072692] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 26 21:10:01 node-4 kernel: [    0.072698] TSC deadline timer enabled
Jul 26 21:10:01 node-4 kernel: [    0.072705] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 26 21:10:01 node-4 kernel: [    0.072711] ... version:                3
Jul 26 21:10:01 node-4 kernel: [    0.072712] ... bit width:              48
Jul 26 21:10:01 node-4 kernel: [    0.072713] ... generic registers:      4
Jul 26 21:10:01 node-4 kernel: [    0.072714] ... value mask:             0000ffffffffffff
Jul 26 21:10:01 node-4 kernel: [    0.072715] ... max period:             0000ffffffffffff
Jul 26 21:10:01 node-4 kernel: [    0.072716] ... fixed-purpose events:   3
Jul 26 21:10:01 node-4 kernel: [    0.072717] ... event mask:             000000070000000f
Jul 26 21:10:01 node-4 kernel: [    0.074175] x86: Booting SMP configuration:
Jul 26 21:10:01 node-4 kernel: [    0.088379] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 26 21:10:01 node-4 kernel: [    0.074177] .... node  #0, CPUs:        #1  #2  #3
Jul 26 21:10:01 node-4 kernel: [    0.116290] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 26 21:10:01 node-4 kernel: [    0.270451] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 26 21:10:01 node-4 kernel: [    0.326076] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 26 21:10:01 node-4 kernel: [    0.382946] x86: Booted up 2 nodes, 16 CPUs
Jul 26 21:10:01 node-4 kernel: [    0.382949] smpboot: Total of 16 processors activated (111764.57 BogoMIPS)
Jul 26 21:10:01 node-4 kernel: [    0.406507] devtmpfs: initialized
Jul 26 21:10:01 node-4 kernel: [    0.409629] EVM: security.selinux
Jul 26 21:10:01 node-4 kernel: [    0.409631] EVM: security.SMACK64
Jul 26 21:10:01 node-4 kernel: [    0.409632] EVM: security.ima
Jul 26 21:10:01 node-4 kernel: [    0.409633] EVM: security.capability
Jul 26 21:10:01 node-4 kernel: [    0.409682] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 26 21:10:01 node-4 kernel: [    0.410361] pinctrl core: initialized pinctrl subsystem
Jul 26 21:10:01 node-4 kernel: [    0.410424] regulator-dummy: no parameters
Jul 26 21:10:01 node-4 kernel: [    0.410456] RTC time: 21:09:25, date: 07/26/16
Jul 26 21:10:01 node-4 kernel: [    0.410490] NET: Registered protocol family 16
Jul 26 21:10:01 node-4 kernel: [    0.410574] cpuidle: using governor ladder
Jul 26 21:10:01 node-4 kernel: [    0.410576] cpuidle: using governor menu
Jul 26 21:10:01 node-4 kernel: [    0.410610] ACPI: bus type PCI registered
Jul 26 21:10:01 node-4 kernel: [    0.410612] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 26 21:10:01 node-4 kernel: [    0.410660] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 26 21:10:01 node-4 kernel: [    0.410662] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 26 21:10:01 node-4 kernel: [    0.424393] PCI: Using configuration type 1 for base access
Jul 26 21:10:01 node-4 kernel: [    0.425396] bio: create slab <bio-0> at 0
Jul 26 21:10:01 node-4 kernel: [    0.425676] ACPI: Added _OSI(Module Device)
Jul 26 21:10:01 node-4 kernel: [    0.425678] ACPI: Added _OSI(Processor Device)
Jul 26 21:10:01 node-4 kernel: [    0.425679] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 26 21:10:01 node-4 kernel: [    0.425680] ACPI: Added _OSI(Processor Aggregator Device)
Jul 26 21:10:01 node-4 kernel: [    0.438280] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 26 21:10:01 node-4 kernel: [    0.448982] ACPI: Interpreter enabled
Jul 26 21:10:01 node-4 kernel: [    0.448987] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 26 21:10:01 node-4 kernel: [    0.448991] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 26 21:10:01 node-4 kernel: [    0.448994] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 26 21:10:01 node-4 kernel: [    0.449001] ACPI: (supports S0 S4 S5)
Jul 26 21:10:01 node-4 kernel: [    0.449002] ACPI: Using IOAPIC for interrupt routing
Jul 26 21:10:01 node-4 kernel: [    0.449042] HEST: Table parsing has been initialized.
Jul 26 21:10:01 node-4 kernel: [    0.449045] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 26 21:10:01 node-4 kernel: [    0.449599] ACPI: No dock devices found.
Jul 26 21:10:01 node-4 kernel: [    0.461228] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 26 21:10:01 node-4 kernel: [    0.461233] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 21:10:01 node-4 kernel: [    0.461237] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 26 21:10:01 node-4 kernel: [    0.461263] PCI host bridge to bus 0000:ff
Jul 26 21:10:01 node-4 kernel: [    0.461265] pci_bus 0000:ff: root bus resource [bus ff]
Jul 26 21:10:01 node-4 kernel: [    0.461273] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461311] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 26 21:10:01 node-4 kernel: [    0.461341] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461376] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461405] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 26 21:10:01 node-4 kernel: [    0.461434] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 26 21:10:01 node-4 kernel: [    0.461464] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461492] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461521] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461549] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461575] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461601] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461629] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461655] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461681] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461707] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461736] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461763] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461789] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 26 21:10:01 node-4 kernel: [    0.461817] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461842] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 26 21:10:01 node-4 kernel: [    0.461867] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461893] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461923] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 26 21:10:01 node-4 kernel: [    0.461957] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.461988] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462017] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462048] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462078] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462109] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462141] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462170] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462201] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462233] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462264] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462296] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462330] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462360] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462387] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462420] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462454] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462490] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462525] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462557] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462587] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462617] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462648] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462676] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462709] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462739] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462771] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462799] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462828] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462856] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462885] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462916] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.462947] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463003] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 26 21:10:01 node-4 kernel: [    0.463006] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 21:10:01 node-4 kernel: [    0.463009] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 26 21:10:01 node-4 kernel: [    0.463026] PCI host bridge to bus 0000:7f
Jul 26 21:10:01 node-4 kernel: [    0.463028] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 26 21:10:01 node-4 kernel: [    0.463033] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463063] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 26 21:10:01 node-4 kernel: [    0.463092] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463121] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463142] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 26 21:10:01 node-4 kernel: [    0.463166] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 26 21:10:01 node-4 kernel: [    0.463193] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463219] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463241] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463263] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463286] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463310] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463335] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463358] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463383] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463408] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463430] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463453] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463475] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 26 21:10:01 node-4 kernel: [    0.463498] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463521] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 26 21:10:01 node-4 kernel: [    0.463544] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463568] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463595] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 26 21:10:01 node-4 kernel: [    0.463631] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463660] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463688] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463716] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463741] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463769] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463797] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463827] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463854] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463882] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463910] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463939] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463968] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.463995] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464019] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464048] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464073] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464102] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464132] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464161] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464186] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464211] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464236] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464267] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464295] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464322] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464352] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464379] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464402] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464428] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464454] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464484] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.464510] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.465769] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 26 21:10:01 node-4 kernel: [    0.465773] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 21:10:01 node-4 kernel: [    0.466891] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 26 21:10:01 node-4 kernel: [    0.467400] PCI host bridge to bus 0000:00
Jul 26 21:10:01 node-4 kernel: [    0.467402] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 26 21:10:01 node-4 kernel: [    0.467404] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 26 21:10:01 node-4 kernel: [    0.467405] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 26 21:10:01 node-4 kernel: [    0.467407] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 26 21:10:01 node-4 kernel: [    0.467408] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 26 21:10:01 node-4 kernel: [    0.467409] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 26 21:10:01 node-4 kernel: [    0.467411] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 26 21:10:01 node-4 kernel: [    0.467417] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 26 21:10:01 node-4 kernel: [    0.467499] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 26 21:10:01 node-4 kernel: [    0.467530] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:01 node-4 kernel: [    0.467571] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 26 21:10:01 node-4 kernel: [    0.467591] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 26 21:10:01 node-4 kernel: [    0.467621] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:01 node-4 kernel: [    0.467662] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 26 21:10:01 node-4 kernel: [    0.467682] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 26 21:10:01 node-4 kernel: [    0.467711] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:01 node-4 kernel: [    0.467751] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 26 21:10:01 node-4 kernel: [    0.467768] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.467839] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.467915] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.467993] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 26 21:10:01 node-4 kernel: [    0.467997] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 26 21:10:01 node-4 kernel: [    0.468083] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 26 21:10:01 node-4 kernel: [    0.468231] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 26 21:10:01 node-4 kernel: [    0.468249] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 26 21:10:01 node-4 kernel: [    0.468326] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:01 node-4 kernel: [    0.468379] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 26 21:10:01 node-4 kernel: [    0.468402] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 26 21:10:01 node-4 kernel: [    0.468457] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:01 node-4 kernel: [    0.468500] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 26 21:10:01 node-4 kernel: [    0.468529] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 26 21:10:01 node-4 kernel: [    0.468585] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 26 21:10:01 node-4 kernel: [    0.468627] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 26 21:10:01 node-4 kernel: [    0.468652] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 26 21:10:01 node-4 kernel: [    0.468670] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 26 21:10:01 node-4 kernel: [    0.468747] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:01 node-4 kernel: [    0.468797] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 26 21:10:01 node-4 kernel: [    0.468827] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 26 21:10:01 node-4 kernel: [    0.469075] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 26 21:10:01 node-4 kernel: [    0.469081] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 26 21:10:01 node-4 kernel: [    0.469087] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 26 21:10:01 node-4 kernel: [    0.469093] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 26 21:10:01 node-4 kernel: [    0.469100] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 26 21:10:01 node-4 kernel: [    0.469130] pci 0000:01:00.0: supports D1 D2
Jul 26 21:10:01 node-4 kernel: [    0.479076] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 26 21:10:01 node-4 kernel: [    0.479083] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 26 21:10:01 node-4 kernel: [    0.479087] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 26 21:10:01 node-4 kernel: [    0.479349] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 26 21:10:01 node-4 kernel: [    0.479408] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 26 21:10:01 node-4 kernel: [    0.487074] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 26 21:10:01 node-4 kernel: [    0.487080] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:01 node-4 kernel: [    0.487084] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 21:10:01 node-4 kernel: [    0.487176] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 26 21:10:01 node-4 kernel: [    0.487244] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 26 21:10:01 node-4 kernel: [    0.487321] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:01 node-4 kernel: [    0.487366] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 26 21:10:01 node-4 kernel: [    0.487370] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:01 node-4 kernel: [    0.487371] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 21:10:01 node-4 kernel: [    0.487424] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 26 21:10:01 node-4 kernel: [    0.487566] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:01 node-4 kernel: [    0.487620] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 26 21:10:01 node-4 kernel: [    0.487622] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:01 node-4 kernel: [    0.487625] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 21:10:01 node-4 kernel: [    0.487673] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 26 21:10:01 node-4 kernel: [    0.487793] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:01 node-4 kernel: [    0.487836] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 26 21:10:01 node-4 kernel: [    0.487955] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:01 node-4 kernel: [    0.487994] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 26 21:10:01 node-4 kernel: [    0.488113] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:01 node-4 kernel: [    0.488152] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 26 21:10:01 node-4 kernel: [    0.488273] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 26 21:10:01 node-4 kernel: [    0.488317] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 26 21:10:01 node-4 kernel: [    0.488320] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:01 node-4 kernel: [    0.488322] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 21:10:01 node-4 kernel: [    0.488380] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 26 21:10:01 node-4 kernel: [    0.488443] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 26 21:10:01 node-4 kernel: [    0.488520] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 26 21:10:01 node-4 kernel: [    0.488560] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 26 21:10:01 node-4 kernel: [    0.488640] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 26 21:10:01 node-4 kernel: [    0.488748] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 26 21:10:01 node-4 kernel: [    0.488750] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:01 node-4 kernel: [    0.488752] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 26 21:10:01 node-4 kernel: [    0.488808] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 26 21:10:01 node-4 kernel: [    0.488865] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 26 21:10:01 node-4 kernel: [    0.488914] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 26 21:10:01 node-4 kernel: [    0.489126] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 26 21:10:01 node-4 kernel: [    0.489130] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 26 21:10:01 node-4 kernel: [    0.489193] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 26 21:10:01 node-4 kernel: [    0.489246] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 26 21:10:01 node-4 kernel: [    0.489294] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 26 21:10:01 node-4 kernel: [    0.489524] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 26 21:10:01 node-4 kernel: [    0.489528] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 26 21:10:01 node-4 kernel: [    0.489587] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 26 21:10:01 node-4 kernel: [    0.489651] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 26 21:10:01 node-4 kernel: [    0.489703] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 26 21:10:01 node-4 kernel: [    0.489926] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 26 21:10:01 node-4 kernel: [    0.489929] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 26 21:10:01 node-4 kernel: [    0.490104] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 26 21:10:01 node-4 kernel: [    0.490142] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 26 21:10:01 node-4 kernel: [    0.490217] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 26 21:10:01 node-4 kernel: [    0.490236] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 26 21:10:01 node-4 kernel: [    0.490249] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 26 21:10:01 node-4 kernel: [    0.490262] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 26 21:10:01 node-4 kernel: [    0.490312] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 26 21:10:01 node-4 kernel: [    0.495086] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 26 21:10:01 node-4 kernel: [    0.495095] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 26 21:10:01 node-4 kernel: [    0.495155] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 26 21:10:01 node-4 kernel: [    0.495645] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 26 21:10:01 node-4 kernel: [    0.495648] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 21:10:01 node-4 kernel: [    0.495772] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 26 21:10:01 node-4 kernel: [    0.495879] PCI host bridge to bus 0000:80
Jul 26 21:10:01 node-4 kernel: [    0.495882] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 26 21:10:01 node-4 kernel: [    0.495883] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 26 21:10:01 node-4 kernel: [    0.495884] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 26 21:10:01 node-4 kernel: [    0.495892] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.495956] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.496027] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 26 21:10:01 node-4 kernel: [    0.496089] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 26 21:10:01 node-4 kernel: [    0.496094] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 26 21:10:01 node-4 kernel: [    0.496167] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 26 21:10:01 node-4 kernel: [    0.496466] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 26 21:10:01 node-4 kernel: [    0.496497] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 26 21:10:01 node-4 kernel: [    0.496527] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 26 21:10:01 node-4 kernel: [    0.496556] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 26 21:10:01 node-4 kernel: [    0.496585] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 21:10:01 node-4 kernel: [    0.496615] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 21:10:01 node-4 kernel: [    0.496645] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 21:10:01 node-4 kernel: [    0.496674] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 21:10:01 node-4 kernel: [    0.496760] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 26 21:10:01 node-4 kernel: [    0.496764] ACPI: \_SB_.UNC1: notify handler is installed
Jul 26 21:10:01 node-4 kernel: [    0.496766] ACPI: \_SB_.UNC0: notify handler is installed
Jul 26 21:10:01 node-4 kernel: [    0.496781] ACPI: \_SB_.PCI0: notify handler is installed
Jul 26 21:10:01 node-4 kernel: [    0.496834] ACPI: \_SB_.PCI1: notify handler is installed
Jul 26 21:10:01 node-4 kernel: [    0.496913] Found 4 acpi root devices
Jul 26 21:10:01 node-4 kernel: [    0.497024] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 26 21:10:01 node-4 kernel: [    0.497026] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 26 21:10:01 node-4 kernel: [    0.497028] vgaarb: loaded
Jul 26 21:10:01 node-4 kernel: [    0.497029] vgaarb: bridge control possible 0000:0c:00.0
Jul 26 21:10:01 node-4 kernel: [    0.497152] SCSI subsystem initialized
Jul 26 21:10:01 node-4 kernel: [    0.497216] libata version 3.00 loaded.
Jul 26 21:10:01 node-4 kernel: [    0.497238] ACPI: bus type USB registered
Jul 26 21:10:01 node-4 kernel: [    0.497248] usbcore: registered new interface driver usbfs
Jul 26 21:10:01 node-4 kernel: [    0.497253] usbcore: registered new interface driver hub
Jul 26 21:10:01 node-4 kernel: [    0.497274] usbcore: registered new device driver usb
Jul 26 21:10:01 node-4 kernel: [    0.497450] PCI: Using ACPI for IRQ routing
Jul 26 21:10:01 node-4 kernel: [    0.501066] PCI: pci_cache_line_size set to 64 bytes
Jul 26 21:10:01 node-4 kernel: [    0.501278] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 26 21:10:01 node-4 kernel: [    0.501280] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 26 21:10:01 node-4 kernel: [    0.501281] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 26 21:10:01 node-4 kernel: [    0.501348] NetLabel: Initializing
Jul 26 21:10:01 node-4 kernel: [    0.501349] NetLabel:  domain hash size = 128
Jul 26 21:10:01 node-4 kernel: [    0.501350] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 26 21:10:01 node-4 kernel: [    0.501360] NetLabel:  unlabeled traffic allowed by default
Jul 26 21:10:01 node-4 kernel: [    0.501416] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 26 21:10:01 node-4 kernel: [    0.501420] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 26 21:10:01 node-4 kernel: [    0.503476] Switched to clocksource hpet
Jul 26 21:10:01 node-4 kernel: [    0.507456] AppArmor: AppArmor Filesystem Enabled
Jul 26 21:10:01 node-4 kernel: [    0.507475] pnp: PnP ACPI init
Jul 26 21:10:01 node-4 kernel: [    0.507481] ACPI: bus type PNP registered
Jul 26 21:10:01 node-4 kernel: [    0.507590] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 26 21:10:01 node-4 kernel: [    0.507598] pnp 00:01: [dma 4]
Jul 26 21:10:01 node-4 kernel: [    0.507610] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 26 21:10:01 node-4 kernel: [    0.507638] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 26 21:10:01 node-4 kernel: [    0.507658] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 26 21:10:01 node-4 kernel: [    0.507676] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 26 21:10:01 node-4 kernel: [    0.507710] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 26 21:10:01 node-4 kernel: [    0.507761] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 26 21:10:01 node-4 kernel: [    0.507763] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 26 21:10:01 node-4 kernel: [    0.507765] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 26 21:10:01 node-4 kernel: [    0.507767] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 26 21:10:01 node-4 kernel: [    0.507768] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 26 21:10:01 node-4 kernel: [    0.507772] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 26 21:10:01 node-4 kernel: [    0.507775] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 26 21:10:01 node-4 kernel: [    0.507776] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 26 21:10:01 node-4 kernel: [    0.507778] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 26 21:10:01 node-4 kernel: [    0.507780] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 26 21:10:01 node-4 kernel: [    0.507781] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 26 21:10:01 node-4 kernel: [    0.507782] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 26 21:10:01 node-4 kernel: [    0.507784] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 26 21:10:01 node-4 kernel: [    0.507786] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 26 21:10:01 node-4 kernel: [    0.507870] pnp 00:07: [dma 0 disabled]
Jul 26 21:10:01 node-4 kernel: [    0.507898] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 26 21:10:01 node-4 kernel: [    0.507973] pnp 00:08: [dma 0 disabled]
Jul 26 21:10:01 node-4 kernel: [    0.508004] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 26 21:10:01 node-4 kernel: [    0.508055] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 26 21:10:01 node-4 kernel: [    0.508402] pnp: PnP ACPI: found 10 devices
Jul 26 21:10:01 node-4 kernel: [    0.508404] ACPI: bus type PNP unregistered
Jul 26 21:10:01 node-4 kernel: [    0.514835] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 26 21:10:01 node-4 kernel: [    0.514838] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 26 21:10:01 node-4 kernel: [    0.514841] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 26 21:10:01 node-4 kernel: [    0.514845] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 26 21:10:01 node-4 kernel: [    0.514847] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:01 node-4 kernel: [    0.514862] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 26 21:10:01 node-4 kernel: [    0.514891] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 26 21:10:01 node-4 kernel: [    0.514905] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 26 21:10:01 node-4 kernel: [    0.514934] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 26 21:10:01 node-4 kernel: [    0.514948] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 26 21:10:01 node-4 kernel: [    0.514977] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 26 21:10:01 node-4 kernel: [    0.514992] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 26 21:10:01 node-4 kernel: [    0.515021] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 26 21:10:01 node-4 kernel: [    0.515022] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:01 node-4 kernel: [    0.515037] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 21:10:01 node-4 kernel: [    0.515066] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 26 21:10:01 node-4 kernel: [    0.515068] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:01 node-4 kernel: [    0.515082] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 21:10:01 node-4 kernel: [    0.515114] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 26 21:10:01 node-4 kernel: [    0.515115] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:01 node-4 kernel: [    0.515118] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 21:10:01 node-4 kernel: [    0.515122] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 26 21:10:01 node-4 kernel: [    0.515124] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 26 21:10:01 node-4 kernel: [    0.515126] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 21:10:01 node-4 kernel: [    0.515130] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 26 21:10:01 node-4 kernel: [    0.515135] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 26 21:10:01 node-4 kernel: [    0.515143] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 26 21:10:01 node-4 kernel: [    0.515146] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 26 21:10:01 node-4 kernel: [    0.515152] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 26 21:10:01 node-4 kernel: [    0.515153] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 26 21:10:01 node-4 kernel: [    0.515154] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 26 21:10:01 node-4 kernel: [    0.515155] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 26 21:10:01 node-4 kernel: [    0.515156] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 26 21:10:01 node-4 kernel: [    0.515157] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 26 21:10:01 node-4 kernel: [    0.515158] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 26 21:10:01 node-4 kernel: [    0.515159] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 26 21:10:01 node-4 kernel: [    0.515160] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 26 21:10:01 node-4 kernel: [    0.515160] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 26 21:10:01 node-4 kernel: [    0.515161] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 26 21:10:01 node-4 kernel: [    0.515162] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 26 21:10:01 node-4 kernel: [    0.515163] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 26 21:10:01 node-4 kernel: [    0.515164] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 26 21:10:01 node-4 kernel: [    0.515165] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 26 21:10:01 node-4 kernel: [    0.515166] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 26 21:10:01 node-4 kernel: [    0.515167] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 26 21:10:01 node-4 kernel: [    0.515167] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 26 21:10:01 node-4 kernel: [    0.515168] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 26 21:10:01 node-4 kernel: [    0.515169] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 26 21:10:01 node-4 kernel: [    0.515170] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 26 21:10:01 node-4 kernel: [    0.515171] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 26 21:10:01 node-4 kernel: [    0.515173] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 26 21:10:01 node-4 kernel: [    0.515174] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 26 21:10:01 node-4 kernel: [    0.515212] NET: Registered protocol family 2
Jul 26 21:10:01 node-4 kernel: [    0.515477] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 26 21:10:01 node-4 kernel: [    0.515808] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 26 21:10:01 node-4 kernel: [    0.515955] TCP: Hash tables configured (established 262144 bind 65536)
Jul 26 21:10:01 node-4 kernel: [    0.515993] TCP: reno registered
Jul 26 21:10:01 node-4 kernel: [    0.516021] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 26 21:10:01 node-4 kernel: [    0.516118] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 26 21:10:01 node-4 kernel: [    0.516265] NET: Registered protocol family 1
Jul 26 21:10:01 node-4 kernel: [    0.551575] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 26 21:10:01 node-4 kernel: [    0.551589] PCI: CLS 64 bytes, default 64
Jul 26 21:10:01 node-4 kernel: [    0.551665] Trying to unpack rootfs image as initramfs...
Jul 26 21:10:01 node-4 kernel: [    0.771000] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 26 21:10:01 node-4 kernel: [    0.771054] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 26 21:10:01 node-4 kernel: [    0.771057] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 26 21:10:01 node-4 kernel: [    0.771509] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:01 node-4 kernel: [    0.771515] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:01 node-4 kernel: [    0.771520] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:01 node-4 kernel: [    0.771525] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:01 node-4 kernel: [    0.771537] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:01 node-4 kernel: [    0.771554] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:01 node-4 kernel: [    0.771570] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:01 node-4 kernel: [    0.771585] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:01 node-4 kernel: [    0.771596] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:01 node-4 kernel: [    0.771606] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:01 node-4 kernel: [    0.771613] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:01 node-4 kernel: [    0.771619] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:01 node-4 kernel: [    0.771627] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:01 node-4 kernel: [    0.771640] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:01 node-4 kernel: [    0.771653] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:01 node-4 kernel: [    0.771665] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 21:10:01 node-4 kernel: [    0.771773] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 26 21:10:01 node-4 kernel: [    0.771779] Scanning for low memory corruption every 60 seconds
Jul 26 21:10:01 node-4 kernel: [    0.772202] Initialise system trusted keyring
Jul 26 21:10:01 node-4 kernel: [    0.772255] audit: initializing netlink socket (disabled)
Jul 26 21:10:01 node-4 kernel: [    0.772271] type=2000 audit(1469567364.728:1): initialized
Jul 26 21:10:01 node-4 kernel: [    0.790194] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 26 21:10:01 node-4 kernel: [    0.791738] zbud: loaded
Jul 26 21:10:01 node-4 kernel: [    0.791862] VFS: Disk quotas dquot_6.5.2
Jul 26 21:10:01 node-4 kernel: [    0.791904] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 26 21:10:01 node-4 kernel: [    0.792295] fuse init (API version 7.22)
Jul 26 21:10:01 node-4 kernel: [    0.792357] msgmni has been set to 32768
Jul 26 21:10:01 node-4 kernel: [    0.792405] Key type big_key registered
Jul 26 21:10:01 node-4 kernel: [    0.792881] Key type asymmetric registered
Jul 26 21:10:01 node-4 kernel: [    0.792883] Asymmetric key parser 'x509' registered
Jul 26 21:10:01 node-4 kernel: [    0.792905] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 26 21:10:01 node-4 kernel: [    0.792977] io scheduler noop registered
Jul 26 21:10:01 node-4 kernel: [    0.792979] io scheduler deadline registered (default)
Jul 26 21:10:01 node-4 kernel: [    0.792998] io scheduler cfq registered
Jul 26 21:10:01 node-4 kernel: [    0.793387] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    0.793506] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    0.793619] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    0.793726] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    0.793866] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    0.793957] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    0.794370] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 26 21:10:01 node-4 kernel: [    0.794394] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 26 21:10:01 node-4 kernel: [    0.794410] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 26 21:10:01 node-4 kernel: [    0.794419] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794422] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794424] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 26 21:10:01 node-4 kernel: [    0.794429] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794431] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794432] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794433] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794435] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794436] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794438] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794439] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794440] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794442] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794443] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794445] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794447] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 26 21:10:01 node-4 kernel: [    0.794452] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794455] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 26 21:10:01 node-4 kernel: [    0.794470] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794473] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 26 21:10:01 node-4 kernel: [    0.794483] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794485] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 26 21:10:01 node-4 kernel: [    0.794488] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 26 21:10:01 node-4 kernel: [    0.794522] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 26 21:10:01 node-4 kernel: [    0.794528] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 26 21:10:01 node-4 kernel: [    0.794533] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 26 21:10:01 node-4 kernel: [    0.794542] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 26 21:10:01 node-4 kernel: [    0.794585] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 26 21:10:01 node-4 kernel: [    0.794586] vesafb: scrolling: redraw
Jul 26 21:10:01 node-4 kernel: [    0.794587] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 26 21:10:01 node-4 kernel: [    0.815304] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 26 21:10:01 node-4 kernel: [    0.823821] Console: switching to colour frame buffer device 80x30
Jul 26 21:10:01 node-4 kernel: [    0.832490] fb0: VESA VGA frame buffer device
Jul 26 21:10:01 node-4 kernel: [    0.832687] intel_idle: MWAIT substates: 0x2120
Jul 26 21:10:01 node-4 kernel: [    0.832688] intel_idle: v0.4 model 0x3F
Jul 26 21:10:01 node-4 kernel: [    0.832688] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 26 21:10:01 node-4 kernel: [    0.832917] ipmi message handler version 39.2
Jul 26 21:10:01 node-4 kernel: [    0.833190] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 26 21:10:01 node-4 kernel: [    0.833624] ACPI: AC Adapter [P111] (on-line)
Jul 26 21:10:01 node-4 kernel: [    0.838850] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 26 21:10:01 node-4 kernel: [    0.849874] ACPI: Power Button [PWRB]
Jul 26 21:10:01 node-4 kernel: [    0.855635] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 26 21:10:01 node-4 kernel: [    0.867278] ACPI: Power Button [PWRF]
Jul 26 21:10:01 node-4 kernel: [    0.893025] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 26 21:10:01 node-4 kernel: [    0.904703] pstore: Registered erst as persistent store backend
Jul 26 21:10:01 node-4 kernel: [    0.910899] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 26 21:10:01 node-4 kernel: [    0.922870] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 26 21:10:01 node-4 kernel: [    0.949621] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 26 21:10:01 node-4 kernel: [    0.982916] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 26 21:10:01 node-4 kernel: [    0.997007] Linux agpgart interface v0.103
Jul 26 21:10:01 node-4 kernel: [    1.004641] brd: module loaded
Jul 26 21:10:01 node-4 kernel: [    1.011716] loop: module loaded
Jul 26 21:10:01 node-4 kernel: [    1.018434] libphy: Fixed MDIO Bus: probed
Jul 26 21:10:01 node-4 kernel: [    1.024910] tun: Universal TUN/TAP device driver, 1.6
Jul 26 21:10:01 node-4 kernel: [    1.031393] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 26 21:10:01 node-4 kernel: [    1.037934] PPP generic driver version 2.4.2
Jul 26 21:10:01 node-4 kernel: [    1.044336] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 26 21:10:01 node-4 kernel: [    1.050788] ehci-pci: EHCI PCI platform driver
Jul 26 21:10:01 node-4 kernel: [    1.057318] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 26 21:10:01 node-4 kernel: [    1.063725] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 26 21:10:01 node-4 kernel: [    1.076260] ehci-pci 0000:00:1a.0: debug port 2
Jul 26 21:10:01 node-4 kernel: [    1.086472] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 26 21:10:01 node-4 kernel: [    1.086492] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 26 21:10:01 node-4 kernel: [    1.102972] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 26 21:10:01 node-4 kernel: [    1.109050] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 26 21:10:01 node-4 kernel: [    1.115234] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 26 21:10:01 node-4 kernel: [    1.127327] usb usb1: Product: EHCI Host Controller
Jul 26 21:10:01 node-4 kernel: [    1.133377] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 26 21:10:01 node-4 kernel: [    1.139566] usb usb1: SerialNumber: 0000:00:1a.0
Jul 26 21:10:01 node-4 kernel: [    1.145604] hub 1-0:1.0: USB hub found
Jul 26 21:10:01 node-4 kernel: [    1.151432] hub 1-0:1.0: 2 ports detected
Jul 26 21:10:01 node-4 kernel: [    1.157251] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 26 21:10:01 node-4 kernel: [    1.162851] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 26 21:10:01 node-4 kernel: [    1.173785] ehci-pci 0000:00:1d.0: debug port 2
Jul 26 21:10:01 node-4 kernel: [    1.183098] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 26 21:10:01 node-4 kernel: [    1.183101] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 26 21:10:01 node-4 kernel: [    1.198890] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 26 21:10:01 node-4 kernel: [    1.204106] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 26 21:10:01 node-4 kernel: [    1.209426] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 26 21:10:01 node-4 kernel: [    1.220044] usb usb2: Product: EHCI Host Controller
Jul 26 21:10:01 node-4 kernel: [    1.225533] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 26 21:10:01 node-4 kernel: [    1.231096] usb usb2: SerialNumber: 0000:00:1d.0
Jul 26 21:10:01 node-4 kernel: [    1.236612] hub 2-0:1.0: USB hub found
Jul 26 21:10:01 node-4 kernel: [    1.241998] hub 2-0:1.0: 2 ports detected
Jul 26 21:10:01 node-4 kernel: [    1.247328] ehci-platform: EHCI generic platform driver
Jul 26 21:10:01 node-4 kernel: [    1.252572] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 26 21:10:01 node-4 kernel: [    1.257890] ohci-pci: OHCI PCI platform driver
Jul 26 21:10:01 node-4 kernel: [    1.263221] ohci-platform: OHCI generic platform driver
Jul 26 21:10:01 node-4 kernel: [    1.268462] uhci_hcd: USB Universal Host Controller Interface driver
Jul 26 21:10:01 node-4 kernel: [    1.273867] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 26 21:10:01 node-4 kernel: [    1.466671] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 26 21:10:01 node-4 kernel: [    1.766476] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 26 21:10:01 node-4 kernel: [    1.782776] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 26 21:10:01 node-4 kernel: [    1.788369] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 26 21:10:01 node-4 kernel: [    1.794046] hub 1-1:1.0: USB hub found
Jul 26 21:10:01 node-4 kernel: [    1.799512] hub 1-1:1.0: 6 ports detected
Jul 26 21:10:01 node-4 kernel: [    1.914313] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 26 21:10:01 node-4 kernel: [    2.312824] i8042: No controller found
Jul 26 21:10:01 node-4 kernel: [    2.318435] mousedev: PS/2 mouse device common for all mice
Jul 26 21:10:01 node-4 kernel: [    2.324176] rtc_cmos 00:02: RTC can wake from S4
Jul 26 21:10:01 node-4 kernel: [    2.326757] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 26 21:10:01 node-4 kernel: [    2.326758] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 26 21:10:01 node-4 kernel: [    2.327268] hub 2-1:1.0: USB hub found
Jul 26 21:10:01 node-4 kernel: [    2.327511] hub 2-1:1.0: 8 ports detected
Jul 26 21:10:01 node-4 kernel: [    2.352561] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 26 21:10:01 node-4 kernel: [    2.358288] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 26 21:10:01 node-4 kernel: [    2.369563] device-mapper: uevent: version 1.0.3
Jul 26 21:10:01 node-4 kernel: [    2.375304] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 26 21:10:01 node-4 kernel: [    2.386648] ledtrig-cpu: registered to indicate activity on CPUs
Jul 26 21:10:01 node-4 kernel: [    2.392590] TCP: cubic registered
Jul 26 21:10:01 node-4 kernel: [    2.398429] NET: Registered protocol family 10
Jul 26 21:10:01 node-4 kernel: [    2.404469] NET: Registered protocol family 17
Jul 26 21:10:01 node-4 kernel: [    2.410209] Key type dns_resolver registered
Jul 26 21:10:01 node-4 kernel: [    2.416224] Loading compiled-in X.509 certificates
Jul 26 21:10:01 node-4 kernel: [    2.422397] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 26 21:10:01 node-4 kernel: [    2.433966] registered taskstats version 1
Jul 26 21:10:01 node-4 kernel: [    2.442020] Key type trusted registered
Jul 26 21:10:01 node-4 kernel: [    2.449624] Key type encrypted registered
Jul 26 21:10:01 node-4 kernel: [    2.455099] AppArmor: AppArmor sha1 policy hashing enabled
Jul 26 21:10:01 node-4 kernel: [    2.460594] IMA: No TPM chip found, activating TPM-bypass!
Jul 26 21:10:01 node-4 kernel: [    2.466659] regulator-dummy: disabling
Jul 26 21:10:01 node-4 kernel: [    2.472138]   Magic number: 8:804:197
Jul 26 21:10:01 node-4 kernel: [    2.477695] acpi device:52: hash matches
Jul 26 21:10:01 node-4 kernel: [    2.483098] acpi PNP0100:00: hash matches
Jul 26 21:10:01 node-4 kernel: [    2.488494] rtc_cmos 00:02: setting system clock to 2016-07-26 21:09:27 UTC (1469567367)
Jul 26 21:10:01 node-4 kernel: [    2.500687] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 26 21:10:01 node-4 kernel: [    2.506187] EDD information not available.
Jul 26 21:10:01 node-4 kernel: [    2.511653] PM: Hibernation image not present or could not be loaded.
Jul 26 21:10:01 node-4 kernel: [    2.512516] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 26 21:10:01 node-4 kernel: [    2.523627] Write protecting the kernel read-only data: 12288k
Jul 26 21:10:01 node-4 kernel: [    2.529868] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 26 21:10:01 node-4 kernel: [    2.542430] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 26 21:10:01 node-4 kernel: [    2.573854] device-mapper: multipath: version 1.6.0 loaded
Jul 26 21:10:01 node-4 kernel: [    2.581478] systemd-udevd[216]: starting version 204
Jul 26 21:10:01 node-4 kernel: [    2.600930] md: linear personality registered for level -1
Jul 26 21:10:01 node-4 kernel: [    2.605843] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 26 21:10:01 node-4 kernel: [    2.621815] md: multipath personality registered for level -4
Jul 26 21:10:01 node-4 kernel: [    2.630024] md: raid0 personality registered for level 0
Jul 26 21:10:01 node-4 kernel: [    2.638059] md: raid1 personality registered for level 1
Jul 26 21:10:01 node-4 kernel: [    2.644372] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 26 21:10:01 node-4 kernel: [    2.650621] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 26 21:10:01 node-4 kernel: [    2.656894] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 26 21:10:01 node-4 kernel: [    2.658150] megasas: FW now in Ready state
Jul 26 21:10:01 node-4 kernel: [    2.658613] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.658693] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.658818] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.658903] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.659045] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.659188] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.659311] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.659451] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.659532] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.659628] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.659750] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.659903] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.659969] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.660141] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.660232] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.660361] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.661057] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 26 21:10:01 node-4 kernel: [    2.688452] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 26 21:10:01 node-4 kernel: [    2.701589] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 26 21:10:01 node-4 kernel: [    2.715380] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 21:10:01 node-4 kernel: [    2.722369] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.722373] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.722377] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.722381] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.722417] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 21:10:01 node-4 kernel: [    2.742740] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 26 21:10:01 node-4 kernel: [    2.745856] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 26 21:10:01 node-4 kernel: [    2.745862] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 26 21:10:01 node-4 kernel: [    2.745870] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 26 21:10:01 node-4 kernel: [    2.745901] usb 2-1.4: Manufacturer: Avocent
Jul 26 21:10:01 node-4 kernel: [    2.745910] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 26 21:10:01 node-4 kernel: [    2.749885] raid6: sse2x1    2052 MB/s
Jul 26 21:10:01 node-4 kernel: [    2.802569] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 26 21:10:01 node-4 kernel: [    2.815748] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 21:10:01 node-4 kernel: [    2.817864] raid6: sse2x2     606 MB/s
Jul 26 21:10:01 node-4 kernel: [    2.885467] raid6: sse2x4    9122 MB/s
Jul 26 21:10:01 node-4 kernel: [    2.957411] raid6: avx2x1   14959 MB/s
Jul 26 21:10:01 node-4 kernel: [    3.029343] raid6: avx2x2   18880 MB/s
Jul 26 21:10:01 node-4 kernel: [    3.101287] raid6: avx2x4   21388 MB/s
Jul 26 21:10:01 node-4 kernel: [    3.107300] raid6: using algorithm avx2x4 (21388 MB/s)
Jul 26 21:10:01 node-4 kernel: [    3.113353] raid6: using avx2x2 recovery algorithm
Jul 26 21:10:01 node-4 kernel: [    3.119273] megasas:IOC Init cmd success
Jul 26 21:10:01 node-4 kernel: [    3.119274] Switched to clocksource tsc
Jul 26 21:10:01 node-4 kernel: [    3.119348] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    3.119389] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    3.119428] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    3.119451] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    3.119555] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 21:10:01 node-4 kernel: [    3.126880] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 26 21:10:01 node-4 kernel: [    3.126882] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 26 21:10:01 node-4 kernel: [    3.126883] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 21:10:01 node-4 kernel: [    3.126968] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    3.127005] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    3.127042] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    3.127077] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    3.127154] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 21:10:01 node-4 kernel: [    3.139284] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 26 21:10:01 node-4 kernel: [    3.139285] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 26 21:10:01 node-4 kernel: [    3.139286] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 21:10:01 node-4 kernel: [    3.139336] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    3.139371] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    3.139404] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    3.139442] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 26 21:10:01 node-4 kernel: [    3.139529] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 21:10:01 node-4 kernel: [    3.141719] megasas: INIT adapter done
Jul 26 21:10:01 node-4 kernel: [    3.182469] hidraw: raw HID events driver (C) Jiri Kosina
Jul 26 21:10:01 node-4 kernel: [    3.217564] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 26 21:10:01 node-4 kernel: [    3.218813] scsi0 : LSI SAS based MegaRAID driver
Jul 26 21:10:01 node-4 kernel: [    3.226369] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 26 21:10:01 node-4 kernel: [    3.229092] xor: automatically using best checksumming function:
Jul 26 21:10:01 node-4 kernel: [    3.260623] usbcore: registered new interface driver usbhid
Jul 26 21:10:01 node-4 kernel: [    3.260624] usbhid: USB HID core driver
Jul 26 21:10:01 node-4 kernel: [    3.265145]    avx       : 36735.000 MB/sec
Jul 26 21:10:01 node-4 kernel: [    3.282513] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Jul 26 21:10:01 node-4 kernel: [    3.290415] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 26 21:10:01 node-4 kernel: [    3.308682] async_tx: api initialized (async)
Jul 26 21:10:01 node-4 kernel: [    3.309723] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Jul 26 21:10:01 node-4 kernel: [    3.311318] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Jul 26 21:10:01 node-4 kernel: [    3.312072] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Jul 26 21:10:01 node-4 kernel: [    3.313622] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Jul 26 21:10:01 node-4 kernel: [    3.315191] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Jul 26 21:10:01 node-4 kernel: [    3.332565] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 26 21:10:01 node-4 kernel: [    3.332934] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 26 21:10:01 node-4 kernel: [    3.333962] sd 0:2:0:0: [sda] Write Protect is off
Jul 26 21:10:01 node-4 kernel: [    3.333966] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 26 21:10:01 node-4 kernel: [    3.334246] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 26 21:10:01 node-4 kernel: [    3.361465]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 26 21:10:01 node-4 kernel: [    3.362920] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 26 21:10:01 node-4 kernel: [    3.442931] md: raid6 personality registered for level 6
Jul 26 21:10:01 node-4 kernel: [    3.450039] md: raid5 personality registered for level 5
Jul 26 21:10:01 node-4 kernel: [    3.456980] md: raid4 personality registered for level 4
Jul 26 21:10:01 node-4 kernel: [    3.466960] md: raid10 personality registered for level 10
Jul 26 21:10:01 node-4 kernel: [    3.523381] multipathd (359): /proc/359/oom_adj is deprecated, please use /proc/359/oom_score_adj instead.
Jul 26 21:10:01 node-4 kernel: [    3.583722] random: lvm urandom read with 35 bits of entropy available
Jul 26 21:10:01 node-4 kernel: [    3.741481] bio: create slab <bio-1> at 1
Jul 26 21:10:01 node-4 kernel: [    4.447497] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 21:10:01 node-4 kernel: [    5.004187] init: plymouth-upstart-bridge main process (548) terminated with status 1
Jul 26 21:10:01 node-4 kernel: [    5.016401] init: plymouth-upstart-bridge main process ended, respawning
Jul 26 21:10:01 node-4 kernel: [    5.126877] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 26 21:10:01 node-4 kernel: [    5.164607] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 26 21:10:01 node-4 kernel: [    5.297378] random: nonblocking pool is initialized
Jul 26 21:10:01 node-4 kernel: [    5.352326] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 26 21:10:01 node-4 kernel: [    5.430166] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 26 21:10:01 node-4 kernel: [    5.476564] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 21:10:01 node-4 kernel: [    5.681548] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 26 21:10:01 node-4 kernel: [    5.716067] XFS (dm-0): Mounting Filesystem
Jul 26 21:10:01 node-4 kernel: [    6.083465] XFS (dm-0): Ending clean mount
Jul 26 21:10:01 node-4 kernel: [    6.138874] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 21:10:01 node-4 kernel: [    6.179807] XFS (dm-1): Mounting Filesystem
Jul 26 21:10:01 node-4 kernel: [    6.273784] XFS (dm-1): Ending clean mount
Jul 26 21:10:01 node-4 kernel: [    8.094925] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 26 21:10:01 node-4 kernel: [    8.123686] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 26 21:10:01 node-4 kernel: [    8.286656] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 26 21:10:01 node-4 kernel: [    8.286661] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 26 21:10:01 node-4 kernel: [    8.286665] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 26 21:10:01 node-4 kernel: [    8.286669] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 26 21:10:01 node-4 kernel: [    8.315980] systemd-udevd[772]: starting version 204
Jul 26 21:10:01 node-4 kernel: [    8.549180] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 26 21:10:01 node-4 kernel: [    8.549186] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 26 21:10:01 node-4 kernel: [    8.549189] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 26 21:10:01 node-4 kernel: [    8.549190] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 26 21:10:01 node-4 kernel: [    8.549204] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 26 21:10:01 node-4 kernel: [    8.574121] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 26 21:10:01 node-4 kernel: [    8.574278] wmi: Mapper loaded
Jul 26 21:10:01 node-4 kernel: [    8.577542] power_meter ACPI000D:00: Found ACPI power meter.
Jul 26 21:10:01 node-4 kernel: [    8.577556] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 26 21:10:01 node-4 kernel: [    8.595559] IPMI System Interface driver.
Jul 26 21:10:01 node-4 kernel: [    8.595606] ipmi_si: probing via ACPI
Jul 26 21:10:01 node-4 kernel: [    8.595629] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 26 21:10:01 node-4 kernel: [    8.595630] ipmi_si: Adding ACPI-specified kcs state machine
Jul 26 21:10:01 node-4 kernel: [    8.595640] ipmi_si: probing via SMBIOS
Jul 26 21:10:01 node-4 kernel: [    8.595642] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 26 21:10:01 node-4 kernel: [    8.595643] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 26 21:10:01 node-4 kernel: [    8.595644] ipmi_si: probing via SPMI
Jul 26 21:10:01 node-4 kernel: [    8.595646] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 26 21:10:01 node-4 kernel: [    8.595646] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 26 21:10:01 node-4 kernel: [    8.595648] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 26 21:10:01 node-4 kernel: [    8.649051] systemd-udevd[808]: renamed network interface eth0 to enp6s0
Jul 26 21:10:01 node-4 kernel: [    8.664931] systemd-udevd[810]: renamed network interface eth2 to enp8s0
Jul 26 21:10:01 node-4 kernel: [    8.688916] systemd-udevd[811]: renamed network interface eth3 to enp9s0
Jul 26 21:10:01 node-4 kernel: [    8.729331] systemd-udevd[809]: renamed network interface eth1 to enp7s0
Jul 26 21:10:01 node-4 kernel: [    8.774743] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 26 21:10:01 node-4 kernel: [    8.774749] ipmi_si 00:09: IPMI kcs interface initialized
Jul 26 21:10:01 node-4 kernel: [    9.019203] type=1400 audit(1469567374.031:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1005 comm="apparmor_parser"
Jul 26 21:10:01 node-4 kernel: [    9.019360] type=1400 audit(1469567374.031:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1005 comm="apparmor_parser"
Jul 26 21:10:01 node-4 kernel: [    9.019489] type=1400 audit(1469567374.031:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1005 comm="apparmor_parser"
Jul 26 21:10:01 node-4 kernel: [    9.022026] type=1400 audit(1469567374.035:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1008 comm="apparmor_parser"
Jul 26 21:10:01 node-4 kernel: [    9.022168] type=1400 audit(1469567374.035:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1008 comm="apparmor_parser"
Jul 26 21:10:01 node-4 kernel: [    9.022289] type=1400 audit(1469567374.035:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1008 comm="apparmor_parser"
Jul 26 21:10:01 node-4 kernel: [    9.045540] type=1400 audit(1469567374.059:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1046 comm="apparmor_parser"
Jul 26 21:10:01 node-4 kernel: [    9.045685] type=1400 audit(1469567374.059:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1046 comm="apparmor_parser"
Jul 26 21:10:01 node-4 kernel: [    9.045807] type=1400 audit(1469567374.059:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1046 comm="apparmor_parser"
Jul 26 21:10:01 node-4 kernel: [    9.060847] type=1400 audit(1469567374.075:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1013 comm="apparmor_parser"
Jul 26 21:10:01 node-4 kernel: [    9.527495] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 26 21:10:01 node-4 kernel: [    9.528348] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 26 21:10:01 node-4 kernel: [    9.740503] enic 0000:06:00.0 enp6s0: Link UP
Jul 26 21:10:01 node-4 kernel: [    9.741530] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 26 21:10:01 node-4 kernel: [    9.741538] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 26 21:10:01 node-4 kernel: [   19.582073] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 26 21:10:02 node-4 failsafe: Failsafe of 120 seconds reached.
Jul 26 21:10:03 node-4 kernel: [   38.701669] init: failsafe main process (8399) killed by TERM signal
Jul 26 21:10:03 node-4 dbus[8445]: [system] AppArmor D-Bus mediation is enabled
Jul 26 21:10:03 node-4 kernel: [   38.879503] audit_printk_skb: 30 callbacks suppressed
Jul 26 21:10:03 node-4 kernel: [   38.879505] type=1400 audit(1469567403.238:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8516 comm="apparmor_parser"
Jul 26 21:10:03 node-4 kernel: [   38.879510] type=1400 audit(1469567403.238:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8516 comm="apparmor_parser"
Jul 26 21:10:03 node-4 kernel: [   38.879513] type=1400 audit(1469567403.238:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8516 comm="apparmor_parser"
Jul 26 21:10:03 node-4 kernel: [   38.879537] type=1400 audit(1469567403.238:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8517 comm="apparmor_parser"
Jul 26 21:10:03 node-4 kernel: [   38.879739] type=1400 audit(1469567403.238:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8516 comm="apparmor_parser"
Jul 26 21:10:03 node-4 kernel: [   38.879741] type=1400 audit(1469567403.238:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8516 comm="apparmor_parser"
Jul 26 21:10:03 node-4 kernel: [   38.879856] type=1400 audit(1469567403.238:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8516 comm="apparmor_parser"
Jul 26 21:10:03 node-4 kernel: [   38.962975] type=1400 audit(1469567403.322:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8519 comm="apparmor_parser"
Jul 26 21:10:03 node-4 anacron[8592]: Anacron 2.3 started on 2016-07-26
Jul 26 21:10:03 node-4 anacron[8592]: Will run job `cron.daily' in 5 min.
Jul 26 21:10:03 node-4 anacron[8592]: Will run job `cron.weekly' in 10 min.
Jul 26 21:10:03 node-4 anacron[8592]: Will run job `cron.monthly' in 15 min.
Jul 26 21:10:03 node-4 anacron[8592]: Jobs will be executed sequentially
Jul 26 21:10:03 node-4 cron[8556]: (CRON) INFO (pidfile fd = 3)
Jul 26 21:10:03 node-4 cron[8605]: (CRON) STARTUP (fork ok)
Jul 26 21:10:03 node-4 multipathd: path checkers start up
Jul 26 21:10:03 node-4 cron[8605]: (CRON) INFO (Running @reboot jobs)
Jul 26 21:10:04 node-4 postfix/master[8737]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 26 21:10:07 node-4 puppet-agent[8921]: Reopening log files
Jul 26 21:10:07 node-4 puppet-agent[8921]: Could not request certificate: Connection refused - connect(2)
Jul 26 21:10:22 node-4 puppet-user[9023]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 26 21:10:22 node-4 puppet-user[9023]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 26 21:10:22 node-4 puppet-user[9023]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 26 21:10:22 node-4 puppet-user[9023]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 26 21:10:22 node-4 puppet-user[9023]: Finished catalog run in 0.60 seconds
Jul 26 21:10:24 node-4 multipathd: uevent trigger error
Jul 26 21:10:24 node-4 puppet-user[9569]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 26 21:10:24 node-4 puppet-user[9569]: Compiled catalog for node-4.domain.tld in environment production in 0.10 seconds
Jul 26 21:10:24 node-4 puppet-user[9569]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 26 21:10:24 node-4 puppet-user[9569]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 26 21:10:24 node-4 puppet-user[9569]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Jul 26 21:10:24 node-4 puppet-user[9569]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 26 21:10:24 node-4 puppet-user[9569]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 26 21:10:24 node-4 puppet-user[9569]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 26 21:10:24 node-4 puppet-user[9569]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 26 21:10:24 node-4 puppet-user[9569]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 26 21:10:24 node-4 puppet-user[9569]: Finished catalog run in 0.06 seconds
Jul 26 21:10:25 node-4 puppet-user[10026]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 26 21:10:25 node-4 puppet-user[10026]: Compiled catalog for node-4.domain.tld in environment production in 0.09 seconds
Jul 26 21:10:26 node-4 puppet-user[10026]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 26 21:10:26 node-4 puppet-user[10026]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 26 21:10:26 node-4 puppet-user[10026]: Finished catalog run in 0.02 seconds
Jul 26 21:10:27 node-4 puppet-user[10484]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 26 21:10:27 node-4 puppet-user[10484]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 26 21:10:27 node-4 puppet-user[10484]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 26 21:10:27 node-4 puppet-user[10484]: Finished catalog run in 0.05 seconds
Jul 26 21:10:29 node-4 puppet-user[10935]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 26 21:10:29 node-4 puppet-user[10935]: Compiled catalog for node-4.domain.tld in environment production in 0.19 seconds
Jul 26 21:10:29 node-4 puppet-user[10935]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 26 21:10:29 node-4 kernel: [   65.259949] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 26 21:10:29 node-4 kernel: [   65.260001] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Jul 26 21:10:29 node-4 puppet-user[10935]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Jul 26 21:10:29 node-4 puppet-user[10935]: Finished catalog run in 0.05 seconds
Jul 26 21:10:31 node-4 puppet-user[11396]: (Scope(Class[main])) MODULAR: sync_time
Jul 26 21:10:31 node-4 puppet-user[11396]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 26 21:10:31 node-4 ntpdate[11806]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 26 21:10:37 node-4 ntpdate[11806]: adjust time server 10.20.0.2 offset 0.347616 sec
Jul 26 21:10:37 node-4 puppet-user[11396]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 26 21:10:37 node-4 puppet-user[11396]: Finished catalog run in 6.18 seconds
Jul 26 21:10:43 node-4 puppet-user[12188]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 26 21:10:43 node-4 puppet-user[12188]: Compiled catalog for node-4.domain.tld in environment production in 0.08 seconds
Jul 26 21:10:43 node-4 puppet-user[12188]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 26 21:10:43 node-4 puppet-user[12188]: Finished catalog run in 0.06 seconds
Jul 26 21:10:44 node-4 puppet-user[12636]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 26 21:10:45 node-4 puppet-user[12636]: Compiled catalog for node-4.domain.tld in environment production in 0.95 seconds
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 26 21:10:46 node-4 kernel: [   81.948597] init: plymouth-upstart-bridge main process ended, respawning
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 26 21:10:46 node-4 puppet-user[12636]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 26 21:10:46 node-4 puppet-agent[8921]: Could not run: SIGTERM
Jul 26 21:10:46 node-4 kernel: [   82.222588] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 26 21:10:46 node-4 ec2: 
Jul 26 21:10:46 node-4 ec2: #############################################################
Jul 26 21:10:46 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 26 21:10:46 node-4 ec2: 1024 cc:55:ac:2f:3c:50:3a:3d:e9:1d:42:72:e9:61:e9:f9  root@node-4.domain.tld (DSA)
Jul 26 21:10:46 node-4 ec2: 256 45:b7:d1:70:f4:7a:78:c4:dd:94:1a:d3:71:49:f0:51  root@node-4.domain.tld (ECDSA)
Jul 26 21:10:46 node-4 ec2: 256 ed:bc:bf:18:f2:68:eb:4b:68:55:94:e0:36:b4:22:58  root@node-4.domain.tld (ED25519)
Jul 26 21:10:46 node-4 ec2: 2048 af:b7:e3:5b:6b:59:fb:22:2a:f9:b1:71:17:c2:b7:46  root@node-4.domain.tld (RSA)
Jul 26 21:10:46 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 26 21:10:46 node-4 ec2: #############################################################
Jul 26 21:11:01 node-4 CRON[13780]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 26 21:11:04 node-4 puppet-user[12636]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 26 21:11:04 node-4 puppet-user[12636]: Finished catalog run in 18.10 seconds
Jul 26 21:11:06 node-4 puppet-user[13884]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 26 21:11:06 node-4 puppet-user[13884]: Compiled catalog for node-4.domain.tld in environment production in 0.16 seconds
Jul 26 21:11:10 node-4 puppet-user[13884]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 26 21:11:14 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 21:11:14 node-4 nailgun-agent: I, [2016-07-26T21:11:14.791519 #13783]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 26 21:11:27 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 21:11:27 node-4 nailgun-agent: I, [2016-07-26T21:11:27.874716 #13783]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 26 21:11:41 node-4 puppet-user[13884]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 26 21:11:42 node-4 puppet-user[13884]: Finished catalog run in 35.67 seconds
Jul 26 21:11:43 node-4 puppet-user[16617]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 26 21:11:44 node-4 puppet-user[16617]: Compiled catalog for node-4.domain.tld in environment production in 0.59 seconds
Jul 26 21:11:44 node-4 puppet-user[16617]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 26 21:11:44 node-4 puppet-user[16617]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 26 21:11:44 node-4 puppet-user[16617]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 26 21:11:44 node-4 puppet-user[16617]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 26 21:11:44 node-4 puppet-user[16617]: Finished catalog run in 0.10 seconds
Jul 26 21:11:46 node-4 puppet-user[17080]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 26 21:11:47 node-4 puppet-user[17080]: Compiled catalog for node-4.domain.tld in environment production in 0.89 seconds
Jul 26 21:11:47 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 26 21:11:47 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 26 21:11:47 node-4 crontab[17521]: (root) LIST (root)
Jul 26 21:11:47 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 26 21:11:47 node-4 crontab[17522]: (root) REPLACE (root)
Jul 26 21:11:49 node-4 puppet-user[17080]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 26 21:11:51 node-4 puppet-user[17080]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 26 21:11:52 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8372" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 21:11:52 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 26 21:11:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:11:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:11:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:11:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:11:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:11:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:12:13 node-4 multipathd: uevent trigger error
<27>Jul 26 21:12:13 node-4 multipathd: uevent trigger error
<27>Jul 26 21:12:13 node-4 multipathd: uevent trigger error
<27>Jul 26 21:12:13 node-4 multipathd: uevent trigger error
<27>Jul 26 21:12:16 node-4 multipathd: uevent trigger error
<27>Jul 26 21:12:16 node-4 multipathd: uevent trigger error
<27>Jul 26 21:12:16 node-4 multipathd: uevent trigger error
<27>Jul 26 21:12:16 node-4 multipathd: uevent trigger error
<27>Jul 26 21:12:16 node-4 multipathd: uevent trigger error
<27>Jul 26 21:13:15 node-4 ntpdate[29090]: no servers can be used, exiting
<27>Jul 26 21:13:48 node-4 multipathd: uevent trigger error
<27>Jul 26 21:13:48 node-4 multipathd: uevent trigger error
<27>Jul 26 21:13:48 node-4 multipathd: uevent trigger error
<27>Jul 26 21:13:48 node-4 multipathd: uevent trigger error
<27>Jul 26 21:13:48 node-4 multipathd: uevent trigger error
<27>Jul 26 21:13:48 node-4 multipathd: uevent trigger error
<27>Jul 26 21:13:52 node-4 multipathd: uevent trigger error
<27>Jul 26 21:13:52 node-4 multipathd: uevent trigger error
<27>Jul 26 21:13:52 node-4 multipathd: uevent trigger error
<27>Jul 26 21:13:52 node-4 multipathd: uevent trigger error
<27>Jul 26 21:13:52 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:04 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:04 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:04 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:04 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:07 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:07 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:07 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:07 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:07 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:13 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:13 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:13 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:13 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:13 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:31 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:31 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:31 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:31 node-4 multipathd: uevent trigger error
<27>Jul 26 21:14:32 node-4 multipathd: uevent trigger error
<43>Jul 26 21:14:32 node-4 apache2_error [Tue Jul 26 21:14:25.571532 2016] [mpm_event:notice] [pid 6609:tid 139874298427264] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 26 21:14:32 node-4 apache2_error [Tue Jul 26 21:14:25.577029 2016] [core:notice] [pid 6609:tid 139874298427264] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 26 21:14:32 node-4 apache2_error [Tue Jul 26 21:14:27.541726 2016] [mpm_event:notice] [pid 6609:tid 139874298427264] AH00491: caught SIGTERM, shutting down
<43>Jul 26 21:14:32 node-4 apache2_error [Tue Jul 26 21:14:28.622744 2016] [mpm_worker:notice] [pid 6887:tid 139889781270400] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 26 21:14:32 node-4 apache2_error [Tue Jul 26 21:14:28.622782 2016] [core:notice] [pid 6887:tid 139889781270400] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 21:15:08 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:08 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:08 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:08 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:08 node-4 multipathd: uevent trigger error
<43>Jul 26 21:15:12 node-4 apache2_error [Tue Jul 26 21:15:05.103098 2016] [mpm_worker:notice] [pid 6887:tid 139889781270400] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 21:15:12 node-4 apache2_error [Tue Jul 26 21:15:05.109509 2016] [mpm_worker:warn] [pid 6887:tid 139889781270400] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 21:15:12 node-4 apache2_error [Tue Jul 26 21:15:05.110769 2016] [mpm_worker:notice] [pid 6887:tid 139889781270400] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 26 21:15:12 node-4 apache2_error [Tue Jul 26 21:15:05.110787 2016] [core:notice] [pid 6887:tid 139889781270400] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 21:15:43 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 26 21:15:48 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:48 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:48 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:48 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:48 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:52 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:52 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:52 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:52 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:52 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:58 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:58 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:58 node-4 multipathd: uevent trigger error
<27>Jul 26 21:15:58 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:06 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:06 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:06 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:06 node-4 multipathd: uevent trigger error
<129>Jul 26 21:16:09 node-4 haproxy[19557]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 26 21:16:11 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:11 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:11 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:11 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:11 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:11 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:14 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:14 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:14 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:14 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:14 node-4 multipathd: uevent trigger error
<129>Jul 26 21:16:17 node-4 haproxy[21715]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:18 node-4 haproxy[21719]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 26 21:16:20 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:20 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:20 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:20 node-4 multipathd: uevent trigger error
<129>Jul 26 21:16:22 node-4 haproxy[23010]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:23 node-4 haproxy[23014]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:24 node-4 haproxy[23014]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 26 21:16:25 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:25 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:25 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:25 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:25 node-4 multipathd: uevent trigger error
<129>Jul 26 21:16:27 node-4 haproxy[24152]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:28 node-4 haproxy[24156]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:28 node-4 haproxy[24156]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:28 node-4 haproxy[24156]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:29 node-4 haproxy[24156]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 26 21:16:30 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:30 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:30 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:30 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:30 node-4 multipathd: uevent trigger error
<129>Jul 26 21:16:32 node-4 haproxy[25271]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:33 node-4 haproxy[25275]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:33 node-4 haproxy[25275]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:33 node-4 haproxy[25275]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:34 node-4 haproxy[25275]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:34 node-4 haproxy[25275]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 26 21:16:35 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:35 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:35 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:35 node-4 multipathd: uevent trigger error
<129>Jul 26 21:16:36 node-4 haproxy[25275]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:36 node-4 haproxy[25275]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:36 node-4 haproxy[25275]: proxy aodh has no server available!
<129>Jul 26 21:16:38 node-4 haproxy[26587]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:38 node-4 haproxy[26587]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:38 node-4 haproxy[26587]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:38 node-4 haproxy[26587]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:39 node-4 haproxy[26587]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:39 node-4 haproxy[26587]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:39 node-4 haproxy[26587]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 26 21:16:41 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:41 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:41 node-4 multipathd: uevent trigger error
<129>Jul 26 21:16:41 node-4 haproxy[26587]: 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.
<27>Jul 26 21:16:41 node-4 multipathd: uevent trigger error
<129>Jul 26 21:16:41 node-4 haproxy[26587]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:41 node-4 haproxy[26587]: proxy aodh has no server available!
<129>Jul 26 21:16:41 node-4 haproxy[26587]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:41 node-4 haproxy[26587]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:41 node-4 haproxy[26587]: proxy ceilometer has no server available!
<129>Jul 26 21:16:43 node-4 haproxy[27705]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:44 node-4 haproxy[27709]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:44 node-4 haproxy[27709]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:44 node-4 haproxy[27709]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:44 node-4 haproxy[27709]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:45 node-4 haproxy[27709]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:45 node-4 haproxy[27709]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 26 21:16:46 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:46 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:46 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:46 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:46 node-4 multipathd: uevent trigger error
<129>Jul 26 21:16:46 node-4 haproxy[27709]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:47 node-4 haproxy[27709]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:47 node-4 haproxy[27709]: proxy aodh has no server available!
<129>Jul 26 21:16:47 node-4 haproxy[27709]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:47 node-4 haproxy[27709]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:47 node-4 haproxy[27709]: proxy ceilometer has no server available!
<129>Jul 26 21:16:49 node-4 haproxy[28828]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:49 node-4 haproxy[28828]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:49 node-4 haproxy[28828]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:49 node-4 haproxy[28828]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:50 node-4 haproxy[28828]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:50 node-4 haproxy[28828]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:50 node-4 haproxy[28828]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:50 node-4 haproxy[28828]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:50 node-4 haproxy[28828]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 26 21:16:51 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:51 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:51 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:51 node-4 multipathd: uevent trigger error
<129>Jul 26 21:16:52 node-4 haproxy[28828]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:52 node-4 haproxy[28828]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:52 node-4 haproxy[28828]: proxy aodh has no server available!
<129>Jul 26 21:16:52 node-4 haproxy[28828]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:52 node-4 haproxy[28828]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:52 node-4 haproxy[28828]: proxy ceilometer has no server available!
<129>Jul 26 21:16:54 node-4 haproxy[29994]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:54 node-4 haproxy[29994]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:54 node-4 haproxy[29994]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:55 node-4 haproxy[29998]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:55 node-4 haproxy[29998]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:55 node-4 haproxy[29998]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:55 node-4 haproxy[29998]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:55 node-4 haproxy[29998]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:55 node-4 haproxy[29998]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:56 node-4 haproxy[29998]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:56 node-4 haproxy[29998]: 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>Jul 26 21:16:56 node-4 haproxy[29998]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:57 node-4 haproxy[29998]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:57 node-4 haproxy[29998]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:57 node-4 haproxy[29998]: proxy glance-registry has no server available!
<129>Jul 26 21:16:57 node-4 haproxy[29998]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:57 node-4 haproxy[29998]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:57 node-4 haproxy[29998]: proxy aodh has no server available!
<129>Jul 26 21:16:57 node-4 haproxy[29998]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:16:58 node-4 haproxy[29998]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:16:58 node-4 haproxy[29998]: proxy ceilometer has no server available!
<27>Jul 26 21:16:58 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:58 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:58 node-4 multipathd: uevent trigger error
<27>Jul 26 21:16:58 node-4 multipathd: uevent trigger error
<129>Jul 26 21:17:01 node-4 haproxy[31134]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:01 node-4 haproxy[31134]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:01 node-4 haproxy[31134]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:01 node-4 haproxy[31134]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:01 node-4 haproxy[31134]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:01 node-4 haproxy[31134]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:02 node-4 haproxy[31134]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:02 node-4 haproxy[31134]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:02 node-4 haproxy[31134]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:02 node-4 haproxy[31134]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:02 node-4 haproxy[31134]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:02 node-4 haproxy[31134]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:02 node-4 haproxy[31134]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:03 node-4 haproxy[31134]: 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>Jul 26 21:17:03 node-4 haproxy[31134]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 26 21:17:03 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:03 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:04 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:04 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:04 node-4 multipathd: uevent trigger error
<129>Jul 26 21:17:04 node-4 haproxy[31134]: 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>Jul 26 21:17:04 node-4 haproxy[31134]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:04 node-4 haproxy[31134]: proxy glance-registry has no server available!
<129>Jul 26 21:17:04 node-4 haproxy[31134]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:04 node-4 haproxy[31134]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:04 node-4 haproxy[31134]: proxy aodh has no server available!
<129>Jul 26 21:17:04 node-4 haproxy[31134]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:04 node-4 haproxy[31134]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:04 node-4 haproxy[31134]: proxy ceilometer has no server available!
<129>Jul 26 21:17:04 node-4 haproxy[31134]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:04 node-4 haproxy[31134]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:04 node-4 haproxy[31134]: proxy nova-novncproxy has no server available!
<129>Jul 26 21:17:06 node-4 haproxy[32309]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:06 node-4 haproxy[32309]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:06 node-4 haproxy[32309]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:06 node-4 haproxy[32309]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:06 node-4 haproxy[32309]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:07 node-4 haproxy[32313]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:07 node-4 haproxy[32313]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:07 node-4 haproxy[32313]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:07 node-4 haproxy[32313]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:07 node-4 haproxy[32313]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:07 node-4 haproxy[32313]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:07 node-4 haproxy[32313]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:08 node-4 haproxy[32313]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:08 node-4 haproxy[32313]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:08 node-4 haproxy[32313]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:08 node-4 haproxy[32313]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 26 21:17:09 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:09 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:09 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:09 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:09 node-4 multipathd: uevent trigger error
<129>Jul 26 21:17:09 node-4 haproxy[32313]: 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>Jul 26 21:17:09 node-4 haproxy[32313]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:09 node-4 haproxy[32313]: proxy glance-registry has no server available!
<129>Jul 26 21:17:09 node-4 haproxy[32313]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:09 node-4 haproxy[32313]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:09 node-4 haproxy[32313]: proxy aodh has no server available!
<129>Jul 26 21:17:09 node-4 haproxy[32313]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:09 node-4 haproxy[32313]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:09 node-4 haproxy[32313]: proxy ceilometer has no server available!
<129>Jul 26 21:17:10 node-4 haproxy[32313]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:10 node-4 haproxy[32313]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:10 node-4 haproxy[32313]: proxy nova-novncproxy has no server available!
<129>Jul 26 21:17:12 node-4 haproxy[1104]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:12 node-4 haproxy[1104]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:12 node-4 haproxy[1104]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:12 node-4 haproxy[1104]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:12 node-4 haproxy[1104]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:12 node-4 haproxy[1104]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:12 node-4 haproxy[1104]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:12 node-4 haproxy[1104]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:12 node-4 haproxy[1104]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:13 node-4 haproxy[1104]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:13 node-4 haproxy[1104]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:13 node-4 haproxy[1104]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:13 node-4 haproxy[1104]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:13 node-4 haproxy[1104]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:13 node-4 haproxy[1104]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:13 node-4 haproxy[1104]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:13 node-4 haproxy[1104]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:13 node-4 haproxy[1104]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:13 node-4 haproxy[1104]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 26 21:17:14 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:14 node-4 multipathd: uevent trigger error
<129>Jul 26 21:17:14 node-4 haproxy[1104]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 26 21:17:14 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:14 node-4 multipathd: uevent trigger error
<129>Jul 26 21:17:14 node-4 haproxy[1104]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:14 node-4 haproxy[1104]: proxy glance-registry has no server available!
<27>Jul 26 21:17:14 node-4 multipathd: uevent trigger error
<129>Jul 26 21:17:15 node-4 haproxy[1104]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:15 node-4 haproxy[1104]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:15 node-4 haproxy[1104]: proxy aodh has no server available!
<129>Jul 26 21:17:15 node-4 haproxy[1104]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:15 node-4 haproxy[1104]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:15 node-4 haproxy[1104]: proxy ceilometer has no server available!
<129>Jul 26 21:17:15 node-4 haproxy[1104]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:15 node-4 haproxy[1104]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:15 node-4 haproxy[1104]: proxy nova-novncproxy has no server available!
<27>Jul 26 21:17:15 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 26 21:17:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:21 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:21 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:21 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:21 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:21 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:21 node-4 multipathd: uevent trigger error
<129>Jul 26 21:17:22 node-4 haproxy[1104]: Server keystone-1/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:22 node-4 haproxy[1104]: Server keystone-1/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:22 node-4 haproxy[1104]: proxy keystone-1 has no server available!
<129>Jul 26 21:17:22 node-4 haproxy[1104]: 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>Jul 26 21:17:22 node-4 haproxy[1104]: Server keystone-2/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:22 node-4 haproxy[1104]: proxy keystone-2 has no server available!
<129>Jul 26 21:17:22 node-4 haproxy[1104]: 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>Jul 26 21:17:22 node-4 haproxy[1104]: Server nova-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:22 node-4 haproxy[1104]: proxy nova-api has no server available!
<129>Jul 26 21:17:22 node-4 haproxy[1104]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:22 node-4 haproxy[1104]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:22 node-4 haproxy[1104]: proxy nova-metadata-api has no server available!
<129>Jul 26 21:17:22 node-4 haproxy[1104]: Server cinder-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:22 node-4 haproxy[1104]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:22 node-4 haproxy[1104]: proxy cinder-api has no server available!
<129>Jul 26 21:17:22 node-4 haproxy[1104]: Server glance-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:22 node-4 haproxy[1104]: Server glance-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:22 node-4 haproxy[1104]: proxy glance-api has no server available!
<129>Jul 26 21:17:22 node-4 haproxy[1104]: Server glance-glare/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:22 node-4 haproxy[1104]: Server glance-glare/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:22 node-4 haproxy[1104]: proxy glance-glare has no server available!
<129>Jul 26 21:17:22 node-4 haproxy[1104]: Server neutron/node-1 is DOWN, reason: Layer4 timeout, check duration: 10002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:22 node-4 haproxy[1104]: Server neutron/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:22 node-4 haproxy[1104]: proxy neutron has no server available!
<129>Jul 26 21:17:23 node-4 haproxy[1104]: Server mysqld/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:23 node-4 haproxy[1104]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:23 node-4 haproxy[1104]: proxy mysqld has no server available!
<129>Jul 26 21:17:23 node-4 haproxy[1104]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:23 node-4 haproxy[1104]: Server object-storage/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:23 node-4 haproxy[1104]: proxy object-storage has no server available!
<129>Jul 26 21:17:23 node-4 haproxy[1104]: 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>Jul 26 21:17:23 node-4 haproxy[1104]: Server heat-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:23 node-4 haproxy[1104]: proxy heat-api has no server available!
<129>Jul 26 21:17:23 node-4 haproxy[1104]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:23 node-4 haproxy[1104]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:23 node-4 haproxy[1104]: proxy heat-api-cfn has no server available!
<129>Jul 26 21:17:23 node-4 haproxy[1104]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 21:17:23 node-4 haproxy[1104]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 26 21:17:23 node-4 haproxy[1104]: proxy heat-api-cloudwatch has no server available!
<27>Jul 26 21:17:25 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:25 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:25 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:25 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:25 node-4 multipathd: uevent trigger error
<27>Jul 26 21:17:44 node-4 multipathd: uevent trigger error
<27>Jul 26 21:18:13 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 26 21:18:13 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 26 21:18:41 node-4 multipathd: uevent trigger error
<27>Jul 26 21:18:41 node-4 multipathd: uevent trigger error
<27>Jul 26 21:18:41 node-4 multipathd: uevent trigger error
<27>Jul 26 21:18:41 node-4 multipathd: uevent trigger error
<27>Jul 26 21:18:54 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 26 21:19:49 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 26 21:19:51 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 26 21:21:05 node-4 multipathd: uevent trigger error
<27>Jul 26 21:21:05 node-4 multipathd: uevent trigger error
<27>Jul 26 21:21:05 node-4 multipathd: uevent trigger error
<27>Jul 26 21:21:05 node-4 multipathd: uevent trigger error
<27>Jul 26 21:21:05 node-4 multipathd: uevent trigger error
<27>Jul 26 21:21:05 node-4 multipathd: uevent trigger error
<11>Jul 26 21:24:09 node-4 epmd: epmd: node name already occupied rabbitmq-cli-57
<27>Jul 26 21:24:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:24:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:24:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:24:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:24:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:24:18 node-4 multipathd: uevent trigger error
<11>Jul 26 21:25:03 node-4 epmd: epmd: node name already occupied rabbitmq-cli-57
<43>Jul 26 21:25:33 node-4 apache2_error [Tue Jul 26 21:25:26.982052 2016] [mpm_worker:notice] [pid 6887:tid 139889781270400] AH00295: caught SIGTERM, shutting down
<43>Jul 26 21:25:33 node-4 apache2_error [Tue Jul 26 21:25:27.729614 2016] [mpm_worker:notice] [pid 4715:tid 140390437054336] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 21:25:33 node-4 apache2_error [Tue Jul 26 21:25:27.729673 2016] [core:notice] [pid 4715:tid 140390437054336] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 26 21:26:03 node-4 apache2_error [Tue Jul 26 21:25:59.759639 2016] [mpm_worker:notice] [pid 4715:tid 140390437054336] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 21:26:03 node-4 apache2_error [Tue Jul 26 21:25:59.772475 2016] [mpm_worker:warn] [pid 4715:tid 140390437054336] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 21:26:03 node-4 apache2_error [Tue Jul 26 21:25:59.777819 2016] [mpm_worker:notice] [pid 4715:tid 140390437054336] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 21:26:03 node-4 apache2_error [Tue Jul 26 21:25:59.777846 2016] [core:notice] [pid 4715:tid 140390437054336] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 21:26:05 node-4 multipathd: uevent trigger error
<27>Jul 26 21:26:05 node-4 multipathd: uevent trigger error
<27>Jul 26 21:26:05 node-4 multipathd: uevent trigger error
<27>Jul 26 21:26:05 node-4 multipathd: uevent trigger error
<27>Jul 26 21:26:05 node-4 multipathd: uevent trigger error
<27>Jul 26 21:27:02 node-4 multipathd: uevent trigger error
<27>Jul 26 21:27:02 node-4 multipathd: uevent trigger error
<27>Jul 26 21:27:02 node-4 multipathd: uevent trigger error
<27>Jul 26 21:27:02 node-4 multipathd: uevent trigger error
<27>Jul 26 21:27:02 node-4 multipathd: uevent trigger error
<27>Jul 26 21:27:02 node-4 multipathd: uevent trigger error
<27>Jul 26 21:27:08 node-4 multipathd: uevent trigger error
<27>Jul 26 21:27:08 node-4 multipathd: uevent trigger error
<27>Jul 26 21:27:08 node-4 multipathd: uevent trigger error
<27>Jul 26 21:27:08 node-4 multipathd: uevent trigger error
<27>Jul 26 21:27:08 node-4 multipathd: uevent trigger error
<11>Jul 26 21:27:41 node-4 epmd: epmd: node name already occupied rabbitmq-cli-57
<27>Jul 26 21:28:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:28:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:28:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:28:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:28:18 node-4 multipathd: uevent trigger error
<11>Jul 26 21:28:58 node-4 epmd: epmd: node name already occupied rabbitmq-cli-57
<11>Jul 26 21:29:37 node-4 epmd: epmd: node name already occupied rabbitmq-cli-57
<11>Jul 26 21:32:51 node-4 epmd: epmd: node name already occupied rabbitmq-cli-57
<27>Jul 26 21:33:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:33:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:33:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:33:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:36:07 node-4 multipathd: uevent trigger error
<27>Jul 26 21:36:07 node-4 multipathd: uevent trigger error
<27>Jul 26 21:36:07 node-4 multipathd: uevent trigger error
<27>Jul 26 21:36:07 node-4 multipathd: uevent trigger error
<27>Jul 26 21:36:07 node-4 multipathd: uevent trigger error
<27>Jul 26 21:36:07 node-4 multipathd: uevent trigger error
<27>Jul 26 21:36:07 node-4 multipathd: uevent trigger error
<11>Jul 26 21:36:50 node-4 epmd: epmd: node name already occupied rabbitmq-cli-57
<27>Jul 26 21:37:14 node-4 multipathd: uevent trigger error
<27>Jul 26 21:37:14 node-4 multipathd: uevent trigger error
<27>Jul 26 21:37:14 node-4 multipathd: uevent trigger error
<27>Jul 26 21:37:14 node-4 multipathd: uevent trigger error
<27>Jul 26 21:37:14 node-4 multipathd: uevent trigger error
<27>Jul 26 21:37:14 node-4 multipathd: uevent trigger error
<27>Jul 26 21:37:14 node-4 multipathd: uevent trigger error
<27>Jul 26 21:37:50 node-4 multipathd: uevent trigger error
<27>Jul 26 21:37:50 node-4 multipathd: uevent trigger error
<27>Jul 26 21:37:50 node-4 multipathd: uevent trigger error
<27>Jul 26 21:37:50 node-4 multipathd: uevent trigger error
<27>Jul 26 21:37:50 node-4 multipathd: uevent trigger error
<27>Jul 26 21:37:50 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:00 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:00 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:00 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:00 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:13 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Jul 26 21:38:13 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Jul 26 21:38:13 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Jul 26 21:38:14 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Jul 26 21:38:14 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Jul 26 21:38:15 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:15 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:15 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:15 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:15 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:33 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:33 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:33 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:33 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:33 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:42 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:42 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:42 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:43 node-4 multipathd: uevent trigger error
<27>Jul 26 21:38:43 node-4 multipathd: uevent trigger error
<43>Jul 26 21:39:34 node-4 apache2_error [Tue Jul 26 21:39:28.701529 2016] [mpm_worker:notice] [pid 4715:tid 140390437054336] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 21:39:34 node-4 apache2_error [Tue Jul 26 21:39:29.087627 2016] [mpm_worker:warn] [pid 4715:tid 140390437054336] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 21:39:34 node-4 apache2_error [Tue Jul 26 21:39:29.092630 2016] [mpm_worker:notice] [pid 4715:tid 140390437054336] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 21:39:34 node-4 apache2_error [Tue Jul 26 21:39:29.092647 2016] [core:notice] [pid 4715:tid 140390437054336] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 21:40:09 node-4 multipathd: uevent trigger error
<27>Jul 26 21:40:09 node-4 multipathd: uevent trigger error
<27>Jul 26 21:40:09 node-4 multipathd: uevent trigger error
<27>Jul 26 21:40:09 node-4 multipathd: uevent trigger error
<27>Jul 26 21:40:09 node-4 multipathd: uevent trigger error
<43>Jul 26 21:40:14 node-4 apache2_error [Tue Jul 26 21:40:05.912821 2016] [mpm_worker:notice] [pid 4715:tid 140390437054336] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 21:40:14 node-4 apache2_error [Tue Jul 26 21:40:06.108488 2016] [mpm_worker:warn] [pid 4715:tid 140390437054336] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 21:40:14 node-4 apache2_error [Tue Jul 26 21:40:06.115781 2016] [mpm_worker:notice] [pid 4715:tid 140390437054336] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 21:40:14 node-4 apache2_error [Tue Jul 26 21:40:06.115802 2016] [core:notice] [pid 4715:tid 140390437054336] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 21:40:50 node-4 multipathd: uevent trigger error
<27>Jul 26 21:40:50 node-4 multipathd: uevent trigger error
<27>Jul 26 21:40:50 node-4 multipathd: uevent trigger error
<27>Jul 26 21:40:50 node-4 multipathd: uevent trigger error
<27>Jul 26 21:40:50 node-4 multipathd: uevent trigger error
<27>Jul 26 21:40:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:40:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:40:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:40:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:41:48 node-4 multipathd: uevent trigger error
<27>Jul 26 21:41:48 node-4 multipathd: uevent trigger error
<27>Jul 26 21:41:48 node-4 multipathd: uevent trigger error
<27>Jul 26 21:41:48 node-4 multipathd: uevent trigger error
<11>Jul 26 21:42:16 node-4 epmd: epmd: node name already occupied rabbitmq-cli-57
<27>Jul 26 21:42:36 node-4 multipathd: uevent trigger error
<27>Jul 26 21:42:36 node-4 multipathd: uevent trigger error
<27>Jul 26 21:42:36 node-4 multipathd: uevent trigger error
<27>Jul 26 21:42:37 node-4 multipathd: uevent trigger error
<27>Jul 26 21:42:37 node-4 multipathd: uevent trigger error
<27>Jul 26 21:42:55 node-4 multipathd: uevent trigger error
<27>Jul 26 21:42:55 node-4 multipathd: uevent trigger error
<27>Jul 26 21:42:55 node-4 multipathd: uevent trigger error
<27>Jul 26 21:42:55 node-4 multipathd: uevent trigger error
<11>Jul 26 21:43:04 node-4 liberasurecode[1505]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:04 node-4 liberasurecode[1505]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:04 node-4 liberasurecode[1505]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:04 node-4 liberasurecode[1505]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:04 node-4 liberasurecode[1530]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:04 node-4 liberasurecode[1530]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:04 node-4 liberasurecode[1530]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:04 node-4 liberasurecode[1530]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:06 node-4 liberasurecode[1943]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:06 node-4 liberasurecode[1943]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:06 node-4 liberasurecode[1943]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:06 node-4 liberasurecode[1943]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4671]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4671]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4671]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4671]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4707]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4707]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4707]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4707]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4779]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4779]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4779]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4779]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4854]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4854]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4854]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4854]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4840]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4840]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4840]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4840]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4866]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4866]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4866]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4866]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4883]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4883]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4883]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:43:12 node-4 liberasurecode[4883]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 26 21:43:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:43:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:43:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:43:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:43:18 node-4 multipathd: uevent trigger error
<27>Jul 26 21:43:23 node-4 multipathd: uevent trigger error
<27>Jul 26 21:43:23 node-4 multipathd: uevent trigger error
<27>Jul 26 21:43:23 node-4 multipathd: uevent trigger error
<27>Jul 26 21:43:23 node-4 multipathd: uevent trigger error
<11>Jul 26 21:44:20 node-4 epmd: epmd: node name already occupied rabbitmq-cli-57
<27>Jul 26 21:44:35 node-4 multipathd: uevent trigger error
<27>Jul 26 21:44:35 node-4 multipathd: uevent trigger error
<27>Jul 26 21:44:35 node-4 multipathd: uevent trigger error
<27>Jul 26 21:44:35 node-4 multipathd: uevent trigger error
<27>Jul 26 21:44:35 node-4 multipathd: uevent trigger error
<11>Jul 26 21:45:02 node-4 liberasurecode[20969]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:45:02 node-4 liberasurecode[20969]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:45:02 node-4 liberasurecode[20969]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:45:02 node-4 liberasurecode[20969]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 26 21:46:36 node-4 multipathd: uevent trigger error
<27>Jul 26 21:46:36 node-4 multipathd: uevent trigger error
<27>Jul 26 21:46:36 node-4 multipathd: uevent trigger error
<27>Jul 26 21:46:36 node-4 multipathd: uevent trigger error
<27>Jul 26 21:46:36 node-4 multipathd: uevent trigger error
<27>Jul 26 21:46:41 node-4 multipathd: uevent trigger error
<27>Jul 26 21:46:41 node-4 multipathd: uevent trigger error
<27>Jul 26 21:46:41 node-4 multipathd: uevent trigger error
<27>Jul 26 21:46:41 node-4 multipathd: uevent trigger error
<27>Jul 26 21:46:41 node-4 multipathd: uevent trigger error
<27>Jul 26 21:46:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:46:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:46:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:46:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:46:54 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:07 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:07 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:07 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:07 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:12 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:12 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:12 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:12 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:12 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:24 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:24 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:24 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:24 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:24 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:29 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:29 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:29 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:29 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:33 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:33 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:33 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:33 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:33 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:38 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:38 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:38 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:38 node-4 multipathd: uevent trigger error
<27>Jul 26 21:47:38 node-4 multipathd: uevent trigger error
<11>Jul 26 21:47:41 node-4 epmd: epmd: node name already occupied rabbitmq-cli-57
<27>Jul 26 21:48:18 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 21:48:18 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<11>Jul 26 21:49:38 node-4 epmd: epmd: node name already occupied rabbitmq-cli-57
<11>Jul 26 21:50:01 node-4 liberasurecode[5690]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:50:01 node-4 liberasurecode[5690]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:50:01 node-4 liberasurecode[5690]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 21:50:01 node-4 liberasurecode[5690]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 21:50:32 node-4 epmd: epmd: node name already occupied rabbitmq-cli-57
