Jul 31 21:48:58 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8365" x-info="http://www.rsyslog.com"] start
Jul 31 21:48:58 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 31 21:48:58 node-5 rsyslogd: rsyslogd's groupid changed to 104
Jul 31 21:48:58 node-5 rsyslogd: rsyslogd's userid changed to 101
Jul 31 21:48:58 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 31 21:48:58 node-5 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 31 21:48:58 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 31 21:48:58 node-5 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 31 21:48:58 node-5 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=f816b2d5-c973-4b12-8097-26e007c56e5c nomdmonddf nomdmonisw
Jul 31 21:48:58 node-5 kernel: [    0.000000] KERNEL supported cpus:
Jul 31 21:48:58 node-5 kernel: [    0.000000]   Intel GenuineIntel
Jul 31 21:48:58 node-5 kernel: [    0.000000]   AMD AuthenticAMD
Jul 31 21:48:58 node-5 kernel: [    0.000000]   Centaur CentaurHauls
Jul 31 21:48:58 node-5 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 31 21:48:58 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 31 21:48:58 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 31 21:48:58 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 31 21:48:58 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Jul 31 21:48:58 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Jul 31 21:48:58 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Jul 31 21:48:58 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Jul 31 21:48:58 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Jul 31 21:48:58 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 31 21:48:58 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 31 21:48:58 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 31 21:48:58 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 31 21:48:58 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 31 21:48:58 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 31 21:48:58 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 31 21:48:58 node-5 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 31 21:48:58 node-5 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 31 21:48:58 node-5 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 31 21:48:58 node-5 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 31 21:48:58 node-5 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 31 21:48:58 node-5 kernel: [    0.000000] No AGP bridge found
Jul 31 21:48:58 node-5 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 31 21:48:58 node-5 kernel: [    0.000000] MTRR default type: write-back
Jul 31 21:48:58 node-5 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 31 21:48:58 node-5 kernel: [    0.000000]   00000-9FFFF write-back
Jul 31 21:48:58 node-5 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 31 21:48:58 node-5 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 31 21:48:58 node-5 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 31 21:48:58 node-5 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 31 21:48:58 node-5 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 31 21:48:58 node-5 kernel: [    0.000000]   2 disabled
Jul 31 21:48:58 node-5 kernel: [    0.000000]   3 disabled
Jul 31 21:48:58 node-5 kernel: [    0.000000]   4 disabled
Jul 31 21:48:58 node-5 kernel: [    0.000000]   5 disabled
Jul 31 21:48:58 node-5 kernel: [    0.000000]   6 disabled
Jul 31 21:48:58 node-5 kernel: [    0.000000]   7 disabled
Jul 31 21:48:58 node-5 kernel: [    0.000000]   8 disabled
Jul 31 21:48:58 node-5 kernel: [    0.000000]   9 disabled
Jul 31 21:48:58 node-5 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 31 21:48:58 node-5 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 31 21:48:58 node-5 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 31 21:48:58 node-5 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 31 21:48:58 node-5 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 31 21:48:58 node-5 kernel: [    0.000000] Using GB pages for direct mapping
Jul 31 21:48:58 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 31 21:48:58 node-5 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 31 21:48:58 node-5 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 31 21:48:58 node-5 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 31 21:48:58 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 31 21:48:58 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 31 21:48:58 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 31 21:48:58 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 31 21:48:58 node-5 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 31 21:48:58 node-5 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Jul 31 21:48:58 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 31 21:48:58 node-5 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 31 21:48:58 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 31 21:48:58 node-5 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 31 21:48:58 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 31 21:48:58 node-5 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 31 21:48:58 node-5 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 31 21:48:58 node-5 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 31 21:48:58 node-5 kernel: [    0.000000] Zone ranges:
Jul 31 21:48:58 node-5 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] Movable zone start for each node
Jul 31 21:48:58 node-5 kernel: [    0.000000] Early memory node ranges
Jul 31 21:48:58 node-5 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 31 21:48:58 node-5 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 31 21:48:58 node-5 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] On node 0 totalpages: 4125855
Jul 31 21:48:58 node-5 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 31 21:48:58 node-5 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 31 21:48:58 node-5 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 31 21:48:58 node-5 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Jul 31 21:48:58 node-5 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Jul 31 21:48:58 node-5 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 31 21:48:58 node-5 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 31 21:48:58 node-5 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 31 21:48:58 node-5 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 31 21:48:58 node-5 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 31 21:48:58 node-5 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 31 21:48:58 node-5 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 31 21:48:58 node-5 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 31 21:48:58 node-5 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 31 21:48:58 node-5 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 31 21:48:58 node-5 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 31 21:48:58 node-5 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 31 21:48:58 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 31 21:48:58 node-5 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 31 21:48:58 node-5 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 31 21:48:58 node-5 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 31 21:48:58 node-5 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 31 21:48:58 node-5 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 31 21:48:58 node-5 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 31 21:48:58 node-5 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Jul 31 21:48:58 node-5 kernel: [    0.000000] Policy zone: Normal
Jul 31 21:48:58 node-5 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=f816b2d5-c973-4b12-8097-26e007c56e5c nomdmonddf nomdmonisw
Jul 31 21:48:58 node-5 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 31 21:48:58 node-5 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 31 21:48:58 node-5 kernel: [    0.000000] Checking aperture...
Jul 31 21:48:58 node-5 kernel: [    0.000000] No AGP bridge found
Jul 31 21:48:58 node-5 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 31 21:48:58 node-5 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 31 21:48:58 node-5 kernel: [    0.000000] Memory: 32653456K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 31 21:48:58 node-5 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 31 21:48:58 node-5 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 31 21:48:58 node-5 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 31 21:48:58 node-5 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 31 21:48:58 node-5 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 31 21:48:58 node-5 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 31 21:48:58 node-5 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 31 21:48:58 node-5 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 31 21:48:58 node-5 kernel: [    0.000000] console [tty0] enabled
Jul 31 21:48:58 node-5 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 31 21:48:58 node-5 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 31 21:48:58 node-5 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 31 21:48:58 node-5 kernel: [    0.000000] hpet clockevent registered
Jul 31 21:48:58 node-5 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 31 21:48:58 node-5 kernel: [    0.004000] tsc: Detected 3492.308 MHz processor
Jul 31 21:48:58 node-5 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.61 BogoMIPS (lpj=13969232)
Jul 31 21:48:58 node-5 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 31 21:48:58 node-5 kernel: [    0.000047] Security Framework initialized
Jul 31 21:48:58 node-5 kernel: [    0.000064] AppArmor: AppArmor initialized
Jul 31 21:48:58 node-5 kernel: [    0.000065] Yama: becoming mindful.
Jul 31 21:48:58 node-5 kernel: [    0.001455] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 31 21:48:58 node-5 kernel: [    0.006386] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 31 21:48:58 node-5 kernel: [    0.008315] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 31 21:48:58 node-5 kernel: [    0.008344] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 31 21:48:58 node-5 kernel: [    0.008632] Initializing cgroup subsys memory
Jul 31 21:48:58 node-5 kernel: [    0.008641] Initializing cgroup subsys devices
Jul 31 21:48:58 node-5 kernel: [    0.008642] Initializing cgroup subsys freezer
Jul 31 21:48:58 node-5 kernel: [    0.008644] Initializing cgroup subsys blkio
Jul 31 21:48:58 node-5 kernel: [    0.008646] Initializing cgroup subsys perf_event
Jul 31 21:48:58 node-5 kernel: [    0.008648] Initializing cgroup subsys hugetlb
Jul 31 21:48:58 node-5 kernel: [    0.008668] CPU: Physical Processor ID: 0
Jul 31 21:48:58 node-5 kernel: [    0.008669] CPU: Processor Core ID: 0
Jul 31 21:48:58 node-5 kernel: [    0.008673] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 31 21:48:58 node-5 kernel: [    0.008673] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 31 21:48:58 node-5 kernel: [    0.009367] mce: CPU supports 22 MCE banks
Jul 31 21:48:58 node-5 kernel: [    0.009394] CPU0: Thermal monitoring enabled (TM1)
Jul 31 21:48:58 node-5 kernel: [    0.009415] process: using mwait in idle threads
Jul 31 21:48:58 node-5 kernel: [    0.009418] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 31 21:48:58 node-5 kernel: [    0.009418] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 31 21:48:58 node-5 kernel: [    0.009418] tlb_flushall_shift: 6
Jul 31 21:48:58 node-5 kernel: [    0.009507] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 31 21:48:58 node-5 kernel: [    0.010229] ACPI: Core revision 20131115
Jul 31 21:48:58 node-5 kernel: [    0.022913] ACPI: All ACPI Tables successfully acquired
Jul 31 21:48:58 node-5 kernel: [    0.023063] ftrace: allocating 28617 entries in 112 pages
Jul 31 21:48:58 node-5 kernel: [    0.031856] dmar: Host address width 46
Jul 31 21:48:58 node-5 kernel: [    0.031858] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 31 21:48:58 node-5 kernel: [    0.031864] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 31 21:48:58 node-5 kernel: [    0.031866] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 31 21:48:58 node-5 kernel: [    0.031870] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 31 21:48:58 node-5 kernel: [    0.031871] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 31 21:48:58 node-5 kernel: [    0.031873] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 31 21:48:58 node-5 kernel: [    0.031874] dmar: ATSR flags: 0x0
Jul 31 21:48:58 node-5 kernel: [    0.031875] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 31 21:48:58 node-5 kernel: [    0.031876] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 31 21:48:58 node-5 kernel: [    0.031992] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 31 21:48:58 node-5 kernel: [    0.031993] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 31 21:48:58 node-5 kernel: [    0.031994] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 31 21:48:58 node-5 kernel: [    0.031996] HPET id 0 under DRHD base 0xc7ffc000
Jul 31 21:48:58 node-5 kernel: [    0.031997] Your BIOS is broken and requested that x2apic be disabled.
Jul 31 21:48:58 node-5 kernel: [    0.031997] This will slightly decrease performance.
Jul 31 21:48:58 node-5 kernel: [    0.031997] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 31 21:48:58 node-5 kernel: [    0.032427] Enabled IRQ remapping in xapic mode
Jul 31 21:48:58 node-5 kernel: [    0.032428] x2apic not enabled, IRQ remapping is in xapic mode
Jul 31 21:48:58 node-5 kernel: [    0.032431] Switched APIC routing to physical flat.
Jul 31 21:48:58 node-5 kernel: [    0.033057] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 31 21:48:58 node-5 kernel: [    0.072711] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 31 21:48:58 node-5 kernel: [    0.072717] TSC deadline timer enabled
Jul 31 21:48:58 node-5 kernel: [    0.072725] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 31 21:48:58 node-5 kernel: [    0.072731] ... version:                3
Jul 31 21:48:58 node-5 kernel: [    0.072731] ... bit width:              48
Jul 31 21:48:58 node-5 kernel: [    0.072732] ... generic registers:      4
Jul 31 21:48:58 node-5 kernel: [    0.072733] ... value mask:             0000ffffffffffff
Jul 31 21:48:58 node-5 kernel: [    0.072734] ... max period:             0000ffffffffffff
Jul 31 21:48:58 node-5 kernel: [    0.072735] ... fixed-purpose events:   3
Jul 31 21:48:58 node-5 kernel: [    0.072736] ... event mask:             000000070000000f
Jul 31 21:48:58 node-5 kernel: [    0.074163] x86: Booting SMP configuration:
Jul 31 21:48:58 node-5 kernel: [    0.088268] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 31 21:48:58 node-5 kernel: [    0.074165] .... node  #0, CPUs:        #1  #2  #3
Jul 31 21:48:58 node-5 kernel: [    0.116176] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 31 21:48:58 node-5 kernel: [    0.270342] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 31 21:48:58 node-5 kernel: [    0.325962] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 31 21:48:58 node-5 kernel: [    0.383026] x86: Booted up 2 nodes, 16 CPUs
Jul 31 21:48:58 node-5 kernel: [    0.383030] smpboot: Total of 16 processors activated (111765.93 BogoMIPS)
Jul 31 21:48:58 node-5 kernel: [    0.407392] devtmpfs: initialized
Jul 31 21:48:58 node-5 kernel: [    0.410482] EVM: security.selinux
Jul 31 21:48:58 node-5 kernel: [    0.410483] EVM: security.SMACK64
Jul 31 21:48:58 node-5 kernel: [    0.410484] EVM: security.ima
Jul 31 21:48:58 node-5 kernel: [    0.410485] EVM: security.capability
Jul 31 21:48:58 node-5 kernel: [    0.410535] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Jul 31 21:48:58 node-5 kernel: [    0.411204] pinctrl core: initialized pinctrl subsystem
Jul 31 21:48:58 node-5 kernel: [    0.411268] regulator-dummy: no parameters
Jul 31 21:48:58 node-5 kernel: [    0.411300] RTC time: 21:48:22, date: 07/31/16
Jul 31 21:48:58 node-5 kernel: [    0.411335] NET: Registered protocol family 16
Jul 31 21:48:58 node-5 kernel: [    0.411420] cpuidle: using governor ladder
Jul 31 21:48:58 node-5 kernel: [    0.411421] cpuidle: using governor menu
Jul 31 21:48:58 node-5 kernel: [    0.411455] ACPI: bus type PCI registered
Jul 31 21:48:58 node-5 kernel: [    0.411457] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 31 21:48:58 node-5 kernel: [    0.411504] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 31 21:48:58 node-5 kernel: [    0.411507] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 31 21:48:58 node-5 kernel: [    0.425236] PCI: Using configuration type 1 for base access
Jul 31 21:48:58 node-5 kernel: [    0.426248] bio: create slab <bio-0> at 0
Jul 31 21:48:58 node-5 kernel: [    0.426539] ACPI: Added _OSI(Module Device)
Jul 31 21:48:58 node-5 kernel: [    0.426540] ACPI: Added _OSI(Processor Device)
Jul 31 21:48:58 node-5 kernel: [    0.426541] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 31 21:48:58 node-5 kernel: [    0.426543] ACPI: Added _OSI(Processor Aggregator Device)
Jul 31 21:48:58 node-5 kernel: [    0.439201] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 31 21:48:58 node-5 kernel: [    0.450758] ACPI: Interpreter enabled
Jul 31 21:48:58 node-5 kernel: [    0.450764] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 31 21:48:58 node-5 kernel: [    0.450768] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 31 21:48:58 node-5 kernel: [    0.450771] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 31 21:48:58 node-5 kernel: [    0.450778] ACPI: (supports S0 S4 S5)
Jul 31 21:48:58 node-5 kernel: [    0.450779] ACPI: Using IOAPIC for interrupt routing
Jul 31 21:48:58 node-5 kernel: [    0.450821] HEST: Table parsing has been initialized.
Jul 31 21:48:58 node-5 kernel: [    0.450824] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 31 21:48:58 node-5 kernel: [    0.451375] ACPI: No dock devices found.
Jul 31 21:48:58 node-5 kernel: [    0.462944] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 31 21:48:58 node-5 kernel: [    0.462950] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 21:48:58 node-5 kernel: [    0.462953] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 31 21:48:58 node-5 kernel: [    0.462979] PCI host bridge to bus 0000:ff
Jul 31 21:48:58 node-5 kernel: [    0.462981] pci_bus 0000:ff: root bus resource [bus ff]
Jul 31 21:48:58 node-5 kernel: [    0.462989] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463027] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 31 21:48:58 node-5 kernel: [    0.463058] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463096] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463126] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 31 21:48:58 node-5 kernel: [    0.463155] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 31 21:48:58 node-5 kernel: [    0.463186] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463214] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463244] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463272] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463298] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463325] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463353] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463379] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463406] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463433] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463461] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463488] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463515] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 31 21:48:58 node-5 kernel: [    0.463543] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463569] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 31 21:48:58 node-5 kernel: [    0.463595] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463621] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463651] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 31 21:48:58 node-5 kernel: [    0.463686] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463717] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463747] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463778] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463809] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463840] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463870] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463901] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463931] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463964] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.463997] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464031] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464065] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464095] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464123] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464155] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464188] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464224] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464259] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464291] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464322] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464351] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464381] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464411] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464445] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464477] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464509] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464539] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464569] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464599] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464630] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464661] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464694] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464752] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 31 21:48:58 node-5 kernel: [    0.464754] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 21:48:58 node-5 kernel: [    0.464757] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 31 21:48:58 node-5 kernel: [    0.464776] PCI host bridge to bus 0000:7f
Jul 31 21:48:58 node-5 kernel: [    0.464777] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 31 21:48:58 node-5 kernel: [    0.464782] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464810] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 31 21:48:58 node-5 kernel: [    0.464838] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464865] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464887] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 31 21:48:58 node-5 kernel: [    0.464911] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 31 21:48:58 node-5 kernel: [    0.464937] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464964] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.464986] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465009] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465038] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465063] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465089] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465113] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465138] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465164] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465186] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465209] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465231] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 31 21:48:58 node-5 kernel: [    0.465255] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465278] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 31 21:48:58 node-5 kernel: [    0.465300] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465322] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465349] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 31 21:48:58 node-5 kernel: [    0.465383] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465409] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465435] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465462] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465487] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465513] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465539] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465566] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465591] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465620] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465648] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465676] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465705] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465734] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465758] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465787] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465812] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465841] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465870] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465899] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465926] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465953] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.465979] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.466005] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.466032] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.466059] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.466089] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.466115] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.466137] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.466164] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.466190] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.466220] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.466247] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.467505] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 31 21:48:58 node-5 kernel: [    0.467508] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 21:48:58 node-5 kernel: [    0.468625] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 31 21:48:58 node-5 kernel: [    0.469143] PCI host bridge to bus 0000:00
Jul 31 21:48:58 node-5 kernel: [    0.469145] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 31 21:48:58 node-5 kernel: [    0.469147] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 31 21:48:58 node-5 kernel: [    0.469148] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 31 21:48:58 node-5 kernel: [    0.469150] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 31 21:48:58 node-5 kernel: [    0.469151] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 31 21:48:58 node-5 kernel: [    0.469153] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 31 21:48:58 node-5 kernel: [    0.469154] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 31 21:48:58 node-5 kernel: [    0.469160] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 31 21:48:58 node-5 kernel: [    0.469243] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 31 21:48:58 node-5 kernel: [    0.469274] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-5 kernel: [    0.469315] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 31 21:48:58 node-5 kernel: [    0.469335] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 31 21:48:58 node-5 kernel: [    0.469365] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-5 kernel: [    0.469405] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 31 21:48:58 node-5 kernel: [    0.469423] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 31 21:48:58 node-5 kernel: [    0.469452] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-5 kernel: [    0.469492] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 31 21:48:58 node-5 kernel: [    0.469510] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.469581] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.469661] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.469736] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 31 21:48:58 node-5 kernel: [    0.469741] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 31 21:48:58 node-5 kernel: [    0.469825] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 31 21:48:58 node-5 kernel: [    0.469974] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 31 21:48:58 node-5 kernel: [    0.469992] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 31 21:48:58 node-5 kernel: [    0.470070] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-5 kernel: [    0.470123] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 31 21:48:58 node-5 kernel: [    0.470145] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 31 21:48:58 node-5 kernel: [    0.470200] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-5 kernel: [    0.470244] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 31 21:48:58 node-5 kernel: [    0.470272] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 31 21:48:58 node-5 kernel: [    0.470327] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-5 kernel: [    0.470370] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 31 21:48:58 node-5 kernel: [    0.470395] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 31 21:48:58 node-5 kernel: [    0.470412] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 31 21:48:58 node-5 kernel: [    0.470491] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-5 kernel: [    0.470540] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 31 21:48:58 node-5 kernel: [    0.470565] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 31 21:48:58 node-5 kernel: [    0.470813] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 31 21:48:58 node-5 kernel: [    0.470819] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 31 21:48:58 node-5 kernel: [    0.470825] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 31 21:48:58 node-5 kernel: [    0.470831] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 31 21:48:58 node-5 kernel: [    0.470838] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 31 21:48:58 node-5 kernel: [    0.470868] pci 0000:01:00.0: supports D1 D2
Jul 31 21:48:58 node-5 kernel: [    0.481033] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 31 21:48:58 node-5 kernel: [    0.481039] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 31 21:48:58 node-5 kernel: [    0.481043] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 31 21:48:58 node-5 kernel: [    0.481305] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 31 21:48:58 node-5 kernel: [    0.481365] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 31 21:48:58 node-5 kernel: [    0.489031] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 31 21:48:58 node-5 kernel: [    0.489037] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-5 kernel: [    0.489041] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 21:48:58 node-5 kernel: [    0.489132] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 31 21:48:58 node-5 kernel: [    0.489200] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 31 21:48:58 node-5 kernel: [    0.489276] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-5 kernel: [    0.489321] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 31 21:48:58 node-5 kernel: [    0.489325] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-5 kernel: [    0.489327] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 21:48:58 node-5 kernel: [    0.489387] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 31 21:48:58 node-5 kernel: [    0.489510] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-5 kernel: [    0.489564] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 31 21:48:58 node-5 kernel: [    0.489567] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-5 kernel: [    0.489569] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 21:48:58 node-5 kernel: [    0.489618] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 31 21:48:58 node-5 kernel: [    0.489737] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-5 kernel: [    0.489779] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 31 21:48:58 node-5 kernel: [    0.489898] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-5 kernel: [    0.489935] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 31 21:48:58 node-5 kernel: [    0.490056] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-5 kernel: [    0.490092] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 31 21:48:58 node-5 kernel: [    0.490211] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-5 kernel: [    0.490252] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 31 21:48:58 node-5 kernel: [    0.490255] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-5 kernel: [    0.490257] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 21:48:58 node-5 kernel: [    0.490317] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 31 21:48:58 node-5 kernel: [    0.490379] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 31 21:48:58 node-5 kernel: [    0.490456] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 31 21:48:58 node-5 kernel: [    0.490496] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 31 21:48:58 node-5 kernel: [    0.490579] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 31 21:48:58 node-5 kernel: [    0.490687] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 31 21:48:58 node-5 kernel: [    0.490689] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-5 kernel: [    0.490691] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 31 21:48:58 node-5 kernel: [    0.490747] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 31 21:48:58 node-5 kernel: [    0.490800] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 31 21:48:58 node-5 kernel: [    0.490849] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 31 21:48:58 node-5 kernel: [    0.491061] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 31 21:48:58 node-5 kernel: [    0.491065] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 31 21:48:58 node-5 kernel: [    0.491128] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 31 21:48:58 node-5 kernel: [    0.491181] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 31 21:48:58 node-5 kernel: [    0.491229] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 31 21:48:58 node-5 kernel: [    0.491459] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 31 21:48:58 node-5 kernel: [    0.491462] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 31 21:48:58 node-5 kernel: [    0.491521] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 31 21:48:58 node-5 kernel: [    0.491588] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 31 21:48:58 node-5 kernel: [    0.491640] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 31 21:48:58 node-5 kernel: [    0.491865] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 31 21:48:58 node-5 kernel: [    0.491869] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 31 21:48:58 node-5 kernel: [    0.492043] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 31 21:48:58 node-5 kernel: [    0.492081] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 31 21:48:58 node-5 kernel: [    0.492160] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 31 21:48:58 node-5 kernel: [    0.492179] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 31 21:48:58 node-5 kernel: [    0.492192] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 31 21:48:58 node-5 kernel: [    0.492205] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 31 21:48:58 node-5 kernel: [    0.492255] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 31 21:48:58 node-5 kernel: [    0.497038] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 31 21:48:58 node-5 kernel: [    0.497047] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 31 21:48:58 node-5 kernel: [    0.497099] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 31 21:48:58 node-5 kernel: [    0.497634] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 31 21:48:58 node-5 kernel: [    0.497637] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 21:48:58 node-5 kernel: [    0.497756] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 31 21:48:58 node-5 kernel: [    0.497865] PCI host bridge to bus 0000:80
Jul 31 21:48:58 node-5 kernel: [    0.497867] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 31 21:48:58 node-5 kernel: [    0.497869] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 31 21:48:58 node-5 kernel: [    0.497870] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 31 21:48:58 node-5 kernel: [    0.497878] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.497942] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.498010] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 31 21:48:58 node-5 kernel: [    0.498072] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 31 21:48:58 node-5 kernel: [    0.498077] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 31 21:48:58 node-5 kernel: [    0.498151] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 31 21:48:58 node-5 kernel: [    0.498447] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 31 21:48:58 node-5 kernel: [    0.498479] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 31 21:48:58 node-5 kernel: [    0.498508] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 31 21:48:58 node-5 kernel: [    0.498537] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 31 21:48:58 node-5 kernel: [    0.498566] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 21:48:58 node-5 kernel: [    0.498596] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 21:48:58 node-5 kernel: [    0.498626] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 21:48:58 node-5 kernel: [    0.498655] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 21:48:58 node-5 kernel: [    0.498741] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 31 21:48:58 node-5 kernel: [    0.498745] ACPI: \_SB_.UNC1: notify handler is installed
Jul 31 21:48:58 node-5 kernel: [    0.498746] ACPI: \_SB_.UNC0: notify handler is installed
Jul 31 21:48:58 node-5 kernel: [    0.498761] ACPI: \_SB_.PCI0: notify handler is installed
Jul 31 21:48:58 node-5 kernel: [    0.498814] ACPI: \_SB_.PCI1: notify handler is installed
Jul 31 21:48:58 node-5 kernel: [    0.498894] Found 4 acpi root devices
Jul 31 21:48:58 node-5 kernel: [    0.499004] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 31 21:48:58 node-5 kernel: [    0.499006] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 31 21:48:58 node-5 kernel: [    0.499008] vgaarb: loaded
Jul 31 21:48:58 node-5 kernel: [    0.499009] vgaarb: bridge control possible 0000:0c:00.0
Jul 31 21:48:58 node-5 kernel: [    0.499127] SCSI subsystem initialized
Jul 31 21:48:58 node-5 kernel: [    0.499191] libata version 3.00 loaded.
Jul 31 21:48:58 node-5 kernel: [    0.499206] ACPI: bus type USB registered
Jul 31 21:48:58 node-5 kernel: [    0.499216] usbcore: registered new interface driver usbfs
Jul 31 21:48:58 node-5 kernel: [    0.499221] usbcore: registered new interface driver hub
Jul 31 21:48:58 node-5 kernel: [    0.499245] usbcore: registered new device driver usb
Jul 31 21:48:58 node-5 kernel: [    0.499414] PCI: Using ACPI for IRQ routing
Jul 31 21:48:58 node-5 kernel: [    0.503014] PCI: pci_cache_line_size set to 64 bytes
Jul 31 21:48:58 node-5 kernel: [    0.503219] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 31 21:48:58 node-5 kernel: [    0.503221] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Jul 31 21:48:58 node-5 kernel: [    0.503221] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 31 21:48:58 node-5 kernel: [    0.503286] NetLabel: Initializing
Jul 31 21:48:58 node-5 kernel: [    0.503287] NetLabel:  domain hash size = 128
Jul 31 21:48:58 node-5 kernel: [    0.503288] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 31 21:48:58 node-5 kernel: [    0.503297] NetLabel:  unlabeled traffic allowed by default
Jul 31 21:48:58 node-5 kernel: [    0.503354] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 31 21:48:58 node-5 kernel: [    0.503358] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 31 21:48:58 node-5 kernel: [    0.505427] Switched to clocksource hpet
Jul 31 21:48:58 node-5 kernel: [    0.509895] AppArmor: AppArmor Filesystem Enabled
Jul 31 21:48:58 node-5 kernel: [    0.509933] pnp: PnP ACPI init
Jul 31 21:48:58 node-5 kernel: [    0.509945] ACPI: bus type PNP registered
Jul 31 21:48:58 node-5 kernel: [    0.510128] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 31 21:48:58 node-5 kernel: [    0.510140] pnp 00:01: [dma 4]
Jul 31 21:48:58 node-5 kernel: [    0.510158] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 31 21:48:58 node-5 kernel: [    0.510192] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 31 21:48:58 node-5 kernel: [    0.510216] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 31 21:48:58 node-5 kernel: [    0.510237] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 31 21:48:58 node-5 kernel: [    0.510283] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 31 21:48:58 node-5 kernel: [    0.510397] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 31 21:48:58 node-5 kernel: [    0.510399] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 31 21:48:58 node-5 kernel: [    0.510401] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 31 21:48:58 node-5 kernel: [    0.510402] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 31 21:48:58 node-5 kernel: [    0.510404] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 31 21:48:58 node-5 kernel: [    0.510405] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 31 21:48:58 node-5 kernel: [    0.510409] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 31 21:48:58 node-5 kernel: [    0.510411] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 31 21:48:58 node-5 kernel: [    0.510412] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 31 21:48:58 node-5 kernel: [    0.510414] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 31 21:48:58 node-5 kernel: [    0.510415] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 31 21:48:58 node-5 kernel: [    0.510417] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 31 21:48:58 node-5 kernel: [    0.510418] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 31 21:48:58 node-5 kernel: [    0.510421] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 31 21:48:58 node-5 kernel: [    0.510523] pnp 00:07: [dma 0 disabled]
Jul 31 21:48:58 node-5 kernel: [    0.510556] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 31 21:48:58 node-5 kernel: [    0.510638] pnp 00:08: [dma 0 disabled]
Jul 31 21:48:58 node-5 kernel: [    0.510674] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 31 21:48:58 node-5 kernel: [    0.510733] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 31 21:48:58 node-5 kernel: [    0.511180] pnp: PnP ACPI: found 10 devices
Jul 31 21:48:58 node-5 kernel: [    0.511182] ACPI: bus type PNP unregistered
Jul 31 21:48:58 node-5 kernel: [    0.517191] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 31 21:48:58 node-5 kernel: [    0.517195] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 31 21:48:58 node-5 kernel: [    0.517198] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 31 21:48:58 node-5 kernel: [    0.517203] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 31 21:48:58 node-5 kernel: [    0.517205] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-5 kernel: [    0.517220] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 31 21:48:58 node-5 kernel: [    0.517249] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 31 21:48:58 node-5 kernel: [    0.517264] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 31 21:48:58 node-5 kernel: [    0.517292] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 31 21:48:58 node-5 kernel: [    0.517311] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 31 21:48:58 node-5 kernel: [    0.517340] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 31 21:48:58 node-5 kernel: [    0.517354] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 31 21:48:58 node-5 kernel: [    0.517397] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 31 21:48:58 node-5 kernel: [    0.517399] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-5 kernel: [    0.517418] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 21:48:58 node-5 kernel: [    0.517447] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 31 21:48:58 node-5 kernel: [    0.517449] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-5 kernel: [    0.517464] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 21:48:58 node-5 kernel: [    0.517493] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 31 21:48:58 node-5 kernel: [    0.517495] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-5 kernel: [    0.517498] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 21:48:58 node-5 kernel: [    0.517502] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 31 21:48:58 node-5 kernel: [    0.517504] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-5 kernel: [    0.517507] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 21:48:58 node-5 kernel: [    0.517511] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 31 21:48:58 node-5 kernel: [    0.517518] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 31 21:48:58 node-5 kernel: [    0.517527] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 31 21:48:58 node-5 kernel: [    0.517530] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 31 21:48:58 node-5 kernel: [    0.517538] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 31 21:48:58 node-5 kernel: [    0.517539] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 31 21:48:58 node-5 kernel: [    0.517539] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 31 21:48:58 node-5 kernel: [    0.517540] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 31 21:48:58 node-5 kernel: [    0.517541] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 31 21:48:58 node-5 kernel: [    0.517542] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 31 21:48:58 node-5 kernel: [    0.517543] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 31 21:48:58 node-5 kernel: [    0.517544] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 31 21:48:58 node-5 kernel: [    0.517545] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 31 21:48:58 node-5 kernel: [    0.517546] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 31 21:48:58 node-5 kernel: [    0.517547] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 31 21:48:58 node-5 kernel: [    0.517548] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 31 21:48:58 node-5 kernel: [    0.517549] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 31 21:48:58 node-5 kernel: [    0.517550] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 31 21:48:58 node-5 kernel: [    0.517551] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 31 21:48:58 node-5 kernel: [    0.517552] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 31 21:48:58 node-5 kernel: [    0.517553] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 31 21:48:58 node-5 kernel: [    0.517553] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 31 21:48:58 node-5 kernel: [    0.517555] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 31 21:48:58 node-5 kernel: [    0.517556] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 31 21:48:58 node-5 kernel: [    0.517557] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 31 21:48:58 node-5 kernel: [    0.517558] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 31 21:48:58 node-5 kernel: [    0.517561] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 31 21:48:58 node-5 kernel: [    0.517562] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 31 21:48:58 node-5 kernel: [    0.517604] NET: Registered protocol family 2
Jul 31 21:48:58 node-5 kernel: [    0.517906] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 31 21:48:58 node-5 kernel: [    0.518288] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 31 21:48:58 node-5 kernel: [    0.518453] TCP: Hash tables configured (established 262144 bind 65536)
Jul 31 21:48:58 node-5 kernel: [    0.518498] TCP: reno registered
Jul 31 21:48:58 node-5 kernel: [    0.518529] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 31 21:48:58 node-5 kernel: [    0.518634] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 31 21:48:58 node-5 kernel: [    0.518811] NET: Registered protocol family 1
Jul 31 21:48:58 node-5 kernel: [    0.557457] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 31 21:48:58 node-5 kernel: [    0.557465] PCI: CLS 64 bytes, default 64
Jul 31 21:48:58 node-5 kernel: [    0.557509] Trying to unpack rootfs image as initramfs...
Jul 31 21:48:58 node-5 kernel: [    0.779207] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 31 21:48:58 node-5 kernel: [    0.779271] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 31 21:48:58 node-5 kernel: [    0.779274] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Jul 31 21:48:58 node-5 kernel: [    0.779718] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-5 kernel: [    0.779732] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-5 kernel: [    0.779746] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-5 kernel: [    0.779758] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-5 kernel: [    0.779770] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-5 kernel: [    0.779778] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-5 kernel: [    0.779785] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-5 kernel: [    0.779790] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-5 kernel: [    0.779798] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-5 kernel: [    0.779809] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-5 kernel: [    0.779824] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-5 kernel: [    0.779836] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-5 kernel: [    0.779846] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-5 kernel: [    0.779853] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-5 kernel: [    0.779858] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-5 kernel: [    0.779864] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-5 kernel: [    0.779910] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 31 21:48:58 node-5 kernel: [    0.779912] Scanning for low memory corruption every 60 seconds
Jul 31 21:48:58 node-5 kernel: [    0.780212] Initialise system trusted keyring
Jul 31 21:48:58 node-5 kernel: [    0.780260] audit: initializing netlink socket (disabled)
Jul 31 21:48:58 node-5 kernel: [    0.780271] type=2000 audit(1470001701.732:1): initialized
Jul 31 21:48:58 node-5 kernel: [    0.798176] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 31 21:48:58 node-5 kernel: [    0.799643] zbud: loaded
Jul 31 21:48:58 node-5 kernel: [    0.799762] VFS: Disk quotas dquot_6.5.2
Jul 31 21:48:58 node-5 kernel: [    0.799803] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 31 21:48:58 node-5 kernel: [    0.800163] fuse init (API version 7.22)
Jul 31 21:48:58 node-5 kernel: [    0.800214] msgmni has been set to 32768
Jul 31 21:48:58 node-5 kernel: [    0.800259] Key type big_key registered
Jul 31 21:48:58 node-5 kernel: [    0.800812] Key type asymmetric registered
Jul 31 21:48:58 node-5 kernel: [    0.800816] Asymmetric key parser 'x509' registered
Jul 31 21:48:58 node-5 kernel: [    0.800864] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 31 21:48:58 node-5 kernel: [    0.800952] io scheduler noop registered
Jul 31 21:48:58 node-5 kernel: [    0.800955] io scheduler deadline registered (default)
Jul 31 21:48:58 node-5 kernel: [    0.800996] io scheduler cfq registered
Jul 31 21:48:58 node-5 kernel: [    0.801445] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    0.801574] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    0.801694] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    0.801819] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    0.801933] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    0.802026] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    0.802470] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 31 21:48:58 node-5 kernel: [    0.802510] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 31 21:48:58 node-5 kernel: [    0.802526] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 31 21:48:58 node-5 kernel: [    0.802538] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802540] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802543] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 31 21:48:58 node-5 kernel: [    0.802548] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802549] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802550] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802552] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802554] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802555] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802556] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802558] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802559] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802560] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802562] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802563] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802565] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 31 21:48:58 node-5 kernel: [    0.802576] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802578] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 31 21:48:58 node-5 kernel: [    0.802589] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802592] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 31 21:48:58 node-5 kernel: [    0.802603] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802604] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-5 kernel: [    0.802607] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 31 21:48:58 node-5 kernel: [    0.802634] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 31 21:48:58 node-5 kernel: [    0.802640] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 31 21:48:58 node-5 kernel: [    0.802644] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 31 21:48:58 node-5 kernel: [    0.802652] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 31 21:48:58 node-5 kernel: [    0.802688] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 31 21:48:58 node-5 kernel: [    0.802689] vesafb: scrolling: redraw
Jul 31 21:48:58 node-5 kernel: [    0.802691] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 31 21:48:58 node-5 kernel: [    0.823271] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 31 21:48:58 node-5 kernel: [    0.831774] Console: switching to colour frame buffer device 80x30
Jul 31 21:48:58 node-5 kernel: [    0.840441] fb0: VESA VGA frame buffer device
Jul 31 21:48:58 node-5 kernel: [    0.840638] intel_idle: MWAIT substates: 0x2120
Jul 31 21:48:58 node-5 kernel: [    0.840639] intel_idle: v0.4 model 0x3F
Jul 31 21:48:58 node-5 kernel: [    0.840640] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 31 21:48:58 node-5 kernel: [    0.840871] ipmi message handler version 39.2
Jul 31 21:48:58 node-5 kernel: [    0.841147] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 31 21:48:58 node-5 kernel: [    0.841581] ACPI: AC Adapter [P111] (on-line)
Jul 31 21:48:58 node-5 kernel: [    0.846831] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 31 21:48:58 node-5 kernel: [    0.857817] ACPI: Power Button [PWRB]
Jul 31 21:48:58 node-5 kernel: [    0.863565] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 31 21:48:58 node-5 kernel: [    0.875172] ACPI: Power Button [PWRF]
Jul 31 21:48:58 node-5 kernel: [    0.890913] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 31 21:48:58 node-5 kernel: [    0.902573] pstore: Registered erst as persistent store backend
Jul 31 21:48:58 node-5 kernel: [    0.908761] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 31 21:48:58 node-5 kernel: [    0.920676] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 31 21:48:58 node-5 kernel: [    0.947408] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 31 21:48:58 node-5 kernel: [    0.980664] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 31 21:48:58 node-5 kernel: [    0.994781] Linux agpgart interface v0.103
Jul 31 21:48:58 node-5 kernel: [    1.002403] brd: module loaded
Jul 31 21:48:58 node-5 kernel: [    1.009491] loop: module loaded
Jul 31 21:48:58 node-5 kernel: [    1.016186] libphy: Fixed MDIO Bus: probed
Jul 31 21:48:58 node-5 kernel: [    1.022655] tun: Universal TUN/TAP device driver, 1.6
Jul 31 21:48:58 node-5 kernel: [    1.029117] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 31 21:48:58 node-5 kernel: [    1.035623] PPP generic driver version 2.4.2
Jul 31 21:48:58 node-5 kernel: [    1.042005] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 31 21:48:58 node-5 kernel: [    1.048441] ehci-pci: EHCI PCI platform driver
Jul 31 21:48:58 node-5 kernel: [    1.054965] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 31 21:48:58 node-5 kernel: [    1.061388] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 31 21:48:58 node-5 kernel: [    1.073915] ehci-pci 0000:00:1a.0: debug port 2
Jul 31 21:48:58 node-5 kernel: [    1.084119] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 31 21:48:58 node-5 kernel: [    1.084137] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 31 21:48:58 node-5 kernel: [    1.100914] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 31 21:48:58 node-5 kernel: [    1.107003] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 31 21:48:58 node-5 kernel: [    1.113191] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 31 21:48:58 node-5 kernel: [    1.125115] usb usb1: Product: EHCI Host Controller
Jul 31 21:48:58 node-5 kernel: [    1.131149] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 31 21:48:58 node-5 kernel: [    1.137212] usb usb1: SerialNumber: 0000:00:1a.0
Jul 31 21:48:58 node-5 kernel: [    1.143171] hub 1-0:1.0: USB hub found
Jul 31 21:48:58 node-5 kernel: [    1.148956] hub 1-0:1.0: 2 ports detected
Jul 31 21:48:58 node-5 kernel: [    1.154762] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 31 21:48:58 node-5 kernel: [    1.160364] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 31 21:48:58 node-5 kernel: [    1.171298] ehci-pci 0000:00:1d.0: debug port 2
Jul 31 21:48:58 node-5 kernel: [    1.180624] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 31 21:48:58 node-5 kernel: [    1.180627] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 31 21:48:58 node-5 kernel: [    1.196832] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 31 21:48:58 node-5 kernel: [    1.202150] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 31 21:48:58 node-5 kernel: [    1.207470] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 31 21:48:58 node-5 kernel: [    1.218072] usb usb2: Product: EHCI Host Controller
Jul 31 21:48:58 node-5 kernel: [    1.223553] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 31 21:48:58 node-5 kernel: [    1.229115] usb usb2: SerialNumber: 0000:00:1d.0
Jul 31 21:48:58 node-5 kernel: [    1.234646] hub 2-0:1.0: USB hub found
Jul 31 21:48:58 node-5 kernel: [    1.240011] hub 2-0:1.0: 2 ports detected
Jul 31 21:48:58 node-5 kernel: [    1.245325] ehci-platform: EHCI generic platform driver
Jul 31 21:48:58 node-5 kernel: [    1.250567] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 31 21:48:58 node-5 kernel: [    1.255889] ohci-pci: OHCI PCI platform driver
Jul 31 21:48:58 node-5 kernel: [    1.261201] ohci-platform: OHCI generic platform driver
Jul 31 21:48:58 node-5 kernel: [    1.266406] uhci_hcd: USB Universal Host Controller Interface driver
Jul 31 21:48:58 node-5 kernel: [    1.271750] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 31 21:48:58 node-5 kernel: [    1.464634] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 31 21:48:58 node-5 kernel: [    1.636788] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 31 21:48:58 node-5 kernel: [    1.642337] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 31 21:48:58 node-5 kernel: [    1.648055] hub 1-1:1.0: USB hub found
Jul 31 21:48:58 node-5 kernel: [    1.653524] hub 1-1:1.0: 6 ports detected
Jul 31 21:48:58 node-5 kernel: [    1.768347] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 31 21:48:58 node-5 kernel: [    1.776379] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 31 21:48:58 node-5 kernel: [    2.036449] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 31 21:48:58 node-5 kernel: [    2.042004] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 31 21:48:58 node-5 kernel: [    2.047841] hub 2-1:1.0: USB hub found
Jul 31 21:48:58 node-5 kernel: [    2.053560] hub 2-1:1.0: 8 ports detected
Jul 31 21:48:58 node-5 kernel: [    2.313631] i8042: No controller found
Jul 31 21:48:58 node-5 kernel: [    2.319059] mousedev: PS/2 mouse device common for all mice
Jul 31 21:48:58 node-5 kernel: [    2.324579] rtc_cmos 00:02: RTC can wake from S4
Jul 31 21:48:58 node-5 kernel: [    2.330171] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 31 21:48:58 node-5 kernel: [    2.331947] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 31 21:48:58 node-5 kernel: [    2.341317] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 31 21:48:58 node-5 kernel: [    2.352409] device-mapper: uevent: version 1.0.3
Jul 31 21:48:58 node-5 kernel: [    2.358051] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 31 21:48:58 node-5 kernel: [    2.369270] ledtrig-cpu: registered to indicate activity on CPUs
Jul 31 21:48:58 node-5 kernel: [    2.375199] TCP: cubic registered
Jul 31 21:48:58 node-5 kernel: [    2.381090] NET: Registered protocol family 10
Jul 31 21:48:58 node-5 kernel: [    2.387066] NET: Registered protocol family 17
Jul 31 21:48:58 node-5 kernel: [    2.392733] Key type dns_resolver registered
Jul 31 21:48:58 node-5 kernel: [    2.398683] Loading compiled-in X.509 certificates
Jul 31 21:48:58 node-5 kernel: [    2.404829] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 31 21:48:58 node-5 kernel: [    2.416193] registered taskstats version 1
Jul 31 21:48:58 node-5 kernel: [    2.424165] Key type trusted registered
Jul 31 21:48:58 node-5 kernel: [    2.431757] Key type encrypted registered
Jul 31 21:48:58 node-5 kernel: [    2.437209] AppArmor: AppArmor sha1 policy hashing enabled
Jul 31 21:48:58 node-5 kernel: [    2.442683] IMA: No TPM chip found, activating TPM-bypass!
Jul 31 21:48:58 node-5 kernel: [    2.448829] regulator-dummy: disabling
Jul 31 21:48:58 node-5 kernel: [    2.454375]   Magic number: 8:353:855
Jul 31 21:48:58 node-5 kernel: [    2.459838] acpi device:d2: hash matches
Jul 31 21:48:58 node-5 kernel: [    2.464153] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 31 21:48:58 node-5 kernel: [    2.464153] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 31 21:48:58 node-5 kernel: [    2.464154] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 31 21:48:58 node-5 kernel: [    2.464155] usb 2-1.4: Manufacturer: Avocent
Jul 31 21:48:58 node-5 kernel: [    2.464156] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 31 21:48:58 node-5 kernel: [    2.498215] rtc_cmos 00:02: setting system clock to 2016-07-31 21:48:24 UTC (1470001704)
Jul 31 21:48:58 node-5 kernel: [    2.510917] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 31 21:48:58 node-5 kernel: [    2.516584] EDD information not available.
Jul 31 21:48:58 node-5 kernel: [    2.522139] PM: Hibernation image not present or could not be loaded.
Jul 31 21:48:58 node-5 kernel: [    2.522997] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 31 21:48:58 node-5 kernel: [    2.534409] Write protecting the kernel read-only data: 12288k
Jul 31 21:48:58 node-5 kernel: [    2.540656] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 31 21:48:58 node-5 kernel: [    2.553212] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 31 21:48:58 node-5 kernel: [    2.585941] device-mapper: multipath: version 1.6.0 loaded
Jul 31 21:48:58 node-5 kernel: [    2.594104] systemd-udevd[216]: starting version 204
Jul 31 21:48:58 node-5 kernel: [    2.616289] md: linear personality registered for level -1
Jul 31 21:48:58 node-5 kernel: [    2.630371] md: multipath personality registered for level -4
Jul 31 21:48:58 node-5 kernel: [    2.638290] md: raid0 personality registered for level 0
Jul 31 21:48:58 node-5 kernel: [    2.646764] md: raid1 personality registered for level 1
Jul 31 21:48:58 node-5 kernel: [    2.655485] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 31 21:48:58 node-5 kernel: [    2.661839] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 31 21:48:58 node-5 kernel: [    2.668187] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 31 21:48:58 node-5 kernel: [    2.671088] megasas: FW now in Ready state
Jul 31 21:48:58 node-5 kernel: [    2.672180] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.672304] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.672356] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.672480] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.672560] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.672736] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.672844] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.673020] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.673113] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.673275] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.673368] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.673485] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.673591] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.673725] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.673887] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.674006] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.674617] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 31 21:48:58 node-5 kernel: [    2.694098] hidraw: raw HID events driver (C) Jiri Kosina
Jul 31 21:48:58 node-5 kernel: [    2.703707] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Jul 31 21:48:58 node-5 kernel: [    2.716951] 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 31 21:48:58 node-5 kernel: [    2.719618] raid6: sse2x1   11334 MB/s
Jul 31 21:48:58 node-5 kernel: [    2.737385] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 21:48:58 node-5 kernel: [    2.744330] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.744335] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.744339] usbcore: registered new interface driver usbhid
Jul 31 21:48:58 node-5 kernel: [    2.744340] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.744344] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.744897] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.764596] usbhid: USB HID core driver
Jul 31 21:48:58 node-5 kernel: [    2.765382] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Jul 31 21:48:58 node-5 kernel: [    2.765388] 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 31 21:48:58 node-5 kernel: [    2.765408] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 21:48:58 node-5 kernel: [    2.765826] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.766003] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.766112] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.766293] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.766485] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 21:48:58 node-5 kernel: [    2.781742] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Jul 31 21:48:58 node-5 kernel: [    2.781744] 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 31 21:48:58 node-5 kernel: [    2.781763] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 21:48:58 node-5 kernel: [    2.787746] raid6: sse2x2   13375 MB/s
Jul 31 21:48:58 node-5 kernel: [    2.855631] raid6: sse2x4    9534 MB/s
Jul 31 21:48:58 node-5 kernel: [    2.923382] raid6: avx2x1   14859 MB/s
Jul 31 21:48:58 node-5 kernel: [    2.995322] raid6: avx2x2   18859 MB/s
Jul 31 21:48:58 node-5 kernel: [    3.067249] raid6: avx2x4   21268 MB/s
Jul 31 21:48:58 node-5 kernel: [    3.073657] raid6: using algorithm avx2x4 (21268 MB/s)
Jul 31 21:48:58 node-5 kernel: [    3.079996] raid6: using avx2x2 recovery algorithm
Jul 31 21:48:58 node-5 kernel: [    3.086247] megasas:IOC Init cmd success
Jul 31 21:48:58 node-5 kernel: [    3.086249] Switched to clocksource tsc
Jul 31 21:48:58 node-5 kernel: [    3.086406] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    3.086535] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    3.086670] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    3.086793] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    3.087266] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 21:48:58 node-5 kernel: [    3.102425] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Jul 31 21:48:58 node-5 kernel: [    3.102437] 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 31 21:48:58 node-5 kernel: [    3.102466] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 21:48:58 node-5 kernel: [    3.102979] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    3.103045] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    3.103117] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    3.103266] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 31 21:48:58 node-5 kernel: [    3.103526] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 21:48:58 node-5 kernel: [    3.153028] xor: automatically using best checksumming function:
Jul 31 21:48:58 node-5 kernel: [    3.163889] 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 31 21:48:58 node-5 kernel: [    3.175907] megasas: INIT adapter done
Jul 31 21:48:58 node-5 kernel: [    3.177107] 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 31 21:48:58 node-5 kernel: [    3.178005] 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 31 21:48:58 node-5 kernel: [    3.178945] 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 31 21:48:58 node-5 kernel: [    3.180012] 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 31 21:48:58 node-5 kernel: [    3.181051] 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 31 21:48:58 node-5 kernel: [    3.195144]    avx       : 36624.000 MB/sec
Jul 31 21:48:58 node-5 kernel: [    3.252609] async_tx: api initialized (async)
Jul 31 21:48:58 node-5 kernel: [    3.263297] md: raid6 personality registered for level 6
Jul 31 21:48:58 node-5 kernel: [    3.270352] md: raid5 personality registered for level 5
Jul 31 21:48:58 node-5 kernel: [    3.277324] md: raid4 personality registered for level 4
Jul 31 21:48:58 node-5 kernel: [    3.287114] md: raid10 personality registered for level 10
Jul 31 21:48:58 node-5 kernel: [    3.323112] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 31 21:48:58 node-5 kernel: [    3.324918] scsi0 : LSI SAS based MegaRAID driver
Jul 31 21:48:58 node-5 kernel: [    3.340239] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 31 21:48:58 node-5 kernel: [    3.365055] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 31 21:48:58 node-5 kernel: [    3.369134] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 31 21:48:58 node-5 kernel: [    3.369245] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 31 21:48:58 node-5 kernel: [    3.369560] sd 0:2:0:0: [sda] Write Protect is off
Jul 31 21:48:58 node-5 kernel: [    3.369561] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 31 21:48:58 node-5 kernel: [    3.369633] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 31 21:48:58 node-5 kernel: [    3.399244]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 31 21:48:58 node-5 kernel: [    3.399876] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 31 21:48:58 node-5 kernel: [    3.432746] multipathd (359): /proc/359/oom_adj is deprecated, please use /proc/359/oom_score_adj instead.
Jul 31 21:48:58 node-5 kernel: [    3.551766] random: lvm urandom read with 28 bits of entropy available
Jul 31 21:48:58 node-5 kernel: [    3.704934] bio: create slab <bio-1> at 1
Jul 31 21:48:58 node-5 kernel: [    4.383381] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 21:48:58 node-5 kernel: [    5.049545] init: plymouth-upstart-bridge main process (549) terminated with status 1
Jul 31 21:48:58 node-5 kernel: [    5.062406] init: plymouth-upstart-bridge main process ended, respawning
Jul 31 21:48:58 node-5 kernel: [    5.214662] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 31 21:48:58 node-5 kernel: [    5.281574] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 31 21:48:58 node-5 kernel: [    5.397490] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 31 21:48:58 node-5 kernel: [    5.433465] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 31 21:48:58 node-5 kernel: [    5.502828] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 21:48:58 node-5 kernel: [    5.548811] random: nonblocking pool is initialized
Jul 31 21:48:58 node-5 kernel: [    5.716576] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 31 21:48:58 node-5 kernel: [    5.764599] XFS (dm-0): Mounting Filesystem
Jul 31 21:48:58 node-5 kernel: [    5.991993] XFS (dm-0): Ending clean mount
Jul 31 21:48:58 node-5 kernel: [    6.041485] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 21:48:58 node-5 kernel: [    6.075740] XFS (dm-1): Mounting Filesystem
Jul 31 21:48:58 node-5 kernel: [    6.229761] XFS (dm-1): Ending clean mount
Jul 31 21:48:58 node-5 kernel: [    8.269052] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 31 21:48:58 node-5 kernel: [    8.296328] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 31 21:48:58 node-5 kernel: [    8.488025] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 31 21:48:58 node-5 kernel: [    8.488036] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 31 21:48:58 node-5 kernel: [    8.488043] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 31 21:48:58 node-5 kernel: [    8.488050] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 31 21:48:58 node-5 kernel: [    8.535562] systemd-udevd[773]: starting version 204
Jul 31 21:48:58 node-5 kernel: [    8.812764] wmi: Mapper loaded
Jul 31 21:48:58 node-5 kernel: [    8.826950] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 31 21:48:58 node-5 kernel: [    8.826955] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 31 21:48:58 node-5 kernel: [    8.826958] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 31 21:48:58 node-5 kernel: [    8.826960] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 31 21:48:58 node-5 kernel: [    8.826977] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 31 21:48:58 node-5 kernel: [    8.831125] power_meter ACPI000D:00: Found ACPI power meter.
Jul 31 21:48:58 node-5 kernel: [    8.831171] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 31 21:48:58 node-5 kernel: [    8.838083] IPMI System Interface driver.
Jul 31 21:48:58 node-5 kernel: [    8.838113] ipmi_si: probing via ACPI
Jul 31 21:48:58 node-5 kernel: [    8.838126] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 31 21:48:58 node-5 kernel: [    8.838127] ipmi_si: Adding ACPI-specified kcs state machine
Jul 31 21:48:58 node-5 kernel: [    8.838135] ipmi_si: probing via SMBIOS
Jul 31 21:48:58 node-5 kernel: [    8.838136] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 31 21:48:58 node-5 kernel: [    8.838136] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 31 21:48:58 node-5 kernel: [    8.838138] ipmi_si: probing via SPMI
Jul 31 21:48:58 node-5 kernel: [    8.838139] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 31 21:48:58 node-5 kernel: [    8.838139] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 31 21:48:58 node-5 kernel: [    8.838141] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 31 21:48:58 node-5 kernel: [    8.839056] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 31 21:48:58 node-5 kernel: [    8.914772] systemd-udevd[814]: renamed network interface eth2 to enp8s0
Jul 31 21:48:58 node-5 kernel: [    8.946633] systemd-udevd[797]: renamed network interface eth0 to enp6s0
Jul 31 21:48:58 node-5 kernel: [    8.962604] systemd-udevd[815]: renamed network interface eth3 to enp9s0
Jul 31 21:48:58 node-5 kernel: [    8.994897] systemd-udevd[811]: renamed network interface eth1 to enp7s0
Jul 31 21:48:58 node-5 kernel: [    9.012598] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 31 21:48:58 node-5 kernel: [    9.012610] ipmi_si 00:09: IPMI kcs interface initialized
Jul 31 21:48:58 node-5 kernel: [    9.385760] type=1400 audit(1470001711.387:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1043 comm="apparmor_parser"
Jul 31 21:48:58 node-5 kernel: [    9.385923] type=1400 audit(1470001711.391:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1043 comm="apparmor_parser"
Jul 31 21:48:58 node-5 kernel: [    9.386051] type=1400 audit(1470001711.391:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1043 comm="apparmor_parser"
Jul 31 21:48:58 node-5 kernel: [    9.397646] type=1400 audit(1470001711.399:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1047 comm="apparmor_parser"
Jul 31 21:48:58 node-5 kernel: [    9.397790] type=1400 audit(1470001711.399:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1047 comm="apparmor_parser"
Jul 31 21:48:58 node-5 kernel: [    9.397919] type=1400 audit(1470001711.403:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1047 comm="apparmor_parser"
Jul 31 21:48:58 node-5 kernel: [    9.399740] type=1400 audit(1470001711.403:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1046 comm="apparmor_parser"
Jul 31 21:48:58 node-5 kernel: [    9.399878] type=1400 audit(1470001711.403:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1046 comm="apparmor_parser"
Jul 31 21:48:58 node-5 kernel: [    9.399998] type=1400 audit(1470001711.403:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1046 comm="apparmor_parser"
Jul 31 21:48:58 node-5 kernel: [    9.446280] type=1400 audit(1470001711.451:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1044 comm="apparmor_parser"
Jul 31 21:48:58 node-5 kernel: [    9.991930] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 31 21:48:58 node-5 kernel: [   10.007449] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 31 21:48:58 node-5 kernel: [   10.188810] enic 0000:06:00.0 enp6s0: Link UP
Jul 31 21:48:58 node-5 kernel: [   10.189238] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 31 21:48:58 node-5 kernel: [   10.189243] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 31 21:48:58 node-5 kernel: [   19.773693] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 31 21:48:59 node-5 failsafe: Failsafe of 120 seconds reached.
Jul 31 21:48:59 node-5 kernel: [   38.196712] init: failsafe main process (8392) killed by TERM signal
Jul 31 21:48:59 node-5 dbus[8441]: [system] AppArmor D-Bus mediation is enabled
Jul 31 21:48:59 node-5 kernel: [   38.459810] audit_printk_skb: 30 callbacks suppressed
Jul 31 21:48:59 node-5 kernel: [   38.459812] type=1400 audit(1470001739.991:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8509 comm="apparmor_parser"
Jul 31 21:48:59 node-5 kernel: [   38.459817] type=1400 audit(1470001739.991:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8509 comm="apparmor_parser"
Jul 31 21:48:59 node-5 kernel: [   38.459820] type=1400 audit(1470001739.991:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8509 comm="apparmor_parser"
Jul 31 21:48:59 node-5 kernel: [   38.460046] type=1400 audit(1470001739.991:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8509 comm="apparmor_parser"
Jul 31 21:48:59 node-5 kernel: [   38.460048] type=1400 audit(1470001739.991:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8509 comm="apparmor_parser"
Jul 31 21:48:59 node-5 kernel: [   38.460164] type=1400 audit(1470001739.991:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8509 comm="apparmor_parser"
Jul 31 21:49:00 node-5 kernel: [   38.482294] type=1400 audit(1470001740.015:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8510 comm="apparmor_parser"
Jul 31 21:49:00 node-5 kernel: [   38.531356] type=1400 audit(1470001740.063:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8512 comm="apparmor_parser"
Jul 31 21:49:00 node-5 anacron[8586]: Anacron 2.3 started on 2016-07-31
Jul 31 21:49:00 node-5 cron[8550]: (CRON) INFO (pidfile fd = 3)
Jul 31 21:49:00 node-5 cron[8593]: (CRON) STARTUP (fork ok)
Jul 31 21:49:00 node-5 anacron[8586]: Will run job `cron.daily' in 5 min.
Jul 31 21:49:00 node-5 anacron[8586]: Will run job `cron.weekly' in 10 min.
Jul 31 21:49:00 node-5 anacron[8586]: Will run job `cron.monthly' in 15 min.
Jul 31 21:49:00 node-5 anacron[8586]: Jobs will be executed sequentially
Jul 31 21:49:00 node-5 multipathd: path checkers start up
Jul 31 21:49:00 node-5 cron[8593]: (CRON) INFO (Running @reboot jobs)
Jul 31 21:49:00 node-5 postfix/master[8730]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 31 21:49:04 node-5 puppet-agent[8914]: Reopening log files
Jul 31 21:49:04 node-5 puppet-agent[8914]: Could not request certificate: Connection refused - connect(2)
Jul 31 21:49:18 node-5 puppet-user[8993]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 31 21:49:18 node-5 puppet-user[8993]: Compiled catalog for node-5.domain.tld in environment production in 0.03 seconds
Jul 31 21:49:18 node-5 puppet-user[8993]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 31 21:49:18 node-5 puppet-user[8993]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 31 21:49:18 node-5 puppet-user[8993]: Finished catalog run in 0.54 seconds
Jul 31 21:49:20 node-5 multipathd: uevent trigger error
Jul 31 21:49:20 node-5 puppet-user[9418]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 31 21:49:20 node-5 puppet-user[9418]: Compiled catalog for node-5.domain.tld in environment production in 0.10 seconds
Jul 31 21:49:20 node-5 puppet-user[9418]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 31 21:49:20 node-5 puppet-user[9418]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 31 21:49:20 node-5 puppet-user[9418]: (/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 31 21:49:20 node-5 puppet-user[9418]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 31 21:49:20 node-5 puppet-user[9418]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 31 21:49:20 node-5 puppet-user[9418]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 31 21:49:20 node-5 puppet-user[9418]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 31 21:49:20 node-5 puppet-user[9418]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 31 21:49:20 node-5 puppet-user[9418]: Finished catalog run in 0.07 seconds
Jul 31 21:49:21 node-5 puppet-user[9888]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 31 21:49:22 node-5 puppet-user[9888]: Compiled catalog for node-5.domain.tld in environment production in 0.08 seconds
Jul 31 21:49:22 node-5 puppet-user[9888]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 31 21:49:22 node-5 puppet-user[9888]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 31 21:49:22 node-5 puppet-user[9888]: Finished catalog run in 0.03 seconds
Jul 31 21:49:23 node-5 puppet-user[10355]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 31 21:49:23 node-5 puppet-user[10355]: Compiled catalog for node-5.domain.tld in environment production in 0.03 seconds
Jul 31 21:49:24 node-5 puppet-user[10355]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 31 21:49:24 node-5 puppet-user[10355]: Finished catalog run in 0.03 seconds
Jul 31 21:49:25 node-5 puppet-user[10806]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 31 21:49:25 node-5 puppet-user[10806]: Compiled catalog for node-5.domain.tld in environment production in 0.17 seconds
Jul 31 21:49:25 node-5 puppet-user[10806]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 31 21:49:27 node-5 puppet-user[10806]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Jul 31 21:49:27 node-5 puppet-user[10806]: Finished catalog run in 2.19 seconds
Jul 31 21:49:28 node-5 puppet-user[11344]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 31 21:49:29 node-5 puppet-user[11344]: Compiled catalog for node-5.domain.tld in environment production in 0.26 seconds
Jul 31 21:49:29 node-5 puppet-user[11344]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 31 21:49:29 node-5 puppet-user[11344]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Jul 31 21:49:29 node-5 puppet-user[11344]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 31 21:49:29 node-5 puppet-user[11344]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 31 21:49:29 node-5 puppet-user[11344]: Finished catalog run in 0.28 seconds
Jul 31 21:49:31 node-5 puppet-user[11850]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 31 21:49:31 node-5 puppet-user[11850]: Compiled catalog for node-5.domain.tld in environment production in 0.14 seconds
Jul 31 21:49:31 node-5 puppet-user[11850]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 31 21:49:31 node-5 kernel: [   69.560746] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 31 21:49:31 node-5 kernel: [   69.560795] 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 31 21:49:31 node-5 puppet-user[11850]: (/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 31 21:49:31 node-5 puppet-user[11850]: Finished catalog run in 0.05 seconds
Jul 31 21:49:32 node-5 puppet-user[12417]: (Scope(Class[main])) MODULAR: sync_time
Jul 31 21:49:32 node-5 puppet-user[12417]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Jul 31 21:49:33 node-5 ntpdate[12832]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 31 21:49:39 node-5 ntpdate[12832]: adjust time server 10.20.0.2 offset 0.000338 sec
Jul 31 21:49:39 node-5 puppet-user[12417]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 31 21:49:39 node-5 puppet-user[12417]: Finished catalog run in 6.16 seconds
Jul 31 21:49:44 node-5 puppet-user[13209]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 31 21:49:44 node-5 puppet-user[13209]: Compiled catalog for node-5.domain.tld in environment production in 0.08 seconds
Jul 31 21:49:44 node-5 puppet-user[13209]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 31 21:49:44 node-5 puppet-user[13209]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Jul 31 21:49:44 node-5 puppet-user[13209]: Finished catalog run in 0.06 seconds
Jul 31 21:49:46 node-5 puppet-user[13672]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 31 21:49:48 node-5 puppet-user[13672]: Compiled catalog for node-5.domain.tld in environment production in 1.64 seconds
Jul 31 21:49:48 node-5 puppet-user[13672]: (/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 31 21:49:48 node-5 puppet-user[13672]: (/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 31 21:49:48 node-5 puppet-user[13672]: (/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 31 21:49:48 node-5 puppet-user[13672]: (/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 31 21:49:48 node-5 puppet-user[13672]: (/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 31 21:49:48 node-5 puppet-user[13672]: (/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 31 21:49:48 node-5 puppet-user[13672]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 31 21:49:48 node-5 puppet-user[13672]: (/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 31 21:49:48 node-5 puppet-user[13672]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 31 21:49:48 node-5 puppet-user[13672]: (/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 31 21:49:48 node-5 puppet-user[13672]: (/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 31 21:49:48 node-5 puppet-user[13672]: (/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 31 21:49:48 node-5 puppet-user[13672]: (/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 31 21:49:48 node-5 puppet-user[13672]: (/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 31 21:49:48 node-5 puppet-user[13672]: (/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 31 21:49:48 node-5 puppet-user[13672]: (/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 31 21:49:55 node-5 kernel: [   93.793020] init: plymouth-upstart-bridge main process ended, respawning
Jul 31 21:49:55 node-5 puppet-agent[8914]: Could not run: SIGTERM
Jul 31 21:49:55 node-5 kernel: [   94.030851] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 31 21:49:55 node-5 ec2: 
Jul 31 21:49:55 node-5 ec2: #############################################################
Jul 31 21:49:55 node-5 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 31 21:49:55 node-5 ec2: 1024 7f:b7:e4:11:e8:52:04:53:93:3e:a3:21:03:e7:06:f0  root@node-5.domain.tld (DSA)
Jul 31 21:49:55 node-5 ec2: 256 96:a9:df:01:4d:2b:f2:3f:00:78:0f:14:b9:f2:a9:c2  root@node-5.domain.tld (ECDSA)
Jul 31 21:49:55 node-5 ec2: 256 af:20:01:32:bb:57:31:dc:e2:70:aa:2a:83:e5:5a:66  root@node-5.domain.tld (ED25519)
Jul 31 21:49:55 node-5 ec2: 2048 53:86:75:7e:71:54:d6:44:c7:91:70:c7:06:d8:7c:a1  root@node-5.domain.tld (RSA)
Jul 31 21:49:55 node-5 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 31 21:49:55 node-5 ec2: #############################################################
Jul 31 21:50:01 node-5 puppet-user[13672]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 31 21:50:01 node-5 puppet-user[13672]: Finished catalog run in 13.18 seconds
Jul 31 21:50:01 node-5 CRON[14751]: (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 31 21:50:02 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 21:50:02 node-5 nailgun-agent: I, [2016-07-31T21:50:02.711145 #14754]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 31 21:50:03 node-5 puppet-user[14786]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 31 21:50:03 node-5 puppet-user[14786]: Compiled catalog for node-5.domain.tld in environment production in 0.12 seconds
Jul 31 21:50:08 node-5 puppet-user[14786]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 31 21:50:15 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 21:50:15 node-5 nailgun-agent: I, [2016-07-31T21:50:15.934349 #14754]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 31 21:50:38 node-5 puppet-user[14786]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 31 21:50:38 node-5 puppet-user[14786]: Finished catalog run in 34.56 seconds
Jul 31 21:50:40 node-5 puppet-user[17548]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 31 21:50:40 node-5 puppet-user[17548]: Compiled catalog for node-5.domain.tld in environment production in 0.58 seconds
Jul 31 21:50:40 node-5 puppet-user[17548]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 31 21:50:40 node-5 puppet-user[17548]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 31 21:50:40 node-5 puppet-user[17548]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 31 21:50:41 node-5 puppet-user[17548]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 31 21:50:41 node-5 puppet-user[17548]: Finished catalog run in 0.09 seconds
Jul 31 21:50:42 node-5 puppet-user[18005]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 31 21:50:43 node-5 puppet-user[18005]: Compiled catalog for node-5.domain.tld in environment production in 0.85 seconds
Jul 31 21:50:43 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 31 21:50:43 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 31 21:50:43 node-5 crontab[18449]: (root) LIST (root)
Jul 31 21:50:43 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 31 21:50:43 node-5 crontab[18450]: (root) REPLACE (root)
Jul 31 21:50:46 node-5 puppet-user[18005]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/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 31 21:50:47 node-5 puppet-user[18005]: (/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 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/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 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/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 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/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 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 31 21:50:47 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 31 21:50:48 node-5 puppet-user[18005]: (/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 31 21:50:48 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 31 21:50:48 node-5 puppet-user[18005]: (/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 31 21:50:48 node-5 puppet-user[18005]: (/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 31 21:50:48 node-5 puppet-user[18005]: (/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 31 21:50:48 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 31 21:50:48 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 31 21:50:48 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 31 21:50:48 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 31 21:50:48 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 31 21:50:48 node-5 puppet-user[18005]: (/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 31 21:50:48 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 31 21:50:48 node-5 puppet-user[18005]: (/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 31 21:50:48 node-5 puppet-user[18005]: (/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 31 21:50:48 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 31 21:50:48 node-5 puppet-user[18005]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 31 21:50:48 node-5 puppet-user[18005]: (/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 31 21:50:48 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8365" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:48 node-5 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 31 21:50:50 node-5 multipathd: uevent trigger error
<27>Jul 31 21:50:50 node-5 multipathd: uevent trigger error
<27>Jul 31 21:50:50 node-5 multipathd: uevent trigger error
<27>Jul 31 21:50:50 node-5 multipathd: uevent trigger error
<27>Jul 31 21:50:50 node-5 multipathd: uevent trigger error
<27>Jul 31 21:50:50 node-5 multipathd: uevent trigger error
<27>Jul 31 21:50:50 node-5 multipathd: uevent trigger error
<27>Jul 31 21:51:08 node-5 multipathd: uevent trigger error
<27>Jul 31 21:51:08 node-5 multipathd: uevent trigger error
<27>Jul 31 21:51:08 node-5 multipathd: uevent trigger error
<27>Jul 31 21:51:08 node-5 multipathd: uevent trigger error
<27>Jul 31 21:51:08 node-5 multipathd: uevent trigger error
<27>Jul 31 21:51:08 node-5 multipathd: uevent trigger error
<27>Jul 31 21:51:57 node-5 multipathd: uevent trigger error
<27>Jul 31 21:51:57 node-5 multipathd: uevent trigger error
<27>Jul 31 21:51:57 node-5 multipathd: uevent trigger error
<27>Jul 31 21:51:57 node-5 multipathd: uevent trigger error
<27>Jul 31 21:51:59 node-5 multipathd: uevent trigger error
<27>Jul 31 21:51:59 node-5 multipathd: uevent trigger error
<27>Jul 31 21:51:59 node-5 multipathd: uevent trigger error
<27>Jul 31 21:52:00 node-5 multipathd: uevent trigger error
<27>Jul 31 21:52:00 node-5 multipathd: uevent trigger error
<27>Jul 31 21:52:00 node-5 multipathd: uevent trigger error
<27>Jul 31 21:52:42 node-5 ntpdate[2181]: no servers can be used, exiting
<27>Jul 31 21:52:43 node-5 ntpdate[2461]: no servers can be used, exiting
<27>Jul 31 21:53:14 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:14 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:14 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:14 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:14 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:17 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:17 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:17 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:18 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:18 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:28 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:28 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:28 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:28 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:28 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:28 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:31 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:31 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:31 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:31 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:31 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:38 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:38 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:38 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:38 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:38 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:58 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:58 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:58 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:58 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:58 node-5 multipathd: uevent trigger error
<27>Jul 31 21:53:58 node-5 multipathd: uevent trigger error
<43>Jul 31 21:53:58 node-5 apache2_error [Sun Jul 31 21:53:50.143658 2016] [mpm_event:notice] [pid 12247:tid 139670950180736] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 31 21:53:58 node-5 apache2_error [Sun Jul 31 21:53:50.143812 2016] [core:notice] [pid 12247:tid 139670950180736] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 31 21:53:58 node-5 apache2_error [Sun Jul 31 21:53:53.148276 2016] [mpm_event:notice] [pid 12247:tid 139670950180736] AH00491: caught SIGTERM, shutting down
<43>Jul 31 21:53:58 node-5 apache2_error [Sun Jul 31 21:53:54.239944 2016] [mpm_worker:notice] [pid 12596:tid 140098745276288] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 31 21:53:58 node-5 apache2_error [Sun Jul 31 21:53:54.239991 2016] [core:notice] [pid 12596:tid 140098745276288] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 21:54:34 node-5 multipathd: uevent trigger error
<27>Jul 31 21:54:34 node-5 multipathd: uevent trigger error
<27>Jul 31 21:54:34 node-5 multipathd: uevent trigger error
<27>Jul 31 21:54:34 node-5 multipathd: uevent trigger error
<27>Jul 31 21:54:34 node-5 multipathd: uevent trigger error
<43>Jul 31 21:54:38 node-5 apache2_error [Sun Jul 31 21:54:31.872159 2016] [mpm_worker:notice] [pid 12596:tid 140098745276288] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 21:54:38 node-5 apache2_error [Sun Jul 31 21:54:31.880772 2016] [mpm_worker:warn] [pid 12596:tid 140098745276288] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 21:54:38 node-5 apache2_error [Sun Jul 31 21:54:31.881518 2016] [mpm_worker:notice] [pid 12596:tid 140098745276288] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 31 21:54:38 node-5 apache2_error [Sun Jul 31 21:54:31.881531 2016] [core:notice] [pid 12596:tid 140098745276288] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 21:54:53 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:27 node-5 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 31 21:55:32 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:32 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:32 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:32 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:32 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:36 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:36 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:36 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:36 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:36 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:47 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:47 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:47 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:47 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:47 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:47 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:55 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:55 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:55 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:55 node-5 multipathd: uevent trigger error
<27>Jul 31 21:55:55 node-5 multipathd: uevent trigger error
<129>Jul 31 21:55:59 node-5 haproxy[30389]: Backup Server mysqld/node-5 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 31 21:56:00 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:00 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:00 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:00 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:00 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:04 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:04 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:04 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:04 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:04 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:04 node-5 multipathd: uevent trigger error
<129>Jul 31 21:56:07 node-5 haproxy[32564]: Backup Server mysqld/node-5 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 31 21:56:08 node-5 haproxy[32564]: Server object-storage/node-5 is DOWN, reason: Layer4 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 31 21:56:09 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:09 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:09 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:09 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:09 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:09 node-5 multipathd: uevent trigger error
<129>Jul 31 21:56:12 node-5 haproxy[1280]: Server neutron/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:12 node-5 haproxy[1280]: Backup Server mysqld/node-5 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 31 21:56:13 node-5 haproxy[1280]: Server object-storage/node-5 is DOWN, reason: Layer4 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 31 21:56:14 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:14 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:14 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:14 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:14 node-5 multipathd: uevent trigger error
<129>Jul 31 21:56:17 node-5 haproxy[2422]: Server keystone-1/node-5 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 31 21:56:17 node-5 haproxy[2422]: Server keystone-2/node-5 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 31 21:56:18 node-5 haproxy[2431]: Server neutron/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:18 node-5 haproxy[2431]: Backup Server mysqld/node-5 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 31 21:56:19 node-5 haproxy[2431]: Server object-storage/node-5 is DOWN, reason: Layer4 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 31 21:56:20 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:20 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:20 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:20 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:20 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:20 node-5 multipathd: uevent trigger error
<129>Jul 31 21:56:22 node-5 haproxy[3555]: Server keystone-1/node-5 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 31 21:56:23 node-5 haproxy[3564]: Server keystone-2/node-5 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 31 21:56:23 node-5 haproxy[3564]: Server neutron/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:23 node-5 haproxy[3564]: Backup Server mysqld/node-5 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 31 21:56:24 node-5 haproxy[3564]: Server object-storage/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:24 node-5 haproxy[3564]: Server aodh/node-5 is DOWN, reason: Layer4 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 31 21:56:25 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:25 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:25 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:25 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:25 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:25 node-5 multipathd: uevent trigger error
<129>Jul 31 21:56:26 node-5 haproxy[3564]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:56:26 node-5 haproxy[3564]: Server aodh/node-4 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 31 21:56:26 node-5 haproxy[3564]: proxy aodh has no server available!
<129>Jul 31 21:56:28 node-5 haproxy[4710]: Server keystone-1/node-5 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 31 21:56:28 node-5 haproxy[4710]: Server keystone-2/node-5 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 31 21:56:28 node-5 haproxy[4710]: Server neutron/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:28 node-5 haproxy[4710]: Backup Server mysqld/node-5 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 31 21:56:29 node-5 haproxy[4710]: Server object-storage/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:29 node-5 haproxy[4710]: Server aodh/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:29 node-5 haproxy[4710]: Server ceilometer/node-5 is DOWN, reason: Layer4 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 31 21:56:30 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:30 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:30 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:30 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:31 node-5 multipathd: uevent trigger error
<129>Jul 31 21:56:31 node-5 haproxy[4710]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:56:31 node-5 haproxy[4710]: Server aodh/node-4 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 31 21:56:31 node-5 haproxy[4710]: proxy aodh has no server available!
<129>Jul 31 21:56:31 node-5 haproxy[4710]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:56:31 node-5 haproxy[4710]: Server ceilometer/node-4 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 31 21:56:31 node-5 haproxy[4710]: proxy ceilometer has no server available!
<129>Jul 31 21:56:33 node-5 haproxy[5964]: Server keystone-1/node-5 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 31 21:56:33 node-5 haproxy[5964]: Server keystone-2/node-5 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 31 21:56:34 node-5 haproxy[5973]: Server neutron/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:34 node-5 haproxy[5973]: Backup Server mysqld/node-5 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 31 21:56:34 node-5 haproxy[5973]: Server object-storage/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:34 node-5 haproxy[5973]: Server aodh/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:35 node-5 haproxy[5973]: Server ceilometer/node-5 is DOWN, reason: Layer4 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 31 21:56:36 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:36 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:36 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:36 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:36 node-5 multipathd: uevent trigger error
<129>Jul 31 21:56:36 node-5 haproxy[5973]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:56:36 node-5 haproxy[5973]: Server aodh/node-4 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 31 21:56:36 node-5 haproxy[5973]: proxy aodh has no server available!
<129>Jul 31 21:56:37 node-5 haproxy[5973]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:56:37 node-5 haproxy[5973]: Server ceilometer/node-4 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 31 21:56:37 node-5 haproxy[5973]: proxy ceilometer has no server available!
<129>Jul 31 21:56:38 node-5 haproxy[7067]: Server keystone-1/node-5 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 31 21:56:38 node-5 haproxy[7067]: Server keystone-2/node-5 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 31 21:56:39 node-5 haproxy[7076]: Server neutron/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:39 node-5 haproxy[7076]: Backup Server mysqld/node-5 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 31 21:56:39 node-5 haproxy[7076]: Server object-storage/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:39 node-5 haproxy[7076]: Server aodh/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:40 node-5 haproxy[7076]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:40 node-5 haproxy[7076]: Server horizon/node-3 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 31 21:56:40 node-5 haproxy[7076]: Server horizon/node-4 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 31 21:56:40 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:41 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:41 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:41 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:41 node-5 multipathd: uevent trigger error
<129>Jul 31 21:56:41 node-5 haproxy[7076]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:56:41 node-5 haproxy[7076]: Server aodh/node-4 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 31 21:56:41 node-5 haproxy[7076]: proxy aodh has no server available!
<129>Jul 31 21:56:42 node-5 haproxy[7076]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:56:42 node-5 haproxy[7076]: Server ceilometer/node-4 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 31 21:56:42 node-5 haproxy[7076]: proxy ceilometer has no server available!
<129>Jul 31 21:56:44 node-5 haproxy[8387]: Server keystone-1/node-5 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 31 21:56:44 node-5 haproxy[8387]: Server keystone-2/node-5 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 31 21:56:44 node-5 haproxy[8387]: Server glance-api/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:44 node-5 haproxy[8387]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:44 node-5 haproxy[8387]: Server neutron/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:44 node-5 haproxy[8387]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:45 node-5 haproxy[8387]: Backup Server mysqld/node-5 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 31 21:56:45 node-5 haproxy[8387]: Server object-storage/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:45 node-5 haproxy[8387]: Server aodh/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:45 node-5 haproxy[8387]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:45 node-5 haproxy[8387]: Server horizon/node-3 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 31 21:56:45 node-5 haproxy[8387]: Server horizon/node-4 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 31 21:56:46 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:46 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:46 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:46 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:46 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:46 node-5 multipathd: uevent trigger error
<129>Jul 31 21:56:46 node-5 haproxy[8387]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:56:46 node-5 haproxy[8387]: Server glance-registry/node-4 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 31 21:56:46 node-5 haproxy[8387]: proxy glance-registry has no server available!
<129>Jul 31 21:56:47 node-5 haproxy[8387]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:56:47 node-5 haproxy[8387]: Server aodh/node-4 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 31 21:56:47 node-5 haproxy[8387]: proxy aodh has no server available!
<129>Jul 31 21:56:47 node-5 haproxy[8387]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:56:47 node-5 haproxy[8387]: Server ceilometer/node-4 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 31 21:56:47 node-5 haproxy[8387]: proxy ceilometer has no server available!
<129>Jul 31 21:56:49 node-5 haproxy[9631]: Server keystone-1/node-5 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 31 21:56:50 node-5 haproxy[9640]: Server keystone-2/node-5 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 31 21:56:50 node-5 haproxy[9640]: Server nova-api/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:50 node-5 haproxy[9640]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:50 node-5 haproxy[9640]: Server glance-api/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:50 node-5 haproxy[9640]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:50 node-5 haproxy[9640]: Server neutron/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:50 node-5 haproxy[9640]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:51 node-5 haproxy[9640]: Backup Server mysqld/node-5 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 31 21:56:51 node-5 haproxy[9640]: Server object-storage/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:51 node-5 haproxy[9640]: Server aodh/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:51 node-5 haproxy[9640]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:51 node-5 haproxy[9640]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:51 node-5 haproxy[9640]: Server horizon/node-3 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 31 21:56:51 node-5 haproxy[9640]: Server horizon/node-4 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 31 21:56:52 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:52 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:52 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:52 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:52 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:52 node-5 multipathd: uevent trigger error
<129>Jul 31 21:56:52 node-5 haproxy[9640]: Server glance-registry/node-3 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 31 21:56:52 node-5 haproxy[9640]: Server glance-registry/node-4 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 31 21:56:52 node-5 haproxy[9640]: proxy glance-registry has no server available!
<129>Jul 31 21:56:53 node-5 haproxy[9640]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:56:53 node-5 haproxy[9640]: Server aodh/node-4 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 31 21:56:53 node-5 haproxy[9640]: proxy aodh has no server available!
<129>Jul 31 21:56:53 node-5 haproxy[9640]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:56:53 node-5 haproxy[9640]: Server ceilometer/node-4 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 31 21:56:53 node-5 haproxy[9640]: proxy ceilometer has no server available!
<129>Jul 31 21:56:53 node-5 haproxy[9640]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:56:53 node-5 haproxy[9640]: Server nova-novncproxy/node-4 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 31 21:56:53 node-5 haproxy[9640]: proxy nova-novncproxy has no server available!
<27>Jul 31 21:56:53 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Jul 31 21:56:55 node-5 haproxy[10827]: Server keystone-1/node-5 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 31 21:56:55 node-5 haproxy[10827]: Server keystone-2/node-5 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 31 21:56:55 node-5 haproxy[10827]: Server nova-api/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:55 node-5 haproxy[10827]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:55 node-5 haproxy[10827]: Backup Server cinder-api/node-5 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 31 21:56:55 node-5 haproxy[10827]: Server glance-api/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:56 node-5 haproxy[10836]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:56 node-5 haproxy[10836]: Server neutron/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:56 node-5 haproxy[10836]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:56 node-5 haproxy[10836]: Backup Server mysqld/node-5 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 31 21:56:56 node-5 haproxy[10836]: Server object-storage/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:56 node-5 haproxy[10836]: Server aodh/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:56 node-5 haproxy[10836]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:56 node-5 haproxy[10836]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection 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 31 21:56:57 node-5 haproxy[10836]: Server horizon/node-3 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 31 21:56:57 node-5 haproxy[10836]: Server horizon/node-4 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 31 21:56:57 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:57 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:57 node-5 multipathd: uevent trigger error
<27>Jul 31 21:56:57 node-5 multipathd: uevent trigger error
<129>Jul 31 21:56:58 node-5 haproxy[10836]: Server glance-registry/node-3 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 31 21:56:58 node-5 haproxy[10836]: Server glance-registry/node-4 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 31 21:56:58 node-5 haproxy[10836]: proxy glance-registry has no server available!
<129>Jul 31 21:56:58 node-5 haproxy[10836]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:56:58 node-5 haproxy[10836]: Server aodh/node-4 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 31 21:56:58 node-5 haproxy[10836]: proxy aodh has no server available!
<129>Jul 31 21:56:58 node-5 haproxy[10836]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:56:58 node-5 haproxy[10836]: Server ceilometer/node-4 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 31 21:56:58 node-5 haproxy[10836]: proxy ceilometer has no server available!
<129>Jul 31 21:56:58 node-5 haproxy[10836]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:56:58 node-5 haproxy[10836]: Server nova-novncproxy/node-4 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 31 21:56:58 node-5 haproxy[10836]: proxy nova-novncproxy has no server available!
<129>Jul 31 21:57:00 node-5 haproxy[12002]: Server keystone-1/node-5 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 31 21:57:00 node-5 haproxy[12002]: Server keystone-2/node-5 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 31 21:57:01 node-5 haproxy[12011]: Server nova-api/node-5 is DOWN, reason: Layer4 connection 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 31 21:57:01 node-5 haproxy[12011]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection 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 31 21:57:01 node-5 haproxy[12011]: Backup Server cinder-api/node-5 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 31 21:57:01 node-5 haproxy[12011]: Server glance-api/node-5 is DOWN, reason: Layer4 connection 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 31 21:57:01 node-5 haproxy[12011]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection 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 31 21:57:01 node-5 haproxy[12011]: Server neutron/node-5 is DOWN, reason: Layer4 connection 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 31 21:57:01 node-5 haproxy[12011]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection 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 31 21:57:01 node-5 haproxy[12011]: Backup Server mysqld/node-5 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 31 21:57:01 node-5 haproxy[12011]: Server object-storage/node-5 is DOWN, reason: Layer4 connection 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 31 21:57:02 node-5 haproxy[12011]: Server aodh/node-5 is DOWN, reason: Layer4 connection 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 31 21:57:02 node-5 haproxy[12011]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection 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 31 21:57:02 node-5 haproxy[12011]: Server heat-api/node-5 is DOWN, reason: Layer4 connection 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 31 21:57:02 node-5 haproxy[12011]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection 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 31 21:57:02 node-5 haproxy[12011]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection 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 31 21:57:02 node-5 haproxy[12011]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection 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 31 21:57:02 node-5 haproxy[12011]: Server horizon/node-3 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 31 21:57:02 node-5 haproxy[12011]: Server horizon/node-4 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 31 21:57:03 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:03 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:03 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:03 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:03 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:03 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:03 node-5 multipathd: uevent trigger error
<129>Jul 31 21:57:03 node-5 haproxy[12011]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:57:03 node-5 haproxy[12011]: Server glance-registry/node-4 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 31 21:57:03 node-5 haproxy[12011]: proxy glance-registry has no server available!
<129>Jul 31 21:57:03 node-5 haproxy[12011]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:57:04 node-5 haproxy[12011]: Server aodh/node-4 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 31 21:57:04 node-5 haproxy[12011]: proxy aodh has no server available!
<129>Jul 31 21:57:04 node-5 haproxy[12011]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:57:04 node-5 haproxy[12011]: Server ceilometer/node-4 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 31 21:57:04 node-5 haproxy[12011]: proxy ceilometer has no server available!
<129>Jul 31 21:57:04 node-5 haproxy[12011]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:57:04 node-5 haproxy[12011]: Server nova-novncproxy/node-4 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 31 21:57:04 node-5 haproxy[12011]: proxy nova-novncproxy has no server available!
<27>Jul 31 21:57:06 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:06 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:06 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:06 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:06 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:06 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:06 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:10 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:10 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:10 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:10 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:10 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:10 node-5 multipathd: uevent trigger error
<129>Jul 31 21:57:10 node-5 haproxy[12011]: Server keystone-1/node-3 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 31 21:57:10 node-5 haproxy[12011]: Server keystone-1/node-4 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 31 21:57:10 node-5 haproxy[12011]: proxy keystone-1 has no server available!
<129>Jul 31 21:57:10 node-5 haproxy[12011]: Server keystone-2/node-3 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 31 21:57:10 node-5 haproxy[12011]: Server keystone-2/node-4 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 31 21:57:10 node-5 haproxy[12011]: proxy keystone-2 has no server available!
<129>Jul 31 21:57:10 node-5 haproxy[12011]: Server nova-api/node-3 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 31 21:57:11 node-5 haproxy[12011]: Server nova-api/node-4 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 31 21:57:11 node-5 haproxy[12011]: proxy nova-api has no server available!
<129>Jul 31 21:57:11 node-5 haproxy[12011]: Server nova-metadata-api/node-3 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 31 21:57:11 node-5 haproxy[12011]: Server nova-metadata-api/node-4 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 31 21:57:11 node-5 haproxy[12011]: proxy nova-metadata-api has no server available!
<129>Jul 31 21:57:11 node-5 haproxy[12011]: Server cinder-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:57:11 node-5 haproxy[12011]: Backup Server cinder-api/node-4 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 31 21:57:11 node-5 haproxy[12011]: proxy cinder-api has no server available!
<129>Jul 31 21:57:11 node-5 haproxy[12011]: Server glance-api/node-3 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 31 21:57:11 node-5 haproxy[12011]: Server glance-api/node-4 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 31 21:57:11 node-5 haproxy[12011]: proxy glance-api has no server available!
<129>Jul 31 21:57:11 node-5 haproxy[12011]: Server glance-glare/node-3 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 31 21:57:11 node-5 haproxy[12011]: Server glance-glare/node-4 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 31 21:57:11 node-5 haproxy[12011]: proxy glance-glare has no server available!
<129>Jul 31 21:57:11 node-5 haproxy[12011]: Server neutron/node-3 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 31 21:57:11 node-5 haproxy[12011]: Server neutron/node-4 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 31 21:57:11 node-5 haproxy[12011]: proxy neutron has no server available!
<129>Jul 31 21:57:11 node-5 haproxy[12011]: Server mysqld/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 21:57:11 node-5 haproxy[12011]: Backup Server mysqld/node-4 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 31 21:57:11 node-5 haproxy[12011]: proxy mysqld has no server available!
<129>Jul 31 21:57:11 node-5 haproxy[12011]: Server object-storage/node-3 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 31 21:57:11 node-5 haproxy[12011]: Server object-storage/node-4 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 31 21:57:11 node-5 haproxy[12011]: proxy object-storage has no server available!
<129>Jul 31 21:57:12 node-5 haproxy[12011]: Server heat-api/node-3 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 31 21:57:12 node-5 haproxy[12011]: Server heat-api/node-4 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 31 21:57:12 node-5 haproxy[12011]: proxy heat-api has no server available!
<129>Jul 31 21:57:12 node-5 haproxy[12011]: Server heat-api-cfn/node-3 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 31 21:57:12 node-5 haproxy[12011]: Server heat-api-cfn/node-4 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 31 21:57:12 node-5 haproxy[12011]: proxy heat-api-cfn has no server available!
<129>Jul 31 21:57:12 node-5 haproxy[12011]: Server heat-api-cloudwatch/node-3 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 31 21:57:12 node-5 haproxy[12011]: Server heat-api-cloudwatch/node-4 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 31 21:57:12 node-5 haproxy[12011]: proxy heat-api-cloudwatch has no server available!
<27>Jul 31 21:57:14 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:14 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:14 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:14 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:14 node-5 multipathd: uevent trigger error
<27>Jul 31 21:57:47 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 31 21:57:47 node-5 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 31 21:57:54 node-5 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 21:57:54 node-5 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 31 21:57:55 node-5 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 31 21:58:13 node-5 multipathd: uevent trigger error
<27>Jul 31 21:58:13 node-5 multipathd: uevent trigger error
<27>Jul 31 21:58:13 node-5 multipathd: uevent trigger error
<27>Jul 31 21:58:13 node-5 multipathd: uevent trigger error
<27>Jul 31 21:58:13 node-5 multipathd: uevent trigger error
<27>Jul 31 21:58:13 node-5 multipathd: uevent trigger error
<27>Jul 31 21:58:28 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 31 21:58:49 node-5 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 31 21:58:51 node-5 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 31 22:00:07 node-5 multipathd: uevent trigger error
<27>Jul 31 22:00:07 node-5 multipathd: uevent trigger error
<27>Jul 31 22:00:07 node-5 multipathd: uevent trigger error
<27>Jul 31 22:00:07 node-5 multipathd: uevent trigger error
<27>Jul 31 22:00:07 node-5 multipathd: uevent trigger error
<27>Jul 31 22:01:27 node-5 multipathd: uevent trigger error
<27>Jul 31 22:01:27 node-5 multipathd: uevent trigger error
<27>Jul 31 22:01:27 node-5 multipathd: uevent trigger error
<27>Jul 31 22:01:27 node-5 multipathd: uevent trigger error
<27>Jul 31 22:01:27 node-5 multipathd: uevent trigger error
<27>Jul 31 22:01:27 node-5 multipathd: uevent trigger error
<11>Jul 31 22:02:31 node-5 epmd: epmd: node name already occupied rabbitmq-cli-77
<27>Jul 31 22:04:05 node-5 multipathd: uevent trigger error
<27>Jul 31 22:04:05 node-5 multipathd: uevent trigger error
<27>Jul 31 22:04:05 node-5 multipathd: uevent trigger error
<27>Jul 31 22:04:05 node-5 multipathd: uevent trigger error
<27>Jul 31 22:04:05 node-5 multipathd: uevent trigger error
<27>Jul 31 22:04:05 node-5 multipathd: uevent trigger error
<43>Jul 31 22:05:19 node-5 apache2_error [Sun Jul 31 22:05:14.111630 2016] [mpm_worker:notice] [pid 12596:tid 140098745276288] AH00295: caught SIGTERM, shutting down
<43>Jul 31 22:05:19 node-5 apache2_error [Sun Jul 31 22:05:14.855340 2016] [mpm_worker:notice] [pid 22072:tid 140253536626560] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 22:05:19 node-5 apache2_error [Sun Jul 31 22:05:14.855374 2016] [core:notice] [pid 22072:tid 140253536626560] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 31 22:05:49 node-5 apache2_error [Sun Jul 31 22:05:46.784847 2016] [mpm_worker:notice] [pid 22072:tid 140253536626560] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 22:05:49 node-5 apache2_error [Sun Jul 31 22:05:46.789165 2016] [mpm_worker:warn] [pid 22072:tid 140253536626560] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 22:05:49 node-5 apache2_error [Sun Jul 31 22:05:46.793074 2016] [mpm_worker:notice] [pid 22072:tid 140253536626560] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 22:05:49 node-5 apache2_error [Sun Jul 31 22:05:46.793096 2016] [core:notice] [pid 22072:tid 140253536626560] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 22:05:52 node-5 multipathd: uevent trigger error
<27>Jul 31 22:05:52 node-5 multipathd: uevent trigger error
<27>Jul 31 22:05:52 node-5 multipathd: uevent trigger error
<27>Jul 31 22:05:52 node-5 multipathd: uevent trigger error
<27>Jul 31 22:05:52 node-5 multipathd: uevent trigger error
<27>Jul 31 22:05:52 node-5 multipathd: uevent trigger error
<27>Jul 31 22:06:48 node-5 multipathd: uevent trigger error
<27>Jul 31 22:06:48 node-5 multipathd: uevent trigger error
<27>Jul 31 22:06:48 node-5 multipathd: uevent trigger error
<27>Jul 31 22:06:48 node-5 multipathd: uevent trigger error
<11>Jul 31 22:07:48 node-5 epmd: epmd: node name already occupied rabbitmq-cli-77
<27>Jul 31 22:08:02 node-5 multipathd: uevent trigger error
<27>Jul 31 22:08:02 node-5 multipathd: uevent trigger error
<27>Jul 31 22:08:02 node-5 multipathd: uevent trigger error
<27>Jul 31 22:08:02 node-5 multipathd: uevent trigger error
<27>Jul 31 22:08:02 node-5 multipathd: uevent trigger error
<11>Jul 31 22:08:05 node-5 epmd: epmd: node name already occupied rabbitmq-cli-77
<27>Jul 31 22:12:44 node-5 multipathd: uevent trigger error
<27>Jul 31 22:12:44 node-5 multipathd: uevent trigger error
<27>Jul 31 22:12:44 node-5 multipathd: uevent trigger error
<27>Jul 31 22:12:44 node-5 multipathd: uevent trigger error
<27>Jul 31 22:12:44 node-5 multipathd: uevent trigger error
<27>Jul 31 22:12:44 node-5 multipathd: uevent trigger error
<27>Jul 31 22:14:57 node-5 multipathd: uevent trigger error
<27>Jul 31 22:14:57 node-5 multipathd: uevent trigger error
<27>Jul 31 22:14:57 node-5 multipathd: uevent trigger error
<27>Jul 31 22:14:57 node-5 multipathd: uevent trigger error
<27>Jul 31 22:14:57 node-5 multipathd: uevent trigger error
<27>Jul 31 22:14:57 node-5 multipathd: uevent trigger error
<27>Jul 31 22:16:04 node-5 multipathd: uevent trigger error
<27>Jul 31 22:16:04 node-5 multipathd: uevent trigger error
<27>Jul 31 22:16:04 node-5 multipathd: uevent trigger error
<27>Jul 31 22:16:04 node-5 multipathd: uevent trigger error
<27>Jul 31 22:16:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:16:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:16:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:16:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:16:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:16:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:16:49 node-5 multipathd: uevent trigger error
<27>Jul 31 22:16:49 node-5 multipathd: uevent trigger error
<27>Jul 31 22:16:49 node-5 multipathd: uevent trigger error
<27>Jul 31 22:16:49 node-5 multipathd: uevent trigger error
<27>Jul 31 22:16:49 node-5 multipathd: uevent trigger error
<27>Jul 31 22:16:49 node-5 multipathd: uevent trigger error
<27>Jul 31 22:17:01 node-5 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Jul 31 22:17:01 node-5 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Jul 31 22:17:01 node-5 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Jul 31 22:17:02 node-5 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Jul 31 22:17:02 node-5 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Jul 31 22:17:03 node-5 multipathd: uevent trigger error
<27>Jul 31 22:17:03 node-5 multipathd: uevent trigger error
<27>Jul 31 22:17:03 node-5 multipathd: uevent trigger error
<27>Jul 31 22:17:03 node-5 multipathd: uevent trigger error
<27>Jul 31 22:17:03 node-5 multipathd: uevent trigger error
<43>Jul 31 22:17:50 node-5 apache2_error [Sun Jul 31 22:17:48.881443 2016] [mpm_worker:notice] [pid 22072:tid 140253536626560] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 22:17:50 node-5 apache2_error [Sun Jul 31 22:17:49.268333 2016] [mpm_worker:warn] [pid 22072:tid 140253536626560] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 22:17:50 node-5 apache2_error [Sun Jul 31 22:17:49.274854 2016] [mpm_worker:notice] [pid 22072:tid 140253536626560] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 22:17:50 node-5 apache2_error [Sun Jul 31 22:17:49.274882 2016] [core:notice] [pid 22072:tid 140253536626560] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 22:18:29 node-5 multipathd: uevent trigger error
<27>Jul 31 22:18:29 node-5 multipathd: uevent trigger error
<27>Jul 31 22:18:29 node-5 multipathd: uevent trigger error
<27>Jul 31 22:18:29 node-5 multipathd: uevent trigger error
<27>Jul 31 22:18:29 node-5 multipathd: uevent trigger error
<27>Jul 31 22:18:29 node-5 multipathd: uevent trigger error
<27>Jul 31 22:18:30 node-5 multipathd: uevent trigger error
<27>Jul 31 22:18:30 node-5 multipathd: uevent trigger error
<43>Jul 31 22:18:30 node-5 apache2_error [Sun Jul 31 22:18:26.068194 2016] [mpm_worker:notice] [pid 22072:tid 140253536626560] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 22:18:30 node-5 apache2_error [Sun Jul 31 22:18:26.453185 2016] [mpm_worker:warn] [pid 22072:tid 140253536626560] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 22:18:30 node-5 apache2_error [Sun Jul 31 22:18:26.466504 2016] [mpm_worker:notice] [pid 22072:tid 140253536626560] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 22:18:30 node-5 apache2_error [Sun Jul 31 22:18:26.466532 2016] [core:notice] [pid 22072:tid 140253536626560] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 22:18:48 node-5 multipathd: uevent trigger error
<27>Jul 31 22:18:48 node-5 multipathd: uevent trigger error
<27>Jul 31 22:18:48 node-5 multipathd: uevent trigger error
<27>Jul 31 22:18:48 node-5 multipathd: uevent trigger error
<27>Jul 31 22:18:48 node-5 multipathd: uevent trigger error
<27>Jul 31 22:18:48 node-5 multipathd: uevent trigger error
<27>Jul 31 22:19:04 node-5 multipathd: uevent trigger error
<27>Jul 31 22:19:05 node-5 multipathd: uevent trigger error
<27>Jul 31 22:19:05 node-5 multipathd: uevent trigger error
<27>Jul 31 22:19:17 node-5 multipathd: uevent trigger error
<27>Jul 31 22:19:17 node-5 multipathd: uevent trigger error
<27>Jul 31 22:19:17 node-5 multipathd: uevent trigger error
<27>Jul 31 22:19:17 node-5 multipathd: uevent trigger error
<27>Jul 31 22:19:17 node-5 multipathd: uevent trigger error
<27>Jul 31 22:19:17 node-5 multipathd: sda: spurious uevent, path already in pathvec
<27>Jul 31 22:20:06 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:06 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:06 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:06 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:06 node-5 multipathd: uevent trigger error
<11>Jul 31 22:20:07 node-5 epmd: epmd: node name already occupied rabbitmq-cli-77
<27>Jul 31 22:20:11 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:11 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:11 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:11 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:11 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:11 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:16 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:16 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:16 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:16 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:16 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:16 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:28 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:28 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:28 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:28 node-5 multipathd: uevent trigger error
<27>Jul 31 22:20:28 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:17 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:17 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:17 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:17 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:17 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:27 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:27 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:27 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:27 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:27 node-5 multipathd: uevent trigger error
<11>Jul 31 22:21:37 node-5 liberasurecode[50606]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:37 node-5 liberasurecode[50606]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:37 node-5 liberasurecode[50606]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:37 node-5 liberasurecode[50606]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:37 node-5 liberasurecode[50636]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:37 node-5 liberasurecode[50636]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:37 node-5 liberasurecode[50636]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:37 node-5 liberasurecode[50636]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:39 node-5 liberasurecode[51072]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:39 node-5 liberasurecode[51072]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:39 node-5 liberasurecode[51072]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:39 node-5 liberasurecode[51072]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:44 node-5 liberasurecode[51826]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:44 node-5 liberasurecode[51826]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:44 node-5 liberasurecode[51826]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:44 node-5 liberasurecode[51826]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:44 node-5 liberasurecode[51865]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:44 node-5 liberasurecode[51865]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:44 node-5 liberasurecode[51865]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:44 node-5 liberasurecode[51865]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[51905]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[51905]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[51905]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[51905]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[51971]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[51971]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[51971]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[51971]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[52007]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[52007]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[52007]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[52007]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[52020]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[52020]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[52020]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[52020]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[52041]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[52041]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[52041]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:45 node-5 liberasurecode[52041]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:47 node-5 epmd: epmd: node name already occupied rabbitmq-cli-77
<27>Jul 31 22:21:51 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:51 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:51 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:51 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:51 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:56 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:56 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:56 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:56 node-5 multipathd: uevent trigger error
<27>Jul 31 22:21:56 node-5 multipathd: uevent trigger error
<27>Jul 31 22:22:01 node-5 multipathd: uevent trigger error
<27>Jul 31 22:22:01 node-5 multipathd: uevent trigger error
<27>Jul 31 22:22:01 node-5 multipathd: uevent trigger error
<27>Jul 31 22:22:01 node-5 multipathd: uevent trigger error
<27>Jul 31 22:22:01 node-5 multipathd: uevent trigger error
<27>Jul 31 22:22:06 node-5 multipathd: uevent trigger error
<27>Jul 31 22:22:06 node-5 multipathd: uevent trigger error
<27>Jul 31 22:22:06 node-5 multipathd: uevent trigger error
<27>Jul 31 22:22:06 node-5 multipathd: uevent trigger error
<27>Jul 31 22:22:06 node-5 multipathd: uevent trigger error
<11>Jul 31 22:23:09 node-5 epmd: epmd: node name already occupied rabbitmq-cli-77
<27>Jul 31 22:24:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:24:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:24:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:24:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:24:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:24:43 node-5 multipathd: uevent trigger error
<27>Jul 31 22:24:43 node-5 multipathd: uevent trigger error
<27>Jul 31 22:24:43 node-5 multipathd: uevent trigger error
<27>Jul 31 22:24:43 node-5 multipathd: uevent trigger error
<27>Jul 31 22:24:43 node-5 multipathd: uevent trigger error
<27>Jul 31 22:24:57 node-5 multipathd: uevent trigger error
<27>Jul 31 22:24:57 node-5 multipathd: uevent trigger error
<27>Jul 31 22:24:57 node-5 multipathd: uevent trigger error
<27>Jul 31 22:24:57 node-5 multipathd: uevent trigger error
<27>Jul 31 22:24:57 node-5 multipathd: uevent trigger error
<27>Jul 31 22:24:57 node-5 multipathd: uevent trigger error
<11>Jul 31 22:25:01 node-5 liberasurecode[86496]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:25:01 node-5 liberasurecode[86496]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:25:01 node-5 liberasurecode[86496]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:25:01 node-5 liberasurecode[86496]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 31 22:25:01 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:01 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:01 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:01 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:01 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:15 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:15 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:15 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:15 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:15 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:29 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:29 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:29 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:29 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:29 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:33 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:33 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:33 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:33 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:33 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:38 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:42 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:42 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:42 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:42 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:42 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:47 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:47 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:47 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:47 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:47 node-5 multipathd: uevent trigger error
<27>Jul 31 22:25:47 node-5 multipathd: uevent trigger error
<11>Jul 31 22:26:34 node-5 epmd: epmd: node name already occupied rabbitmq-cli-77
<27>Jul 31 22:27:27 node-5 multipathd: uevent trigger error
<27>Jul 31 22:27:27 node-5 multipathd: uevent trigger error
<27>Jul 31 22:27:27 node-5 multipathd: uevent trigger error
<27>Jul 31 22:27:28 node-5 multipathd: uevent trigger error
<27>Jul 31 22:27:28 node-5 multipathd: uevent trigger error
<11>Jul 31 22:27:30 node-5 epmd: epmd: node name already occupied rabbitmq-cli-77
<27>Jul 31 22:27:36 node-5 multipathd: uevent trigger error
<27>Jul 31 22:27:36 node-5 multipathd: uevent trigger error
<27>Jul 31 22:27:36 node-5 multipathd: uevent trigger error
<27>Jul 31 22:27:36 node-5 multipathd: uevent trigger error
<27>Jul 31 22:27:36 node-5 multipathd: uevent trigger error
<27>Jul 31 22:27:46 node-5 multipathd: uevent trigger error
<27>Jul 31 22:27:46 node-5 multipathd: uevent trigger error
<27>Jul 31 22:27:46 node-5 multipathd: uevent trigger error
<27>Jul 31 22:27:46 node-5 multipathd: uevent trigger error
<27>Jul 31 22:27:46 node-5 multipathd: uevent trigger error
<27>Jul 31 22:27:46 node-5 multipathd: uevent trigger error
<129>Jul 31 22:27:57 node-5 haproxy[117083]: 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 31 22:27:57 node-5 haproxy[117083]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 31 22:28:00 node-5 multipathd: uevent trigger error
<27>Jul 31 22:28:00 node-5 multipathd: uevent trigger error
<27>Jul 31 22:28:00 node-5 multipathd: uevent trigger error
<27>Jul 31 22:28:00 node-5 multipathd: uevent trigger error
<129>Jul 31 22:29:17 node-5 haproxy[117083]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<11>Jul 31 22:30:02 node-5 liberasurecode[141842]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:30:02 node-5 liberasurecode[141842]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:30:02 node-5 liberasurecode[141842]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:30:02 node-5 liberasurecode[141842]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:30:39 node-5 epmd: epmd: node name already occupied rabbitmq-cli-77
