Jul 29 06:55:11 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8367" x-info="http://www.rsyslog.com"] start
Jul 29 06:55:11 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 29 06:55:11 node-5 rsyslogd: rsyslogd's groupid changed to 104
Jul 29 06:55:11 node-5 rsyslogd: rsyslogd's userid changed to 101
Jul 29 06:55:11 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 29 06:55:11 node-5 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 29 06:55:11 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 29 06:55:11 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 29 06:55:11 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=152235d1-5ecc-4315-9e5a-cf2925ae2972 nomdmonddf nomdmonisw
Jul 29 06:55:11 node-5 kernel: [    0.000000] KERNEL supported cpus:
Jul 29 06:55:11 node-5 kernel: [    0.000000]   Intel GenuineIntel
Jul 29 06:55:11 node-5 kernel: [    0.000000]   AMD AuthenticAMD
Jul 29 06:55:11 node-5 kernel: [    0.000000]   Centaur CentaurHauls
Jul 29 06:55:11 node-5 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 29 06:55:11 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 29 06:55:11 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 29 06:55:11 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 29 06:55:11 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 29 06:55:11 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 29 06:55:11 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 29 06:55:11 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 29 06:55:11 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 29 06:55:11 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 29 06:55:11 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 29 06:55:11 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 29 06:55:11 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 29 06:55:11 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 29 06:55:11 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 29 06:55:11 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 29 06:55:11 node-5 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 29 06:55:11 node-5 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 29 06:55:11 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 29 06:55:11 node-5 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 29 06:55:11 node-5 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 29 06:55:11 node-5 kernel: [    0.000000] No AGP bridge found
Jul 29 06:55:11 node-5 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 29 06:55:11 node-5 kernel: [    0.000000] MTRR default type: write-back
Jul 29 06:55:11 node-5 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 29 06:55:11 node-5 kernel: [    0.000000]   00000-9FFFF write-back
Jul 29 06:55:11 node-5 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 29 06:55:11 node-5 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 29 06:55:11 node-5 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 29 06:55:11 node-5 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 29 06:55:11 node-5 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 29 06:55:11 node-5 kernel: [    0.000000]   2 disabled
Jul 29 06:55:11 node-5 kernel: [    0.000000]   3 disabled
Jul 29 06:55:11 node-5 kernel: [    0.000000]   4 disabled
Jul 29 06:55:11 node-5 kernel: [    0.000000]   5 disabled
Jul 29 06:55:11 node-5 kernel: [    0.000000]   6 disabled
Jul 29 06:55:11 node-5 kernel: [    0.000000]   7 disabled
Jul 29 06:55:11 node-5 kernel: [    0.000000]   8 disabled
Jul 29 06:55:11 node-5 kernel: [    0.000000]   9 disabled
Jul 29 06:55:11 node-5 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 29 06:55:11 node-5 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 29 06:55:11 node-5 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 29 06:55:11 node-5 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 29 06:55:11 node-5 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 29 06:55:11 node-5 kernel: [    0.000000] Using GB pages for direct mapping
Jul 29 06:55:11 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 29 06:55:11 node-5 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 29 06:55:11 node-5 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 29 06:55:11 node-5 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 29 06:55:11 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 29 06:55:11 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 29 06:55:11 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 29 06:55:11 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 29 06:55:11 node-5 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 29 06:55:11 node-5 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 29 06:55:11 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 29 06:55:11 node-5 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 29 06:55:11 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 29 06:55:11 node-5 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 29 06:55:11 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 29 06:55:11 node-5 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 29 06:55:11 node-5 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 29 06:55:11 node-5 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 29 06:55:11 node-5 kernel: [    0.000000] Zone ranges:
Jul 29 06:55:11 node-5 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] Movable zone start for each node
Jul 29 06:55:11 node-5 kernel: [    0.000000] Early memory node ranges
Jul 29 06:55:11 node-5 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 29 06:55:11 node-5 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 29 06:55:11 node-5 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 29 06:55:11 node-5 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 29 06:55:11 node-5 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 29 06:55:11 node-5 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 29 06:55:11 node-5 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 29 06:55:11 node-5 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 29 06:55:11 node-5 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 29 06:55:11 node-5 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 29 06:55:11 node-5 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 29 06:55:11 node-5 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 29 06:55:11 node-5 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 29 06:55:11 node-5 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 29 06:55:11 node-5 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 29 06:55:11 node-5 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 29 06:55:11 node-5 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 29 06:55:11 node-5 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 29 06:55:11 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 29 06:55:11 node-5 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 29 06:55:11 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 29 06:55:11 node-5 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 29 06:55:11 node-5 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 29 06:55:11 node-5 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 29 06:55:11 node-5 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 29 06:55:11 node-5 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 29 06:55:11 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 29 06:55:11 node-5 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 29 06:55:11 node-5 kernel: [    0.000000] Policy zone: Normal
Jul 29 06:55:11 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=152235d1-5ecc-4315-9e5a-cf2925ae2972 nomdmonddf nomdmonisw
Jul 29 06:55:11 node-5 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 29 06:55:11 node-5 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 29 06:55:11 node-5 kernel: [    0.000000] Checking aperture...
Jul 29 06:55:11 node-5 kernel: [    0.000000] No AGP bridge found
Jul 29 06:55:11 node-5 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 29 06:55:11 node-5 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 29 06:55:11 node-5 kernel: [    0.000000] Memory: 32653320K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Jul 29 06:55:11 node-5 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 29 06:55:11 node-5 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 29 06:55:11 node-5 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 29 06:55:11 node-5 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 29 06:55:11 node-5 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 29 06:55:11 node-5 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 29 06:55:11 node-5 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 29 06:55:11 node-5 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 29 06:55:11 node-5 kernel: [    0.000000] console [tty0] enabled
Jul 29 06:55:11 node-5 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 29 06:55:11 node-5 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 29 06:55:11 node-5 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 29 06:55:11 node-5 kernel: [    0.000000] hpet clockevent registered
Jul 29 06:55:11 node-5 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 29 06:55:11 node-5 kernel: [    0.004000] tsc: Detected 3491.973 MHz processor
Jul 29 06:55:11 node-5 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.94 BogoMIPS (lpj=13967892)
Jul 29 06:55:11 node-5 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 29 06:55:11 node-5 kernel: [    0.000044] Security Framework initialized
Jul 29 06:55:11 node-5 kernel: [    0.000062] AppArmor: AppArmor initialized
Jul 29 06:55:11 node-5 kernel: [    0.000063] Yama: becoming mindful.
Jul 29 06:55:11 node-5 kernel: [    0.001459] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 29 06:55:11 node-5 kernel: [    0.006359] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 29 06:55:11 node-5 kernel: [    0.008290] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 29 06:55:11 node-5 kernel: [    0.008318] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 29 06:55:11 node-5 kernel: [    0.008612] Initializing cgroup subsys memory
Jul 29 06:55:11 node-5 kernel: [    0.008620] Initializing cgroup subsys devices
Jul 29 06:55:11 node-5 kernel: [    0.008622] Initializing cgroup subsys freezer
Jul 29 06:55:11 node-5 kernel: [    0.008624] Initializing cgroup subsys blkio
Jul 29 06:55:11 node-5 kernel: [    0.008625] Initializing cgroup subsys perf_event
Jul 29 06:55:11 node-5 kernel: [    0.008628] Initializing cgroup subsys hugetlb
Jul 29 06:55:11 node-5 kernel: [    0.008647] CPU: Physical Processor ID: 0
Jul 29 06:55:11 node-5 kernel: [    0.008648] CPU: Processor Core ID: 0
Jul 29 06:55:11 node-5 kernel: [    0.008652] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 29 06:55:11 node-5 kernel: [    0.008652] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 29 06:55:11 node-5 kernel: [    0.009346] mce: CPU supports 22 MCE banks
Jul 29 06:55:11 node-5 kernel: [    0.009373] CPU0: Thermal monitoring enabled (TM1)
Jul 29 06:55:11 node-5 kernel: [    0.009394] process: using mwait in idle threads
Jul 29 06:55:11 node-5 kernel: [    0.009397] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 29 06:55:11 node-5 kernel: [    0.009397] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 29 06:55:11 node-5 kernel: [    0.009397] tlb_flushall_shift: 6
Jul 29 06:55:11 node-5 kernel: [    0.009486] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 29 06:55:11 node-5 kernel: [    0.010210] ACPI: Core revision 20131115
Jul 29 06:55:11 node-5 kernel: [    0.022883] ACPI: All ACPI Tables successfully acquired
Jul 29 06:55:11 node-5 kernel: [    0.023042] ftrace: allocating 28617 entries in 112 pages
Jul 29 06:55:11 node-5 kernel: [    0.031855] dmar: Host address width 46
Jul 29 06:55:11 node-5 kernel: [    0.031857] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 29 06:55:11 node-5 kernel: [    0.031863] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 29 06:55:11 node-5 kernel: [    0.031865] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 29 06:55:11 node-5 kernel: [    0.031869] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 29 06:55:11 node-5 kernel: [    0.031870] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 29 06:55:11 node-5 kernel: [    0.031872] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 29 06:55:11 node-5 kernel: [    0.031873] dmar: ATSR flags: 0x0
Jul 29 06:55:11 node-5 kernel: [    0.031874] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 29 06:55:11 node-5 kernel: [    0.031875] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 29 06:55:11 node-5 kernel: [    0.031991] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 29 06:55:11 node-5 kernel: [    0.031992] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 29 06:55:11 node-5 kernel: [    0.031993] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 29 06:55:11 node-5 kernel: [    0.031994] HPET id 0 under DRHD base 0xc7ffc000
Jul 29 06:55:11 node-5 kernel: [    0.031995] Your BIOS is broken and requested that x2apic be disabled.
Jul 29 06:55:11 node-5 kernel: [    0.031995] This will slightly decrease performance.
Jul 29 06:55:11 node-5 kernel: [    0.031995] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 29 06:55:11 node-5 kernel: [    0.032427] Enabled IRQ remapping in xapic mode
Jul 29 06:55:11 node-5 kernel: [    0.032428] x2apic not enabled, IRQ remapping is in xapic mode
Jul 29 06:55:11 node-5 kernel: [    0.032432] Switched APIC routing to physical flat.
Jul 29 06:55:11 node-5 kernel: [    0.033052] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 29 06:55:11 node-5 kernel: [    0.072702] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 29 06:55:11 node-5 kernel: [    0.072707] TSC deadline timer enabled
Jul 29 06:55:11 node-5 kernel: [    0.072715] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 29 06:55:11 node-5 kernel: [    0.072721] ... version:                3
Jul 29 06:55:11 node-5 kernel: [    0.072722] ... bit width:              48
Jul 29 06:55:11 node-5 kernel: [    0.072723] ... generic registers:      4
Jul 29 06:55:11 node-5 kernel: [    0.072723] ... value mask:             0000ffffffffffff
Jul 29 06:55:11 node-5 kernel: [    0.072725] ... max period:             0000ffffffffffff
Jul 29 06:55:11 node-5 kernel: [    0.072725] ... fixed-purpose events:   3
Jul 29 06:55:11 node-5 kernel: [    0.072726] ... event mask:             000000070000000f
Jul 29 06:55:11 node-5 kernel: [    0.074164] x86: Booting SMP configuration:
Jul 29 06:55:11 node-5 kernel: [    0.088367] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 29 06:55:11 node-5 kernel: [    0.074166] .... node  #0, CPUs:        #1  #2  #3
Jul 29 06:55:11 node-5 kernel: [    0.116278] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 29 06:55:11 node-5 kernel: [    0.270247] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 29 06:55:11 node-5 kernel: [    0.325861] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 29 06:55:11 node-5 kernel: [    0.382416] x86: Booted up 2 nodes, 16 CPUs
Jul 29 06:55:11 node-5 kernel: [    0.382420] smpboot: Total of 16 processors activated (111755.33 BogoMIPS)
Jul 29 06:55:11 node-5 kernel: [    0.405902] devtmpfs: initialized
Jul 29 06:55:11 node-5 kernel: [    0.409005] EVM: security.selinux
Jul 29 06:55:11 node-5 kernel: [    0.409006] EVM: security.SMACK64
Jul 29 06:55:11 node-5 kernel: [    0.409007] EVM: security.ima
Jul 29 06:55:11 node-5 kernel: [    0.409008] EVM: security.capability
Jul 29 06:55:11 node-5 kernel: [    0.409058] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 29 06:55:11 node-5 kernel: [    0.409727] pinctrl core: initialized pinctrl subsystem
Jul 29 06:55:11 node-5 kernel: [    0.409788] regulator-dummy: no parameters
Jul 29 06:55:11 node-5 kernel: [    0.409819] RTC time:  6:54:36, date: 07/29/16
Jul 29 06:55:11 node-5 kernel: [    0.409853] NET: Registered protocol family 16
Jul 29 06:55:11 node-5 kernel: [    0.409936] cpuidle: using governor ladder
Jul 29 06:55:11 node-5 kernel: [    0.409937] cpuidle: using governor menu
Jul 29 06:55:11 node-5 kernel: [    0.409972] ACPI: bus type PCI registered
Jul 29 06:55:11 node-5 kernel: [    0.409974] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 29 06:55:11 node-5 kernel: [    0.410019] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 29 06:55:11 node-5 kernel: [    0.410022] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 29 06:55:11 node-5 kernel: [    0.423749] PCI: Using configuration type 1 for base access
Jul 29 06:55:11 node-5 kernel: [    0.424738] bio: create slab <bio-0> at 0
Jul 29 06:55:11 node-5 kernel: [    0.425014] ACPI: Added _OSI(Module Device)
Jul 29 06:55:11 node-5 kernel: [    0.425016] ACPI: Added _OSI(Processor Device)
Jul 29 06:55:11 node-5 kernel: [    0.425017] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 29 06:55:11 node-5 kernel: [    0.425018] ACPI: Added _OSI(Processor Aggregator Device)
Jul 29 06:55:11 node-5 kernel: [    0.437685] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 29 06:55:11 node-5 kernel: [    0.449320] ACPI: Interpreter enabled
Jul 29 06:55:11 node-5 kernel: [    0.449325] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 29 06:55:11 node-5 kernel: [    0.449329] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 29 06:55:11 node-5 kernel: [    0.449332] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 29 06:55:11 node-5 kernel: [    0.449338] ACPI: (supports S0 S4 S5)
Jul 29 06:55:11 node-5 kernel: [    0.449340] ACPI: Using IOAPIC for interrupt routing
Jul 29 06:55:11 node-5 kernel: [    0.449379] HEST: Table parsing has been initialized.
Jul 29 06:55:11 node-5 kernel: [    0.449382] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 29 06:55:11 node-5 kernel: [    0.449933] ACPI: No dock devices found.
Jul 29 06:55:11 node-5 kernel: [    0.461564] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 29 06:55:11 node-5 kernel: [    0.461568] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 06:55:11 node-5 kernel: [    0.461572] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 29 06:55:11 node-5 kernel: [    0.461598] PCI host bridge to bus 0000:ff
Jul 29 06:55:11 node-5 kernel: [    0.461600] pci_bus 0000:ff: root bus resource [bus ff]
Jul 29 06:55:11 node-5 kernel: [    0.461608] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.461645] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 29 06:55:11 node-5 kernel: [    0.461675] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.461710] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.461739] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 29 06:55:11 node-5 kernel: [    0.461769] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 29 06:55:11 node-5 kernel: [    0.461800] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.461829] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.461860] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.461887] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.461914] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.461940] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.461968] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.461994] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462020] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462046] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462075] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462102] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462128] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 29 06:55:11 node-5 kernel: [    0.462156] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462181] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 29 06:55:11 node-5 kernel: [    0.462206] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462232] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462262] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 29 06:55:11 node-5 kernel: [    0.462296] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462327] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462356] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462386] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462417] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462448] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462478] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462508] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462538] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462571] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462603] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462636] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462669] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462699] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462726] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462759] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462792] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462832] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462865] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462897] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462928] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462956] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.462986] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463017] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463050] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463080] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463111] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463140] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463169] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463198] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463228] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463259] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463291] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463348] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 29 06:55:11 node-5 kernel: [    0.463350] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 06:55:11 node-5 kernel: [    0.463353] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 29 06:55:11 node-5 kernel: [    0.463371] PCI host bridge to bus 0000:7f
Jul 29 06:55:11 node-5 kernel: [    0.463373] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 29 06:55:11 node-5 kernel: [    0.463378] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463405] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 29 06:55:11 node-5 kernel: [    0.463434] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463463] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463485] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 29 06:55:11 node-5 kernel: [    0.463514] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 29 06:55:11 node-5 kernel: [    0.463541] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463568] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463591] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463613] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463636] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463658] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463682] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463705] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463729] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463755] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463777] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463799] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463822] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 29 06:55:11 node-5 kernel: [    0.463846] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463868] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 29 06:55:11 node-5 kernel: [    0.463890] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463912] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463939] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 29 06:55:11 node-5 kernel: [    0.463973] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.463999] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464025] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464051] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464076] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464105] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464132] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464162] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464186] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464214] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464243] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464272] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464300] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464327] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464353] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464381] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464406] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464432] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464461] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464489] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464514] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464541] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464566] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464594] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464620] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464647] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464676] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464700] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464722] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464747] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464772] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464802] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.464828] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.466071] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 29 06:55:11 node-5 kernel: [    0.466074] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 06:55:11 node-5 kernel: [    0.467191] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 29 06:55:11 node-5 kernel: [    0.467700] PCI host bridge to bus 0000:00
Jul 29 06:55:11 node-5 kernel: [    0.467703] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 29 06:55:11 node-5 kernel: [    0.467704] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 29 06:55:11 node-5 kernel: [    0.467706] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 29 06:55:11 node-5 kernel: [    0.467707] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 29 06:55:11 node-5 kernel: [    0.467708] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 29 06:55:11 node-5 kernel: [    0.467710] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 29 06:55:11 node-5 kernel: [    0.467711] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 29 06:55:11 node-5 kernel: [    0.467717] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 29 06:55:11 node-5 kernel: [    0.467799] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 29 06:55:11 node-5 kernel: [    0.467829] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 29 06:55:11 node-5 kernel: [    0.467871] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 29 06:55:11 node-5 kernel: [    0.467890] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 29 06:55:11 node-5 kernel: [    0.467919] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 29 06:55:11 node-5 kernel: [    0.467959] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 29 06:55:11 node-5 kernel: [    0.467976] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 29 06:55:11 node-5 kernel: [    0.468005] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 29 06:55:11 node-5 kernel: [    0.468048] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 29 06:55:11 node-5 kernel: [    0.468064] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.468135] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.468212] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.468287] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 29 06:55:11 node-5 kernel: [    0.468292] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 29 06:55:11 node-5 kernel: [    0.468376] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 29 06:55:11 node-5 kernel: [    0.468523] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 29 06:55:11 node-5 kernel: [    0.468541] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 29 06:55:11 node-5 kernel: [    0.468619] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 29 06:55:11 node-5 kernel: [    0.468671] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 29 06:55:11 node-5 kernel: [    0.468692] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 29 06:55:11 node-5 kernel: [    0.468748] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 29 06:55:11 node-5 kernel: [    0.468791] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 29 06:55:11 node-5 kernel: [    0.468817] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 29 06:55:11 node-5 kernel: [    0.468874] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 29 06:55:11 node-5 kernel: [    0.468917] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 29 06:55:11 node-5 kernel: [    0.468941] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 29 06:55:11 node-5 kernel: [    0.468958] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 29 06:55:11 node-5 kernel: [    0.469036] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 29 06:55:11 node-5 kernel: [    0.469086] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 29 06:55:11 node-5 kernel: [    0.469111] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 29 06:55:11 node-5 kernel: [    0.469357] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 29 06:55:11 node-5 kernel: [    0.469363] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 29 06:55:11 node-5 kernel: [    0.469369] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 29 06:55:11 node-5 kernel: [    0.469375] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 29 06:55:11 node-5 kernel: [    0.469382] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 29 06:55:11 node-5 kernel: [    0.469412] pci 0000:01:00.0: supports D1 D2
Jul 29 06:55:11 node-5 kernel: [    0.479533] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 29 06:55:11 node-5 kernel: [    0.479536] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 29 06:55:11 node-5 kernel: [    0.479538] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 29 06:55:11 node-5 kernel: [    0.479644] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 29 06:55:11 node-5 kernel: [    0.479677] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 29 06:55:11 node-5 kernel: [    0.487522] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 29 06:55:11 node-5 kernel: [    0.487528] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 29 06:55:11 node-5 kernel: [    0.487532] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 06:55:11 node-5 kernel: [    0.487617] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 29 06:55:11 node-5 kernel: [    0.487689] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 29 06:55:11 node-5 kernel: [    0.487783] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 29 06:55:11 node-5 kernel: [    0.487865] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 29 06:55:11 node-5 kernel: [    0.487872] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 06:55:11 node-5 kernel: [    0.487876] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 06:55:11 node-5 kernel: [    0.487946] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 29 06:55:11 node-5 kernel: [    0.488070] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 29 06:55:11 node-5 kernel: [    0.488122] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 29 06:55:11 node-5 kernel: [    0.488125] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 06:55:11 node-5 kernel: [    0.488127] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 06:55:11 node-5 kernel: [    0.488176] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 29 06:55:11 node-5 kernel: [    0.488295] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 29 06:55:11 node-5 kernel: [    0.488333] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 29 06:55:11 node-5 kernel: [    0.488452] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 29 06:55:11 node-5 kernel: [    0.488502] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 29 06:55:11 node-5 kernel: [    0.488625] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 29 06:55:11 node-5 kernel: [    0.488661] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 29 06:55:11 node-5 kernel: [    0.488780] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 29 06:55:11 node-5 kernel: [    0.488821] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 29 06:55:11 node-5 kernel: [    0.488824] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 06:55:11 node-5 kernel: [    0.488826] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 06:55:11 node-5 kernel: [    0.488886] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 29 06:55:11 node-5 kernel: [    0.488949] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 29 06:55:11 node-5 kernel: [    0.489003] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 29 06:55:11 node-5 kernel: [    0.489045] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 29 06:55:11 node-5 kernel: [    0.489127] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 29 06:55:11 node-5 kernel: [    0.489233] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 29 06:55:11 node-5 kernel: [    0.489236] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 06:55:11 node-5 kernel: [    0.489238] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 29 06:55:11 node-5 kernel: [    0.489293] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 29 06:55:11 node-5 kernel: [    0.489347] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 29 06:55:11 node-5 kernel: [    0.489395] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 29 06:55:11 node-5 kernel: [    0.489637] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 29 06:55:11 node-5 kernel: [    0.489641] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 29 06:55:11 node-5 kernel: [    0.489704] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 29 06:55:11 node-5 kernel: [    0.489757] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 29 06:55:11 node-5 kernel: [    0.489806] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 29 06:55:11 node-5 kernel: [    0.490013] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 29 06:55:11 node-5 kernel: [    0.490017] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 29 06:55:11 node-5 kernel: [    0.490079] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 29 06:55:11 node-5 kernel: [    0.490139] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 29 06:55:11 node-5 kernel: [    0.490191] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 29 06:55:11 node-5 kernel: [    0.490412] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 29 06:55:11 node-5 kernel: [    0.490416] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 29 06:55:11 node-5 kernel: [    0.490611] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 29 06:55:11 node-5 kernel: [    0.490649] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 29 06:55:11 node-5 kernel: [    0.490725] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 29 06:55:11 node-5 kernel: [    0.490744] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 29 06:55:11 node-5 kernel: [    0.490757] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 29 06:55:11 node-5 kernel: [    0.490770] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 29 06:55:11 node-5 kernel: [    0.490821] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 29 06:55:11 node-5 kernel: [    0.495528] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 29 06:55:11 node-5 kernel: [    0.495537] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 29 06:55:11 node-5 kernel: [    0.495594] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 29 06:55:11 node-5 kernel: [    0.496084] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 29 06:55:11 node-5 kernel: [    0.496087] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 06:55:11 node-5 kernel: [    0.496212] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 29 06:55:11 node-5 kernel: [    0.496320] PCI host bridge to bus 0000:80
Jul 29 06:55:11 node-5 kernel: [    0.496322] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 29 06:55:11 node-5 kernel: [    0.496323] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 29 06:55:11 node-5 kernel: [    0.496325] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 29 06:55:11 node-5 kernel: [    0.496333] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.496396] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.496465] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 29 06:55:11 node-5 kernel: [    0.496528] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 29 06:55:11 node-5 kernel: [    0.496533] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 29 06:55:11 node-5 kernel: [    0.496606] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 29 06:55:11 node-5 kernel: [    0.496907] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 29 06:55:11 node-5 kernel: [    0.496938] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 29 06:55:11 node-5 kernel: [    0.496968] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 29 06:55:11 node-5 kernel: [    0.496997] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 29 06:55:11 node-5 kernel: [    0.497026] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 06:55:11 node-5 kernel: [    0.497056] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 06:55:11 node-5 kernel: [    0.497086] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 06:55:11 node-5 kernel: [    0.497116] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 06:55:11 node-5 kernel: [    0.497201] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 29 06:55:11 node-5 kernel: [    0.497205] ACPI: \_SB_.UNC1: notify handler is installed
Jul 29 06:55:11 node-5 kernel: [    0.497206] ACPI: \_SB_.UNC0: notify handler is installed
Jul 29 06:55:11 node-5 kernel: [    0.497221] ACPI: \_SB_.PCI0: notify handler is installed
Jul 29 06:55:11 node-5 kernel: [    0.497274] ACPI: \_SB_.PCI1: notify handler is installed
Jul 29 06:55:11 node-5 kernel: [    0.497354] Found 4 acpi root devices
Jul 29 06:55:11 node-5 kernel: [    0.497466] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 29 06:55:11 node-5 kernel: [    0.497468] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 29 06:55:11 node-5 kernel: [    0.497469] vgaarb: loaded
Jul 29 06:55:11 node-5 kernel: [    0.497470] vgaarb: bridge control possible 0000:0c:00.0
Jul 29 06:55:11 node-5 kernel: [    0.497588] SCSI subsystem initialized
Jul 29 06:55:11 node-5 kernel: [    0.497653] libata version 3.00 loaded.
Jul 29 06:55:11 node-5 kernel: [    0.497668] ACPI: bus type USB registered
Jul 29 06:55:11 node-5 kernel: [    0.497678] usbcore: registered new interface driver usbfs
Jul 29 06:55:11 node-5 kernel: [    0.497683] usbcore: registered new interface driver hub
Jul 29 06:55:11 node-5 kernel: [    0.497707] usbcore: registered new device driver usb
Jul 29 06:55:11 node-5 kernel: [    0.497866] PCI: Using ACPI for IRQ routing
Jul 29 06:55:11 node-5 kernel: [    0.501481] PCI: pci_cache_line_size set to 64 bytes
Jul 29 06:55:11 node-5 kernel: [    0.501688] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 29 06:55:11 node-5 kernel: [    0.501690] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 29 06:55:11 node-5 kernel: [    0.501690] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 29 06:55:11 node-5 kernel: [    0.501755] NetLabel: Initializing
Jul 29 06:55:11 node-5 kernel: [    0.501756] NetLabel:  domain hash size = 128
Jul 29 06:55:11 node-5 kernel: [    0.501757] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 29 06:55:11 node-5 kernel: [    0.501767] NetLabel:  unlabeled traffic allowed by default
Jul 29 06:55:11 node-5 kernel: [    0.501823] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 29 06:55:11 node-5 kernel: [    0.501827] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 29 06:55:11 node-5 kernel: [    0.503885] Switched to clocksource hpet
Jul 29 06:55:11 node-5 kernel: [    0.507917] AppArmor: AppArmor Filesystem Enabled
Jul 29 06:55:11 node-5 kernel: [    0.507931] pnp: PnP ACPI init
Jul 29 06:55:11 node-5 kernel: [    0.507938] ACPI: bus type PNP registered
Jul 29 06:55:11 node-5 kernel: [    0.508049] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 29 06:55:11 node-5 kernel: [    0.508057] pnp 00:01: [dma 4]
Jul 29 06:55:11 node-5 kernel: [    0.508069] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 29 06:55:11 node-5 kernel: [    0.508096] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 29 06:55:11 node-5 kernel: [    0.508116] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 29 06:55:11 node-5 kernel: [    0.508133] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 29 06:55:11 node-5 kernel: [    0.508166] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 29 06:55:11 node-5 kernel: [    0.508220] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 29 06:55:11 node-5 kernel: [    0.508222] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 29 06:55:11 node-5 kernel: [    0.508224] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 29 06:55:11 node-5 kernel: [    0.508225] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 29 06:55:11 node-5 kernel: [    0.508227] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 29 06:55:11 node-5 kernel: [    0.508232] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 29 06:55:11 node-5 kernel: [    0.508234] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 29 06:55:11 node-5 kernel: [    0.508236] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 29 06:55:11 node-5 kernel: [    0.508237] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 29 06:55:11 node-5 kernel: [    0.508239] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 29 06:55:11 node-5 kernel: [    0.508240] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 29 06:55:11 node-5 kernel: [    0.508241] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 29 06:55:11 node-5 kernel: [    0.508243] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 29 06:55:11 node-5 kernel: [    0.508245] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 29 06:55:11 node-5 kernel: [    0.508329] pnp 00:07: [dma 0 disabled]
Jul 29 06:55:11 node-5 kernel: [    0.508357] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 29 06:55:11 node-5 kernel: [    0.508432] pnp 00:08: [dma 0 disabled]
Jul 29 06:55:11 node-5 kernel: [    0.508464] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 29 06:55:11 node-5 kernel: [    0.508515] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 29 06:55:11 node-5 kernel: [    0.508861] pnp: PnP ACPI: found 10 devices
Jul 29 06:55:11 node-5 kernel: [    0.508863] ACPI: bus type PNP unregistered
Jul 29 06:55:11 node-5 kernel: [    0.515122] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 29 06:55:11 node-5 kernel: [    0.515125] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 29 06:55:11 node-5 kernel: [    0.515128] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 29 06:55:11 node-5 kernel: [    0.515132] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 29 06:55:11 node-5 kernel: [    0.515134] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 06:55:11 node-5 kernel: [    0.515149] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 29 06:55:11 node-5 kernel: [    0.515178] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 29 06:55:11 node-5 kernel: [    0.515193] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 29 06:55:11 node-5 kernel: [    0.515225] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 29 06:55:11 node-5 kernel: [    0.515240] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 29 06:55:11 node-5 kernel: [    0.515268] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 29 06:55:11 node-5 kernel: [    0.515283] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 29 06:55:11 node-5 kernel: [    0.515311] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 29 06:55:11 node-5 kernel: [    0.515313] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 06:55:11 node-5 kernel: [    0.515328] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 06:55:11 node-5 kernel: [    0.515356] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 29 06:55:11 node-5 kernel: [    0.515358] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 06:55:11 node-5 kernel: [    0.515373] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 06:55:11 node-5 kernel: [    0.515401] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 29 06:55:11 node-5 kernel: [    0.515403] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 06:55:11 node-5 kernel: [    0.515406] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 06:55:11 node-5 kernel: [    0.515410] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 29 06:55:11 node-5 kernel: [    0.515411] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 29 06:55:11 node-5 kernel: [    0.515414] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 06:55:11 node-5 kernel: [    0.515418] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 29 06:55:11 node-5 kernel: [    0.515422] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 29 06:55:11 node-5 kernel: [    0.515430] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 29 06:55:11 node-5 kernel: [    0.515434] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 29 06:55:11 node-5 kernel: [    0.515440] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 29 06:55:11 node-5 kernel: [    0.515441] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 29 06:55:11 node-5 kernel: [    0.515442] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 29 06:55:11 node-5 kernel: [    0.515443] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 29 06:55:11 node-5 kernel: [    0.515444] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 29 06:55:11 node-5 kernel: [    0.515445] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 29 06:55:11 node-5 kernel: [    0.515445] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 29 06:55:11 node-5 kernel: [    0.515446] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 29 06:55:11 node-5 kernel: [    0.515447] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 29 06:55:11 node-5 kernel: [    0.515448] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 29 06:55:11 node-5 kernel: [    0.515449] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 29 06:55:11 node-5 kernel: [    0.515450] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 29 06:55:11 node-5 kernel: [    0.515451] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 29 06:55:11 node-5 kernel: [    0.515452] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 29 06:55:11 node-5 kernel: [    0.515452] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 29 06:55:11 node-5 kernel: [    0.515453] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 29 06:55:11 node-5 kernel: [    0.515454] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 29 06:55:11 node-5 kernel: [    0.515455] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 29 06:55:11 node-5 kernel: [    0.515456] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 29 06:55:11 node-5 kernel: [    0.515457] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 29 06:55:11 node-5 kernel: [    0.515458] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 29 06:55:11 node-5 kernel: [    0.515459] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 29 06:55:11 node-5 kernel: [    0.515461] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 29 06:55:11 node-5 kernel: [    0.515462] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 29 06:55:11 node-5 kernel: [    0.515503] NET: Registered protocol family 2
Jul 29 06:55:11 node-5 kernel: [    0.515770] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 29 06:55:11 node-5 kernel: [    0.516109] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 29 06:55:11 node-5 kernel: [    0.516255] TCP: Hash tables configured (established 262144 bind 65536)
Jul 29 06:55:11 node-5 kernel: [    0.516297] TCP: reno registered
Jul 29 06:55:11 node-5 kernel: [    0.516328] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 29 06:55:11 node-5 kernel: [    0.516424] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 29 06:55:11 node-5 kernel: [    0.516571] NET: Registered protocol family 1
Jul 29 06:55:11 node-5 kernel: [    0.551992] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 29 06:55:11 node-5 kernel: [    0.551999] PCI: CLS 64 bytes, default 64
Jul 29 06:55:11 node-5 kernel: [    0.552041] Trying to unpack rootfs image as initramfs...
Jul 29 06:55:11 node-5 kernel: [    0.771188] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Jul 29 06:55:11 node-5 kernel: [    0.771224] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 29 06:55:11 node-5 kernel: [    0.771226] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 29 06:55:11 node-5 kernel: [    0.771644] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 06:55:11 node-5 kernel: [    0.771650] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 06:55:11 node-5 kernel: [    0.771663] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 06:55:11 node-5 kernel: [    0.771669] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 06:55:11 node-5 kernel: [    0.771683] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 06:55:11 node-5 kernel: [    0.771700] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 06:55:11 node-5 kernel: [    0.771725] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 06:55:11 node-5 kernel: [    0.771734] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 06:55:11 node-5 kernel: [    0.771742] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 06:55:11 node-5 kernel: [    0.771751] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 06:55:11 node-5 kernel: [    0.771758] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 06:55:11 node-5 kernel: [    0.771764] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 06:55:11 node-5 kernel: [    0.771771] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 06:55:11 node-5 kernel: [    0.771779] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 06:55:11 node-5 kernel: [    0.771786] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 06:55:11 node-5 kernel: [    0.771794] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 06:55:11 node-5 kernel: [    0.771871] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 29 06:55:11 node-5 kernel: [    0.771874] Scanning for low memory corruption every 60 seconds
Jul 29 06:55:11 node-5 kernel: [    0.772249] Initialise system trusted keyring
Jul 29 06:55:11 node-5 kernel: [    0.772303] audit: initializing netlink socket (disabled)
Jul 29 06:55:11 node-5 kernel: [    0.772319] type=2000 audit(1469775275.724:1): initialized
Jul 29 06:55:11 node-5 kernel: [    0.790254] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 29 06:55:11 node-5 kernel: [    0.791767] zbud: loaded
Jul 29 06:55:11 node-5 kernel: [    0.791893] VFS: Disk quotas dquot_6.5.2
Jul 29 06:55:11 node-5 kernel: [    0.791929] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 29 06:55:11 node-5 kernel: [    0.792301] fuse init (API version 7.22)
Jul 29 06:55:11 node-5 kernel: [    0.792361] msgmni has been set to 32768
Jul 29 06:55:11 node-5 kernel: [    0.792410] Key type big_key registered
Jul 29 06:55:11 node-5 kernel: [    0.792983] Key type asymmetric registered
Jul 29 06:55:11 node-5 kernel: [    0.792985] Asymmetric key parser 'x509' registered
Jul 29 06:55:11 node-5 kernel: [    0.793007] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 29 06:55:11 node-5 kernel: [    0.793071] io scheduler noop registered
Jul 29 06:55:11 node-5 kernel: [    0.793073] io scheduler deadline registered (default)
Jul 29 06:55:11 node-5 kernel: [    0.793091] io scheduler cfq registered
Jul 29 06:55:11 node-5 kernel: [    0.793614] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    0.793773] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    0.793891] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    0.794002] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    0.794118] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    0.794215] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    0.794626] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 29 06:55:11 node-5 kernel: [    0.794652] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 29 06:55:11 node-5 kernel: [    0.794668] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 29 06:55:11 node-5 kernel: [    0.794677] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794679] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794682] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 29 06:55:11 node-5 kernel: [    0.794687] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794689] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794690] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794691] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794693] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794695] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794696] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794698] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794699] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794700] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794702] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794703] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794705] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 29 06:55:11 node-5 kernel: [    0.794710] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794713] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 29 06:55:11 node-5 kernel: [    0.794728] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794731] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 29 06:55:11 node-5 kernel: [    0.794741] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794743] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 29 06:55:11 node-5 kernel: [    0.794746] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 29 06:55:11 node-5 kernel: [    0.794781] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 29 06:55:11 node-5 kernel: [    0.794787] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 29 06:55:11 node-5 kernel: [    0.794791] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 29 06:55:11 node-5 kernel: [    0.794800] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 29 06:55:11 node-5 kernel: [    0.794841] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 29 06:55:11 node-5 kernel: [    0.794843] vesafb: scrolling: redraw
Jul 29 06:55:11 node-5 kernel: [    0.794844] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 29 06:55:11 node-5 kernel: [    0.815424] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 29 06:55:11 node-5 kernel: [    0.823947] Console: switching to colour frame buffer device 80x30
Jul 29 06:55:11 node-5 kernel: [    0.832617] fb0: VESA VGA frame buffer device
Jul 29 06:55:11 node-5 kernel: [    0.832815] intel_idle: MWAIT substates: 0x2120
Jul 29 06:55:11 node-5 kernel: [    0.832816] intel_idle: v0.4 model 0x3F
Jul 29 06:55:11 node-5 kernel: [    0.832817] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 29 06:55:11 node-5 kernel: [    0.833043] ipmi message handler version 39.2
Jul 29 06:55:11 node-5 kernel: [    0.833324] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 29 06:55:11 node-5 kernel: [    0.833756] ACPI: AC Adapter [P111] (on-line)
Jul 29 06:55:11 node-5 kernel: [    0.838981] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 29 06:55:11 node-5 kernel: [    0.849994] ACPI: Power Button [PWRB]
Jul 29 06:55:11 node-5 kernel: [    0.855754] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 29 06:55:11 node-5 kernel: [    0.867366] ACPI: Power Button [PWRF]
Jul 29 06:55:11 node-5 kernel: [    0.881473] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 29 06:55:11 node-5 kernel: [    0.893115] pstore: Registered erst as persistent store backend
Jul 29 06:55:11 node-5 kernel: [    0.899325] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 29 06:55:11 node-5 kernel: [    0.911254] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 29 06:55:11 node-5 kernel: [    0.937988] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 29 06:55:11 node-5 kernel: [    0.971249] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 29 06:55:11 node-5 kernel: [    0.985310] Linux agpgart interface v0.103
Jul 29 06:55:11 node-5 kernel: [    0.992930] brd: module loaded
Jul 29 06:55:11 node-5 kernel: [    0.999935] loop: module loaded
Jul 29 06:55:11 node-5 kernel: [    1.006630] libphy: Fixed MDIO Bus: probed
Jul 29 06:55:11 node-5 kernel: [    1.013072] tun: Universal TUN/TAP device driver, 1.6
Jul 29 06:55:11 node-5 kernel: [    1.019515] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 29 06:55:11 node-5 kernel: [    1.026080] PPP generic driver version 2.4.2
Jul 29 06:55:11 node-5 kernel: [    1.032553] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 29 06:55:11 node-5 kernel: [    1.039002] ehci-pci: EHCI PCI platform driver
Jul 29 06:55:11 node-5 kernel: [    1.045499] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 29 06:55:11 node-5 kernel: [    1.051891] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 29 06:55:11 node-5 kernel: [    1.064394] ehci-pci 0000:00:1a.0: debug port 2
Jul 29 06:55:11 node-5 kernel: [    1.074556] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 29 06:55:11 node-5 kernel: [    1.074574] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 29 06:55:11 node-5 kernel: [    1.091390] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 29 06:55:11 node-5 kernel: [    1.097439] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 29 06:55:11 node-5 kernel: [    1.103584] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 29 06:55:11 node-5 kernel: [    1.115454] usb usb1: Product: EHCI Host Controller
Jul 29 06:55:11 node-5 kernel: [    1.121472] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 29 06:55:11 node-5 kernel: [    1.127493] usb usb1: SerialNumber: 0000:00:1a.0
Jul 29 06:55:11 node-5 kernel: [    1.133425] hub 1-0:1.0: USB hub found
Jul 29 06:55:11 node-5 kernel: [    1.139174] hub 1-0:1.0: 2 ports detected
Jul 29 06:55:11 node-5 kernel: [    1.144956] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 29 06:55:11 node-5 kernel: [    1.150544] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 29 06:55:11 node-5 kernel: [    1.161497] ehci-pci 0000:00:1d.0: debug port 2
Jul 29 06:55:11 node-5 kernel: [    1.170816] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 29 06:55:11 node-5 kernel: [    1.170819] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 29 06:55:11 node-5 kernel: [    1.187309] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 29 06:55:11 node-5 kernel: [    1.192511] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 29 06:55:11 node-5 kernel: [    1.197805] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 29 06:55:11 node-5 kernel: [    1.208388] usb usb2: Product: EHCI Host Controller
Jul 29 06:55:11 node-5 kernel: [    1.213856] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 29 06:55:11 node-5 kernel: [    1.219404] usb usb2: SerialNumber: 0000:00:1d.0
Jul 29 06:55:11 node-5 kernel: [    1.224916] hub 2-0:1.0: USB hub found
Jul 29 06:55:11 node-5 kernel: [    1.230267] hub 2-0:1.0: 2 ports detected
Jul 29 06:55:11 node-5 kernel: [    1.235556] ehci-platform: EHCI generic platform driver
Jul 29 06:55:11 node-5 kernel: [    1.240790] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 29 06:55:11 node-5 kernel: [    1.246099] ohci-pci: OHCI PCI platform driver
Jul 29 06:55:11 node-5 kernel: [    1.251391] ohci-platform: OHCI generic platform driver
Jul 29 06:55:11 node-5 kernel: [    1.256583] uhci_hcd: USB Universal Host Controller Interface driver
Jul 29 06:55:11 node-5 kernel: [    1.261923] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 29 06:55:11 node-5 kernel: [    1.455088] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 29 06:55:11 node-5 kernel: [    1.627325] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 29 06:55:11 node-5 kernel: [    1.632845] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 29 06:55:11 node-5 kernel: [    1.638593] hub 1-1:1.0: USB hub found
Jul 29 06:55:11 node-5 kernel: [    1.644062] hub 1-1:1.0: 6 ports detected
Jul 29 06:55:11 node-5 kernel: [    1.758822] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 29 06:55:11 node-5 kernel: [    1.766819] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 29 06:55:11 node-5 kernel: [    2.026987] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 29 06:55:11 node-5 kernel: [    2.032529] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 29 06:55:11 node-5 kernel: [    2.038379] hub 2-1:1.0: USB hub found
Jul 29 06:55:11 node-5 kernel: [    2.044098] hub 2-1:1.0: 8 ports detected
Jul 29 06:55:11 node-5 kernel: [    2.303569] i8042: No controller found
Jul 29 06:55:11 node-5 kernel: [    2.308985] mousedev: PS/2 mouse device common for all mice
Jul 29 06:55:11 node-5 kernel: [    2.314486] rtc_cmos 00:02: RTC can wake from S4
Jul 29 06:55:11 node-5 kernel: [    2.320071] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 29 06:55:11 node-5 kernel: [    2.322414] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 29 06:55:11 node-5 kernel: [    2.331214] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 29 06:55:11 node-5 kernel: [    2.342285] device-mapper: uevent: version 1.0.3
Jul 29 06:55:11 node-5 kernel: [    2.347904] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 29 06:55:11 node-5 kernel: [    2.359119] ledtrig-cpu: registered to indicate activity on CPUs
Jul 29 06:55:11 node-5 kernel: [    2.365036] TCP: cubic registered
Jul 29 06:55:11 node-5 kernel: [    2.370914] NET: Registered protocol family 10
Jul 29 06:55:11 node-5 kernel: [    2.376904] NET: Registered protocol family 17
Jul 29 06:55:11 node-5 kernel: [    2.382556] Key type dns_resolver registered
Jul 29 06:55:11 node-5 kernel: [    2.388547] Loading compiled-in X.509 certificates
Jul 29 06:55:11 node-5 kernel: [    2.394764] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 29 06:55:11 node-5 kernel: [    2.406275] registered taskstats version 1
Jul 29 06:55:11 node-5 kernel: [    2.414320] Key type trusted registered
Jul 29 06:55:11 node-5 kernel: [    2.421911] Key type encrypted registered
Jul 29 06:55:11 node-5 kernel: [    2.427368] AppArmor: AppArmor sha1 policy hashing enabled
Jul 29 06:55:11 node-5 kernel: [    2.432848] IMA: No TPM chip found, activating TPM-bypass!
Jul 29 06:55:11 node-5 kernel: [    2.438981] regulator-dummy: disabling
Jul 29 06:55:11 node-5 kernel: [    2.444530]   Magic number: 8:710:924
Jul 29 06:55:11 node-5 kernel: [    2.450169] rtc_cmos 00:02: setting system clock to 2016-07-29 06:54:38 UTC (1469775278)
Jul 29 06:55:11 node-5 kernel: [    2.455083] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 29 06:55:11 node-5 kernel: [    2.455084] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 29 06:55:11 node-5 kernel: [    2.455085] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 29 06:55:11 node-5 kernel: [    2.455086] usb 2-1.4: Manufacturer: Avocent
Jul 29 06:55:11 node-5 kernel: [    2.455086] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 29 06:55:11 node-5 kernel: [    2.497448] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 29 06:55:11 node-5 kernel: [    2.503285] EDD information not available.
Jul 29 06:55:11 node-5 kernel: [    2.509032] PM: Hibernation image not present or could not be loaded.
Jul 29 06:55:11 node-5 kernel: [    2.509908] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 29 06:55:11 node-5 kernel: [    2.521381] Write protecting the kernel read-only data: 12288k
Jul 29 06:55:11 node-5 kernel: [    2.527743] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 29 06:55:11 node-5 kernel: [    2.540398] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 29 06:55:11 node-5 kernel: [    2.572728] device-mapper: multipath: version 1.6.0 loaded
Jul 29 06:55:11 node-5 kernel: [    2.580798] systemd-udevd[218]: starting version 204
Jul 29 06:55:11 node-5 kernel: [    2.605495] md: linear personality registered for level -1
Jul 29 06:55:11 node-5 kernel: [    2.619538] md: multipath personality registered for level -4
Jul 29 06:55:11 node-5 kernel: [    2.627526] md: raid0 personality registered for level 0
Jul 29 06:55:11 node-5 kernel: [    2.636638] md: raid1 personality registered for level 1
Jul 29 06:55:11 node-5 kernel: [    2.644881] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 29 06:55:11 node-5 kernel: [    2.651321] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 29 06:55:11 node-5 kernel: [    2.651527] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 29 06:55:11 node-5 kernel: [    2.664131] hidraw: raw HID events driver (C) Jiri Kosina
Jul 29 06:55:11 node-5 kernel: [    2.668328] megasas: FW now in Ready state
Jul 29 06:55:11 node-5 kernel: [    2.668788] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.668940] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.669112] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.669207] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.669283] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.669421] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.669586] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.669713] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.669863] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.670435] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.670508] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.670664] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.670751] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.670863] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.670987] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.671088] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.671734] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 29 06:55:11 node-5 kernel: [    2.672926] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 29 06:55:11 node-5 kernel: [    2.672927] 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 29 06:55:11 node-5 kernel: [    2.672928] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 06:55:11 node-5 kernel: [    2.673041] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.673074] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.673109] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.673159] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.673264] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.684640] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 29 06:55:11 node-5 kernel: [    2.684642] 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 29 06:55:11 node-5 kernel: [    2.684644] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 06:55:11 node-5 kernel: [    2.684717] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.684757] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.684794] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.684839] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.684937] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.693670] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 29 06:55:11 node-5 kernel: [    2.693673] 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 29 06:55:11 node-5 kernel: [    2.693674] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 06:55:11 node-5 kernel: [    2.693755] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.693788] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.693820] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.693857] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.693952] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.703207] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 29 06:55:11 node-5 kernel: [    2.703209] 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 29 06:55:11 node-5 kernel: [    2.703210] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 06:55:11 node-5 kernel: [    2.703283] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.703328] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.703396] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.703434] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.703525] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 06:55:11 node-5 kernel: [    2.718166] raid6: sse2x1    2254 MB/s
Jul 29 06:55:11 node-5 kernel: [    2.786125] raid6: sse2x2     809 MB/s
Jul 29 06:55:11 node-5 kernel: [    2.854016] raid6: sse2x4    1476 MB/s
Jul 29 06:55:11 node-5 kernel: [    2.921848] raid6: avx2x1    6271 MB/s
Jul 29 06:55:11 node-5 kernel: [    2.993783] raid6: avx2x2   18861 MB/s
Jul 29 06:55:11 node-5 kernel: [    3.065726] raid6: avx2x4   21377 MB/s
Jul 29 06:55:11 node-5 kernel: [    3.071521] raid6: using algorithm avx2x4 (21377 MB/s)
Jul 29 06:55:11 node-5 kernel: [    3.077452] raid6: using avx2x2 recovery algorithm
Jul 29 06:55:11 node-5 kernel: [    3.083312] Switched to clocksource tsc
Jul 29 06:55:11 node-5 kernel: [    3.083313] megasas:IOC Init cmd success
Jul 29 06:55:11 node-5 kernel: [    3.095374] xor: automatically using best checksumming function:
Jul 29 06:55:11 node-5 kernel: [    3.102744] usbcore: registered new interface driver usbhid
Jul 29 06:55:11 node-5 kernel: [    3.105701] megasas: INIT adapter done
Jul 29 06:55:11 node-5 kernel: [    3.113429] usbhid: USB HID core driver
Jul 29 06:55:11 node-5 kernel: [    3.119652] 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 29 06:55:11 node-5 kernel: [    3.130635] 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 29 06:55:11 node-5 kernel: [    3.137720]    avx       : 35883.000 MB/sec
Jul 29 06:55:11 node-5 kernel: [    3.147106] 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 29 06:55:11 node-5 kernel: [    3.158290] async_tx: api initialized (async)
Jul 29 06:55:11 node-5 kernel: [    3.158319] 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 29 06:55:11 node-5 kernel: [    3.158374] 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 29 06:55:11 node-5 kernel: [    3.158414] 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 29 06:55:11 node-5 kernel: [    3.177639] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 29 06:55:11 node-5 kernel: [    3.178031] scsi0 : LSI SAS based MegaRAID driver
Jul 29 06:55:11 node-5 kernel: [    3.185920] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 29 06:55:11 node-5 kernel: [    3.223015] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 29 06:55:11 node-5 kernel: [    3.238453] md: raid6 personality registered for level 6
Jul 29 06:55:11 node-5 kernel: [    3.238889] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 29 06:55:11 node-5 kernel: [    3.239166] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 29 06:55:11 node-5 kernel: [    3.239646] sd 0:2:0:0: [sda] Write Protect is off
Jul 29 06:55:11 node-5 kernel: [    3.239647] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 29 06:55:11 node-5 kernel: [    3.239856] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 29 06:55:11 node-5 kernel: [    3.271194]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 29 06:55:11 node-5 kernel: [    3.272154] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 29 06:55:11 node-5 kernel: [    3.300939] md: raid5 personality registered for level 5
Jul 29 06:55:11 node-5 kernel: [    3.308044] md: raid4 personality registered for level 4
Jul 29 06:55:11 node-5 kernel: [    3.318191] md: raid10 personality registered for level 10
Jul 29 06:55:11 node-5 kernel: [    3.372703] multipathd (359): /proc/359/oom_adj is deprecated, please use /proc/359/oom_score_adj instead.
Jul 29 06:55:11 node-5 kernel: [    3.440450] random: lvm urandom read with 28 bits of entropy available
Jul 29 06:55:11 node-5 kernel: [    3.558476] bio: create slab <bio-1> at 1
Jul 29 06:55:11 node-5 kernel: [    4.226607] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 06:55:11 node-5 kernel: [    4.798295] init: plymouth-upstart-bridge main process (548) terminated with status 1
Jul 29 06:55:11 node-5 kernel: [    4.810857] init: plymouth-upstart-bridge main process ended, respawning
Jul 29 06:55:11 node-5 kernel: [    4.912891] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 29 06:55:11 node-5 kernel: [    4.957421] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 29 06:55:11 node-5 kernel: [    5.090532] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 29 06:55:11 node-5 kernel: [    5.150403] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 29 06:55:11 node-5 kernel: [    5.232733] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 06:55:11 node-5 kernel: [    5.270266] random: nonblocking pool is initialized
Jul 29 06:55:11 node-5 kernel: [    5.423567] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 29 06:55:11 node-5 kernel: [    5.476566] XFS (dm-0): Mounting Filesystem
Jul 29 06:55:11 node-5 kernel: [    5.785741] XFS (dm-0): Ending clean mount
Jul 29 06:55:11 node-5 kernel: [    5.853291] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 06:55:11 node-5 kernel: [    5.880435] XFS (dm-1): Mounting Filesystem
Jul 29 06:55:11 node-5 kernel: [    6.017806] XFS (dm-1): Ending clean mount
Jul 29 06:55:11 node-5 kernel: [    7.715842] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 29 06:55:11 node-5 kernel: [    7.729786] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 29 06:55:11 node-5 kernel: [    7.860649] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 29 06:55:11 node-5 kernel: [    7.860654] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 29 06:55:11 node-5 kernel: [    7.860658] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 29 06:55:11 node-5 kernel: [    7.860662] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 29 06:55:11 node-5 kernel: [    7.902114] systemd-udevd[772]: starting version 204
Jul 29 06:55:11 node-5 kernel: [    8.062401] power_meter ACPI000D:00: Found ACPI power meter.
Jul 29 06:55:11 node-5 kernel: [    8.062429] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 29 06:55:11 node-5 kernel: [    8.120388] IPMI System Interface driver.
Jul 29 06:55:11 node-5 kernel: [    8.120429] ipmi_si: probing via ACPI
Jul 29 06:55:11 node-5 kernel: [    8.120455] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 29 06:55:11 node-5 kernel: [    8.120456] ipmi_si: Adding ACPI-specified kcs state machine
Jul 29 06:55:11 node-5 kernel: [    8.120465] ipmi_si: probing via SMBIOS
Jul 29 06:55:11 node-5 kernel: [    8.120466] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 29 06:55:11 node-5 kernel: [    8.120467] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 29 06:55:11 node-5 kernel: [    8.120469] ipmi_si: probing via SPMI
Jul 29 06:55:11 node-5 kernel: [    8.120469] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 29 06:55:11 node-5 kernel: [    8.120470] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 29 06:55:11 node-5 kernel: [    8.120471] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 29 06:55:11 node-5 kernel: [    8.136195] wmi: Mapper loaded
Jul 29 06:55:11 node-5 kernel: [    8.151530] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 29 06:55:11 node-5 kernel: [    8.168641] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 29 06:55:11 node-5 kernel: [    8.168646] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 29 06:55:11 node-5 kernel: [    8.168649] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 29 06:55:11 node-5 kernel: [    8.168650] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 29 06:55:11 node-5 kernel: [    8.168663] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 29 06:55:11 node-5 kernel: [    8.225847] systemd-udevd[793]: renamed network interface eth0 to enp6s0
Jul 29 06:55:11 node-5 kernel: [    8.253935] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 29 06:55:11 node-5 kernel: [    8.253941] ipmi_si 00:09: IPMI kcs interface initialized
Jul 29 06:55:11 node-5 kernel: [    8.257690] systemd-udevd[800]: renamed network interface eth1 to enp7s0
Jul 29 06:55:11 node-5 kernel: [    8.291365] systemd-udevd[803]: renamed network interface eth2 to enp8s0
Jul 29 06:55:11 node-5 kernel: [    8.329661] systemd-udevd[811]: renamed network interface eth3 to enp9s0
Jul 29 06:55:11 node-5 kernel: [    8.611553] type=1400 audit(1469775284.662:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=989 comm="apparmor_parser"
Jul 29 06:55:11 node-5 kernel: [    8.611711] type=1400 audit(1469775284.662:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=989 comm="apparmor_parser"
Jul 29 06:55:11 node-5 kernel: [    8.611838] type=1400 audit(1469775284.662:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=989 comm="apparmor_parser"
Jul 29 06:55:11 node-5 kernel: [    8.614420] type=1400 audit(1469775284.666:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1009 comm="apparmor_parser"
Jul 29 06:55:11 node-5 kernel: [    8.614563] type=1400 audit(1469775284.666:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1009 comm="apparmor_parser"
Jul 29 06:55:11 node-5 kernel: [    8.614680] type=1400 audit(1469775284.666:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1009 comm="apparmor_parser"
Jul 29 06:55:11 node-5 kernel: [    8.631322] type=1400 audit(1469775284.682:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=988 comm="apparmor_parser"
Jul 29 06:55:11 node-5 kernel: [    8.631460] type=1400 audit(1469775284.682:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=988 comm="apparmor_parser"
Jul 29 06:55:11 node-5 kernel: [    8.631577] type=1400 audit(1469775284.682:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=988 comm="apparmor_parser"
Jul 29 06:55:11 node-5 kernel: [    8.641020] type=1400 audit(1469775284.694:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=990 comm="apparmor_parser"
Jul 29 06:55:11 node-5 kernel: [    9.202115] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 29 06:55:11 node-5 kernel: [    9.207993] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 29 06:55:11 node-5 kernel: [    9.379877] enic 0000:06:00.0 enp6s0: Link UP
Jul 29 06:55:11 node-5 kernel: [    9.380300] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 29 06:55:11 node-5 kernel: [    9.380309] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 29 06:55:11 node-5 kernel: [   18.537064] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 29 06:55:12 node-5 failsafe: Failsafe of 120 seconds reached.
Jul 29 06:55:12 node-5 kernel: [   37.125832] init: failsafe main process (8394) killed by TERM signal
Jul 29 06:55:13 node-5 dbus[8437]: [system] AppArmor D-Bus mediation is enabled
Jul 29 06:55:13 node-5 kernel: [   37.335435] audit_printk_skb: 30 callbacks suppressed
Jul 29 06:55:13 node-5 kernel: [   37.335437] type=1400 audit(1469775313.117:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8520 comm="apparmor_parser"
Jul 29 06:55:13 node-5 kernel: [   37.335442] type=1400 audit(1469775313.117:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8520 comm="apparmor_parser"
Jul 29 06:55:13 node-5 kernel: [   37.335444] type=1400 audit(1469775313.117:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8520 comm="apparmor_parser"
Jul 29 06:55:13 node-5 kernel: [   37.335665] type=1400 audit(1469775313.117:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8520 comm="apparmor_parser"
Jul 29 06:55:13 node-5 kernel: [   37.335669] type=1400 audit(1469775313.117:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8520 comm="apparmor_parser"
Jul 29 06:55:13 node-5 kernel: [   37.335782] type=1400 audit(1469775313.117:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8520 comm="apparmor_parser"
Jul 29 06:55:13 node-5 kernel: [   37.338747] type=1400 audit(1469775313.121:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8521 comm="apparmor_parser"
Jul 29 06:55:13 node-5 kernel: [   37.420150] type=1400 audit(1469775313.205:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8523 comm="apparmor_parser"
Jul 29 06:55:13 node-5 anacron[8587]: Anacron 2.3 started on 2016-07-29
Jul 29 06:55:13 node-5 cron[8553]: (CRON) INFO (pidfile fd = 3)
Jul 29 06:55:13 node-5 cron[8591]: (CRON) STARTUP (fork ok)
Jul 29 06:55:13 node-5 anacron[8587]: Will run job `cron.daily' in 5 min.
Jul 29 06:55:13 node-5 anacron[8587]: Will run job `cron.weekly' in 10 min.
Jul 29 06:55:13 node-5 anacron[8587]: Will run job `cron.monthly' in 15 min.
Jul 29 06:55:13 node-5 anacron[8587]: Jobs will be executed sequentially
Jul 29 06:55:13 node-5 multipathd: path checkers start up
Jul 29 06:55:13 node-5 cron[8591]: (CRON) INFO (Running @reboot jobs)
Jul 29 06:55:13 node-5 postfix/master[8732]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 29 06:55:16 node-5 puppet-agent[8916]: Reopening log files
Jul 29 06:55:17 node-5 puppet-agent[8916]: Could not request certificate: Connection refused - connect(2)
Jul 29 06:55:30 node-5 puppet-user[8995]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 29 06:55:30 node-5 puppet-user[8995]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Jul 29 06:55:31 node-5 puppet-user[8995]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 29 06:55:31 node-5 puppet-user[8995]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 29 06:55:31 node-5 puppet-user[8995]: Finished catalog run in 0.58 seconds
Jul 29 06:55:32 node-5 multipathd: uevent trigger error
Jul 29 06:55:32 node-5 puppet-user[9415]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 29 06:55:32 node-5 puppet-user[9415]: Compiled catalog for node-5.domain.tld in environment production in 0.09 seconds
Jul 29 06:55:33 node-5 puppet-user[9415]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 29 06:55:33 node-5 puppet-user[9415]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 29 06:55:33 node-5 puppet-user[9415]: (/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 29 06:55:33 node-5 puppet-user[9415]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 29 06:55:33 node-5 puppet-user[9415]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 29 06:55:33 node-5 puppet-user[9415]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 29 06:55:33 node-5 puppet-user[9415]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 29 06:55:33 node-5 puppet-user[9415]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 29 06:55:33 node-5 puppet-user[9415]: Finished catalog run in 0.07 seconds
Jul 29 06:55:34 node-5 puppet-user[9872]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 29 06:55:34 node-5 puppet-user[9872]: Compiled catalog for node-5.domain.tld in environment production in 0.09 seconds
Jul 29 06:55:34 node-5 puppet-user[9872]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 29 06:55:34 node-5 puppet-user[9872]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 29 06:55:34 node-5 puppet-user[9872]: Finished catalog run in 0.02 seconds
Jul 29 06:55:36 node-5 puppet-user[10463]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 29 06:55:36 node-5 puppet-user[10463]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Jul 29 06:55:36 node-5 puppet-user[10463]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 29 06:55:36 node-5 puppet-user[10463]: Finished catalog run in 0.05 seconds
Jul 29 06:55:37 node-5 puppet-user[10932]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 29 06:55:37 node-5 puppet-user[10932]: Compiled catalog for node-5.domain.tld in environment production in 0.17 seconds
Jul 29 06:55:38 node-5 puppet-user[10932]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 29 06:55:39 node-5 puppet-user[10932]: (/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 29 06:55:39 node-5 puppet-user[10932]: Finished catalog run in 1.88 seconds
Jul 29 06:55:41 node-5 puppet-user[11471]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 29 06:55:41 node-5 puppet-user[11471]: Compiled catalog for node-5.domain.tld in environment production in 0.20 seconds
Jul 29 06:55:41 node-5 puppet-user[11471]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 29 06:55:41 node-5 puppet-user[11471]: (/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 29 06:55:41 node-5 puppet-user[11471]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 29 06:55:42 node-5 puppet-user[11471]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 29 06:55:42 node-5 puppet-user[11471]: Finished catalog run in 0.21 seconds
Jul 29 06:55:43 node-5 puppet-user[11950]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 29 06:55:43 node-5 puppet-user[11950]: Compiled catalog for node-5.domain.tld in environment production in 0.14 seconds
Jul 29 06:55:43 node-5 puppet-user[11950]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 29 06:55:43 node-5 kernel: [   67.972269] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 29 06:55:43 node-5 kernel: [   67.972318] 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 29 06:55:43 node-5 puppet-user[11950]: (/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 29 06:55:43 node-5 puppet-user[11950]: Finished catalog run in 0.05 seconds
Jul 29 06:55:45 node-5 puppet-user[12407]: (Scope(Class[main])) MODULAR: sync_time
Jul 29 06:55:45 node-5 puppet-user[12407]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Jul 29 06:55:45 node-5 ntpdate[12831]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 29 06:55:51 node-5 ntpdate[12831]: adjust time server 10.20.0.2 offset 0.000632 sec
Jul 29 06:55:51 node-5 puppet-user[12407]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 29 06:55:51 node-5 puppet-user[12407]: Finished catalog run in 6.15 seconds
Jul 29 06:55:56 node-5 puppet-user[13223]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 29 06:55:56 node-5 puppet-user[13223]: Compiled catalog for node-5.domain.tld in environment production in 0.07 seconds
Jul 29 06:55:56 node-5 puppet-user[13223]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 29 06:55:56 node-5 puppet-user[13223]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Jul 29 06:55:56 node-5 puppet-user[13223]: Finished catalog run in 0.07 seconds
Jul 29 06:55:57 node-5 puppet-user[13681]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 29 06:55:58 node-5 puppet-user[13681]: Compiled catalog for node-5.domain.tld in environment production in 0.71 seconds
Jul 29 06:55:58 node-5 puppet-user[13681]: (/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 29 06:55:58 node-5 puppet-user[13681]: (/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 29 06:55:58 node-5 puppet-user[13681]: (/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 29 06:55:58 node-5 puppet-user[13681]: (/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 29 06:55:59 node-5 puppet-user[13681]: (/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 29 06:55:59 node-5 puppet-user[13681]: (/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 29 06:55:59 node-5 puppet-user[13681]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 29 06:55:59 node-5 puppet-user[13681]: (/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 29 06:55:59 node-5 puppet-user[13681]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 29 06:55:59 node-5 puppet-user[13681]: (/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 29 06:55:59 node-5 puppet-user[13681]: (/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 29 06:55:59 node-5 puppet-user[13681]: (/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 29 06:55:59 node-5 puppet-user[13681]: (/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 29 06:55:59 node-5 puppet-user[13681]: (/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 29 06:55:59 node-5 puppet-user[13681]: (/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 29 06:55:59 node-5 puppet-user[13681]: (/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 29 06:55:59 node-5 kernel: [   84.089807] init: plymouth-upstart-bridge main process ended, respawning
Jul 29 06:56:00 node-5 puppet-agent[8916]: Could not run: SIGTERM
Jul 29 06:56:00 node-5 kernel: [   84.362290] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 29 06:56:00 node-5 ec2: 
Jul 29 06:56:00 node-5 ec2: #############################################################
Jul 29 06:56:00 node-5 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 29 06:56:00 node-5 ec2: 1024 4a:3a:4d:4c:a0:46:6a:1f:7f:4e:33:27:b0:4b:22:bf  root@node-5.domain.tld (DSA)
Jul 29 06:56:00 node-5 ec2: 256 1d:e2:c0:fa:eb:ee:48:92:41:62:97:1a:75:2e:e8:51  root@node-5.domain.tld (ECDSA)
Jul 29 06:56:00 node-5 ec2: 256 86:35:2d:6e:68:cf:28:f8:c9:14:c5:80:d0:3a:9f:7b  root@node-5.domain.tld (ED25519)
Jul 29 06:56:00 node-5 ec2: 2048 10:91:f5:3f:86:1a:c0:fd:52:9f:8f:83:f8:96:2d:19  root@node-5.domain.tld (RSA)
Jul 29 06:56:00 node-5 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 29 06:56:00 node-5 ec2: #############################################################
Jul 29 06:56:01 node-5 CRON[14398]: (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 29 06:56:01 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 06:56:01 node-5 nailgun-agent: I, [2016-07-29T06:56:01.562285 #14401]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 06:56:14 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 06:56:14 node-5 nailgun-agent: I, [2016-07-29T06:56:14.408091 #14401]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 29 06:56:16 node-5 puppet-user[13681]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 29 06:56:16 node-5 puppet-user[13681]: Finished catalog run in 18.13 seconds
Jul 29 06:56:18 node-5 puppet-user[15177]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 29 06:56:19 node-5 puppet-user[15177]: Compiled catalog for node-5.domain.tld in environment production in 0.15 seconds
Jul 29 06:56:23 node-5 puppet-user[15177]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 29 06:56:55 node-5 puppet-user[15177]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 29 06:56:55 node-5 puppet-user[15177]: Finished catalog run in 36.22 seconds
Jul 29 06:56:57 node-5 puppet-user[17658]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 29 06:56:57 node-5 puppet-user[17658]: Compiled catalog for node-5.domain.tld in environment production in 0.57 seconds
Jul 29 06:56:57 node-5 puppet-user[17658]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 29 06:56:57 node-5 puppet-user[17658]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 29 06:56:57 node-5 puppet-user[17658]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 29 06:56:57 node-5 puppet-user[17658]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 29 06:56:58 node-5 puppet-user[17658]: Finished catalog run in 0.11 seconds
Jul 29 06:56:59 node-5 puppet-user[18112]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 29 06:57:00 node-5 puppet-user[18112]: Compiled catalog for node-5.domain.tld in environment production in 0.92 seconds
Jul 29 06:57:01 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 29 06:57:01 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 29 06:57:01 node-5 crontab[18558]: (root) LIST (root)
Jul 29 06:57:01 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 29 06:57:01 node-5 crontab[18559]: (root) REPLACE (root)
Jul 29 06:57:01 node-5 CRON[18587]: (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 29 06:57:03 node-5 puppet-user[18112]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 29 06:57:03 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 06:57:03 node-5 nailgun-agent: I, [2016-07-29T06:57:03.573661 #18590]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 29 06:57:04 node-5 puppet-user[18112]: (/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 29 06:57:04 node-5 puppet-user[18112]: (/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 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 29 06:57:04 node-5 puppet-user[18112]: (/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 29 06:57:04 node-5 puppet-user[18112]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 29 06:57:05 node-5 puppet-user[18112]: (/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 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 29 06:57:05 node-5 puppet-user[18112]: (/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 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 29 06:57:05 node-5 puppet-user[18112]: (/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 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 29 06:57:05 node-5 puppet-user[18112]: (/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 29 06:57:05 node-5 puppet-user[18112]: (/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 29 06:57:05 node-5 puppet-user[18112]: (/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 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 29 06:57:05 node-5 puppet-user[18112]: (/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 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 29 06:57:05 node-5 puppet-user[18112]: (/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 29 06:57:05 node-5 puppet-user[18112]: (/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 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 29 06:57:05 node-5 puppet-user[18112]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 29 06:57:05 node-5 puppet-user[18112]: (/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 29 06:57:05 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8367" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 06:57:05 node-5 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 29 06:57:07 node-5 multipathd: uevent trigger error
<27>Jul 29 06:57:07 node-5 multipathd: uevent trigger error
<27>Jul 29 06:57:07 node-5 multipathd: uevent trigger error
<27>Jul 29 06:57:07 node-5 multipathd: uevent trigger error
<27>Jul 29 06:57:07 node-5 multipathd: uevent trigger error
<27>Jul 29 06:57:07 node-5 multipathd: uevent trigger error
<27>Jul 29 06:57:26 node-5 multipathd: uevent trigger error
<27>Jul 29 06:57:26 node-5 multipathd: uevent trigger error
<27>Jul 29 06:57:26 node-5 multipathd: uevent trigger error
<27>Jul 29 06:57:26 node-5 multipathd: uevent trigger error
<27>Jul 29 06:58:14 node-5 multipathd: uevent trigger error
<27>Jul 29 06:58:14 node-5 multipathd: uevent trigger error
<27>Jul 29 06:58:14 node-5 multipathd: uevent trigger error
<27>Jul 29 06:58:14 node-5 multipathd: uevent trigger error
<27>Jul 29 06:58:14 node-5 multipathd: uevent trigger error
<27>Jul 29 06:58:14 node-5 multipathd: uevent trigger error
<27>Jul 29 06:58:16 node-5 multipathd: uevent trigger error
<27>Jul 29 06:58:16 node-5 multipathd: uevent trigger error
<27>Jul 29 06:58:16 node-5 multipathd: uevent trigger error
<27>Jul 29 06:58:16 node-5 multipathd: uevent trigger error
<27>Jul 29 06:58:16 node-5 multipathd: uevent trigger error
<27>Jul 29 06:58:59 node-5 ntpdate[2351]: no servers can be used, exiting
<27>Jul 29 06:58:59 node-5 ntpdate[2570]: no servers can be used, exiting
<27>Jul 29 06:58:59 node-5 ntpdate[2652]: no servers can be used, exiting
<27>Jul 29 06:59:31 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:31 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:31 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:31 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:34 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:34 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:34 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:34 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:34 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:46 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:46 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:46 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:46 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:46 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:49 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:49 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:49 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:49 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:49 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:55 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:55 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:55 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:55 node-5 multipathd: uevent trigger error
<27>Jul 29 06:59:55 node-5 multipathd: uevent trigger error
<27>Jul 29 07:00:15 node-5 multipathd: uevent trigger error
<27>Jul 29 07:00:15 node-5 multipathd: uevent trigger error
<27>Jul 29 07:00:15 node-5 multipathd: uevent trigger error
<27>Jul 29 07:00:15 node-5 multipathd: uevent trigger error
<43>Jul 29 07:00:15 node-5 apache2_error [Fri Jul 29 07:00:08.339189 2016] [mpm_event:notice] [pid 12564:tid 140448490641280] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 07:00:15 node-5 apache2_error [Fri Jul 29 07:00:08.339282 2016] [core:notice] [pid 12564:tid 140448490641280] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 29 07:00:15 node-5 apache2_error [Fri Jul 29 07:00:10.519961 2016] [mpm_event:notice] [pid 12564:tid 140448490641280] AH00491: caught SIGTERM, shutting down
<43>Jul 29 07:00:15 node-5 apache2_error [Fri Jul 29 07:00:11.695085 2016] [mpm_worker:notice] [pid 12892:tid 140265461770112] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 07:00:15 node-5 apache2_error [Fri Jul 29 07:00:11.695145 2016] [core:notice] [pid 12892:tid 140265461770112] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 07:00:15 node-5 multipathd: uevent trigger error
<27>Jul 29 07:00:15 node-5 multipathd: uevent trigger error
<27>Jul 29 07:00:24 node-5 multipathd: uevent trigger error
<27>Jul 29 07:00:24 node-5 multipathd: uevent trigger error
<27>Jul 29 07:00:24 node-5 multipathd: uevent trigger error
<27>Jul 29 07:00:24 node-5 multipathd: uevent trigger error
<27>Jul 29 07:00:24 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:00 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:00 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:00 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:00 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:00 node-5 multipathd: uevent trigger error
<43>Jul 29 07:01:05 node-5 apache2_error [Fri Jul 29 07:00:57.442080 2016] [mpm_worker:notice] [pid 12892:tid 140265461770112] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 07:01:05 node-5 apache2_error [Fri Jul 29 07:00:57.449531 2016] [mpm_worker:warn] [pid 12892:tid 140265461770112] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 07:01:05 node-5 apache2_error [Fri Jul 29 07:00:57.450111 2016] [mpm_worker:notice] [pid 12892:tid 140265461770112] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 07:01:05 node-5 apache2_error [Fri Jul 29 07:00:57.450118 2016] [core:notice] [pid 12892:tid 140265461770112] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 07:01:35 node-5 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 29 07:01:40 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:40 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:40 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:40 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:40 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:44 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:44 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:44 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:44 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:50 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:50 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:50 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:50 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:50 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:50 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:57 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:57 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:57 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:57 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:57 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:57 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:57 node-5 multipathd: uevent trigger error
<27>Jul 29 07:01:57 node-5 multipathd: uevent trigger error
<129>Jul 29 07:02:01 node-5 haproxy[26871]: 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 29 07:02:02 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:02 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:02 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:02 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:02 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:06 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:06 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:06 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:06 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:06 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:06 node-5 multipathd: uevent trigger error
<129>Jul 29 07:02:09 node-5 haproxy[29155]: 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 29 07:02:10 node-5 haproxy[29155]: 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 29 07:02:11 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:11 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:11 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:11 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:11 node-5 multipathd: uevent trigger error
<129>Jul 29 07:02:13 node-5 haproxy[30291]: 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 29 07:02:14 node-5 haproxy[30295]: 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 29 07:02:15 node-5 haproxy[30295]: 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 29 07:02:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:16 node-5 multipathd: uevent trigger error
<129>Jul 29 07:02:19 node-5 haproxy[31607]: 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 29 07:02:19 node-5 haproxy[31607]: 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 29 07:02:19 node-5 haproxy[31607]: 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 29 07:02:20 node-5 haproxy[31607]: 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 29 07:02:20 node-5 haproxy[31607]: 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 29 07:02:21 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:21 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:21 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:21 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:21 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:21 node-5 multipathd: uevent trigger error
<129>Jul 29 07:02:24 node-5 haproxy[32749]: 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 29 07:02:24 node-5 haproxy[32749]: 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 29 07:02:24 node-5 haproxy[32749]: 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 29 07:02:25 node-5 haproxy[32749]: 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 29 07:02:25 node-5 haproxy[32749]: 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 29 07:02:25 node-5 haproxy[32749]: 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 29 07:02:27 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:27 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:27 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:27 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:27 node-5 multipathd: uevent trigger error
<129>Jul 29 07:02:27 node-5 haproxy[32749]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:27 node-5 haproxy[32749]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:02:27 node-5 haproxy[32749]: proxy aodh has no server available!
<129>Jul 29 07:02:29 node-5 haproxy[1456]: 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 29 07:02:29 node-5 haproxy[1456]: 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 29 07:02:30 node-5 haproxy[1465]: 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 29 07:02:30 node-5 haproxy[1465]: 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 29 07:02:30 node-5 haproxy[1465]: 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 29 07:02:30 node-5 haproxy[1465]: 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 29 07:02:31 node-5 haproxy[1465]: 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 29 07:02:32 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:32 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:32 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:32 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:32 node-5 multipathd: uevent trigger error
<129>Jul 29 07:02:32 node-5 haproxy[1465]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:32 node-5 haproxy[1465]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:02:32 node-5 haproxy[1465]: proxy aodh has no server available!
<129>Jul 29 07:02:32 node-5 haproxy[1465]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:33 node-5 haproxy[1465]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:02:33 node-5 haproxy[1465]: proxy ceilometer has no server available!
<129>Jul 29 07:02:34 node-5 haproxy[2570]: 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 29 07:02:34 node-5 haproxy[2570]: 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 29 07:02:35 node-5 haproxy[2574]: 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 29 07:02:35 node-5 haproxy[2574]: 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 29 07:02:35 node-5 haproxy[2574]: 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 29 07:02:36 node-5 haproxy[2574]: 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 29 07:02:36 node-5 haproxy[2574]: 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 29 07:02:37 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:37 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:37 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:37 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:37 node-5 multipathd: uevent trigger error
<129>Jul 29 07:02:37 node-5 haproxy[2574]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:38 node-5 haproxy[2574]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:02:38 node-5 haproxy[2574]: proxy aodh has no server available!
<129>Jul 29 07:02:38 node-5 haproxy[2574]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:38 node-5 haproxy[2574]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:02:38 node-5 haproxy[2574]: proxy ceilometer has no server available!
<129>Jul 29 07:02:40 node-5 haproxy[3699]: 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 29 07:02:40 node-5 haproxy[3699]: 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 29 07:02:40 node-5 haproxy[3699]: 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 29 07:02:40 node-5 haproxy[3699]: 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 29 07:02:41 node-5 haproxy[3699]: 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 29 07:02:41 node-5 haproxy[3699]: 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 29 07:02:41 node-5 haproxy[3699]: 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 29 07:02:41 node-5 haproxy[3699]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:41 node-5 haproxy[3699]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 07:02:42 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:42 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:42 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:42 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:42 node-5 multipathd: uevent trigger error
<129>Jul 29 07:02:43 node-5 haproxy[3699]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:43 node-5 haproxy[3699]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:02:43 node-5 haproxy[3699]: proxy aodh has no server available!
<129>Jul 29 07:02:43 node-5 haproxy[3699]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:43 node-5 haproxy[3699]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:02:43 node-5 haproxy[3699]: proxy ceilometer has no server available!
<129>Jul 29 07:02:45 node-5 haproxy[4856]: 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 29 07:02:45 node-5 haproxy[4856]: 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 29 07:02:45 node-5 haproxy[4856]: 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 29 07:02:46 node-5 haproxy[4864]: 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 29 07:02:46 node-5 haproxy[4864]: 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 29 07:02:46 node-5 haproxy[4864]: 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 29 07:02:46 node-5 haproxy[4864]: 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 29 07:02:46 node-5 haproxy[4864]: 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 29 07:02:47 node-5 haproxy[4864]: 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 29 07:02:47 node-5 haproxy[4864]: 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 29 07:02:47 node-5 haproxy[4864]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:47 node-5 haproxy[4864]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 07:02:48 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:48 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:48 node-5 multipathd: uevent trigger error
<129>Jul 29 07:02:48 node-5 haproxy[4864]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 07:02:48 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:48 node-5 multipathd: uevent trigger error
<129>Jul 29 07:02:48 node-5 haproxy[4864]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:02:48 node-5 haproxy[4864]: proxy glance-registry has no server available!
<129>Jul 29 07:02:48 node-5 haproxy[4864]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:49 node-5 haproxy[4864]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:02:49 node-5 haproxy[4864]: proxy aodh has no server available!
<129>Jul 29 07:02:49 node-5 haproxy[4864]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:49 node-5 haproxy[4864]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:02:49 node-5 haproxy[4864]: proxy ceilometer has no server available!
<129>Jul 29 07:02:51 node-5 haproxy[6019]: 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 29 07:02:51 node-5 haproxy[6019]: 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 29 07:02:51 node-5 haproxy[6019]: 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 29 07:02:51 node-5 haproxy[6019]: 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 29 07:02:51 node-5 haproxy[6019]: 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 29 07:02:51 node-5 haproxy[6019]: 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 29 07:02:52 node-5 haproxy[6019]: 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 29 07:02:52 node-5 haproxy[6019]: 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 29 07:02:52 node-5 haproxy[6019]: 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 29 07:02:52 node-5 haproxy[6019]: 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 29 07:02:52 node-5 haproxy[6019]: 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 29 07:02:52 node-5 haproxy[6019]: 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 29 07:02:52 node-5 haproxy[6019]: 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 29 07:02:52 node-5 haproxy[6019]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:52 node-5 haproxy[6019]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:54 node-5 haproxy[6019]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 07:02:54 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:54 node-5 multipathd: uevent trigger error
<129>Jul 29 07:02:54 node-5 haproxy[6019]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:02:54 node-5 haproxy[6019]: proxy glance-registry has no server available!
<27>Jul 29 07:02:54 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:54 node-5 multipathd: uevent trigger error
<129>Jul 29 07:02:54 node-5 haproxy[6019]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:54 node-5 haproxy[6019]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:02:54 node-5 haproxy[6019]: proxy aodh has no server available!
<129>Jul 29 07:02:54 node-5 haproxy[6019]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:54 node-5 haproxy[6019]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:02:54 node-5 haproxy[6019]: proxy ceilometer has no server available!
<129>Jul 29 07:02:54 node-5 haproxy[6019]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:54 node-5 haproxy[6019]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:02:54 node-5 haproxy[6019]: proxy nova-novncproxy has no server available!
<129>Jul 29 07:02:56 node-5 haproxy[7154]: 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 29 07:02:56 node-5 haproxy[7154]: 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 29 07:02:56 node-5 haproxy[7154]: 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 29 07:02:56 node-5 haproxy[7154]: 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 29 07:02:56 node-5 haproxy[7154]: 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 29 07:02:57 node-5 haproxy[7158]: 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 29 07:02:57 node-5 haproxy[7158]: 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 29 07:02:57 node-5 haproxy[7158]: 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 29 07:02:57 node-5 haproxy[7158]: 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 29 07:02:57 node-5 haproxy[7158]: 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 29 07:02:57 node-5 haproxy[7158]: 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 29 07:02:57 node-5 haproxy[7158]: 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 29 07:02:58 node-5 haproxy[7158]: 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 29 07:02:58 node-5 haproxy[7158]: 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 29 07:02:58 node-5 haproxy[7158]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:58 node-5 haproxy[7158]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 07:02:59 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:59 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:59 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:59 node-5 multipathd: uevent trigger error
<27>Jul 29 07:02:59 node-5 multipathd: uevent trigger error
<129>Jul 29 07:02:59 node-5 haproxy[7158]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:59 node-5 haproxy[7158]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:02:59 node-5 haproxy[7158]: proxy glance-registry has no server available!
<129>Jul 29 07:02:59 node-5 haproxy[7158]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:02:59 node-5 haproxy[7158]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:02:59 node-5 haproxy[7158]: proxy aodh has no server available!
<129>Jul 29 07:02:59 node-5 haproxy[7158]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:00 node-5 haproxy[7158]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:00 node-5 haproxy[7158]: proxy ceilometer has no server available!
<129>Jul 29 07:03:00 node-5 haproxy[7158]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:00 node-5 haproxy[7158]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:00 node-5 haproxy[7158]: proxy nova-novncproxy has no server available!
<27>Jul 29 07:03:01 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Jul 29 07:03:02 node-5 haproxy[8354]: 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 29 07:03:02 node-5 haproxy[8354]: 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 29 07:03:02 node-5 haproxy[8354]: 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 29 07:03:02 node-5 haproxy[8354]: 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 29 07:03:02 node-5 haproxy[8354]: 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 29 07:03:02 node-5 haproxy[8354]: 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 29 07:03:02 node-5 haproxy[8354]: 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 29 07:03:02 node-5 haproxy[8354]: 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 29 07:03:02 node-5 haproxy[8354]: 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 29 07:03:03 node-5 haproxy[8354]: 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 29 07:03:03 node-5 haproxy[8354]: 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 29 07:03:03 node-5 haproxy[8354]: 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 29 07:03:03 node-5 haproxy[8354]: 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 29 07:03:03 node-5 haproxy[8354]: 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 29 07:03:03 node-5 haproxy[8354]: 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 29 07:03:03 node-5 haproxy[8354]: 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 29 07:03:03 node-5 haproxy[8354]: 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 29 07:03:03 node-5 haproxy[8354]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:03 node-5 haproxy[8354]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:04 node-5 haproxy[8354]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:04 node-5 haproxy[8354]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:04 node-5 haproxy[8354]: proxy glance-registry has no server available!
<27>Jul 29 07:03:04 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:05 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:05 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:05 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:05 node-5 multipathd: uevent trigger error
<129>Jul 29 07:03:05 node-5 haproxy[8354]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:05 node-5 haproxy[8354]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:05 node-5 haproxy[8354]: proxy aodh has no server available!
<129>Jul 29 07:03:05 node-5 haproxy[8354]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:05 node-5 haproxy[8354]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:05 node-5 haproxy[8354]: proxy ceilometer has no server available!
<129>Jul 29 07:03:05 node-5 haproxy[8354]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:05 node-5 haproxy[8354]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:05 node-5 haproxy[8354]: proxy nova-novncproxy has no server available!
<27>Jul 29 07:03:08 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:08 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:08 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:08 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:08 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:08 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:11 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:11 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:11 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:11 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:11 node-5 multipathd: uevent trigger error
<129>Jul 29 07:03:11 node-5 haproxy[8354]: Server keystone-1/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:12 node-5 haproxy[8354]: Server keystone-1/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:12 node-5 haproxy[8354]: proxy keystone-1 has no server available!
<129>Jul 29 07:03:12 node-5 haproxy[8354]: Server keystone-2/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:12 node-5 haproxy[8354]: Server keystone-2/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:12 node-5 haproxy[8354]: proxy keystone-2 has no server available!
<129>Jul 29 07:03:12 node-5 haproxy[8354]: Server nova-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:12 node-5 haproxy[8354]: Server nova-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:12 node-5 haproxy[8354]: proxy nova-api has no server available!
<129>Jul 29 07:03:12 node-5 haproxy[8354]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:12 node-5 haproxy[8354]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:12 node-5 haproxy[8354]: proxy nova-metadata-api has no server available!
<129>Jul 29 07:03:12 node-5 haproxy[8354]: Server cinder-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:12 node-5 haproxy[8354]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:12 node-5 haproxy[8354]: proxy cinder-api has no server available!
<129>Jul 29 07:03:12 node-5 haproxy[8354]: Server glance-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:12 node-5 haproxy[8354]: Server glance-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:12 node-5 haproxy[8354]: proxy glance-api has no server available!
<129>Jul 29 07:03:12 node-5 haproxy[8354]: Server glance-glare/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:12 node-5 haproxy[8354]: Server glance-glare/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:12 node-5 haproxy[8354]: proxy glance-glare has no server available!
<129>Jul 29 07:03:12 node-5 haproxy[8354]: Server neutron/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:12 node-5 haproxy[8354]: Server neutron/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:12 node-5 haproxy[8354]: proxy neutron has no server available!
<129>Jul 29 07:03:12 node-5 haproxy[8354]: Server mysqld/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:13 node-5 haproxy[8354]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:13 node-5 haproxy[8354]: proxy mysqld has no server available!
<129>Jul 29 07:03:13 node-5 haproxy[8354]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:13 node-5 haproxy[8354]: Server object-storage/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:13 node-5 haproxy[8354]: proxy object-storage has no server available!
<129>Jul 29 07:03:13 node-5 haproxy[8354]: Server heat-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:13 node-5 haproxy[8354]: Server heat-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:13 node-5 haproxy[8354]: proxy heat-api has no server available!
<129>Jul 29 07:03:13 node-5 haproxy[8354]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:13 node-5 haproxy[8354]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:13 node-5 haproxy[8354]: proxy heat-api-cfn has no server available!
<129>Jul 29 07:03:13 node-5 haproxy[8354]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 07:03:13 node-5 haproxy[8354]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:03:13 node-5 haproxy[8354]: proxy heat-api-cloudwatch has no server available!
<27>Jul 29 07:03:15 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:15 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:15 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:15 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:15 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:33 node-5 multipathd: uevent trigger error
<27>Jul 29 07:03:55 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 29 07:03:55 node-5 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 29 07:03:59 node-5 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 29 07:03:59 node-5 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 29 07:03:59 node-5 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 29 07:04:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:04:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:04:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:04:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:04:29 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 29 07:04:56 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 29 07:04:58 node-5 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 29 07:06:13 node-5 multipathd: uevent trigger error
<27>Jul 29 07:06:13 node-5 multipathd: uevent trigger error
<27>Jul 29 07:06:13 node-5 multipathd: uevent trigger error
<27>Jul 29 07:06:13 node-5 multipathd: uevent trigger error
<27>Jul 29 07:06:13 node-5 multipathd: uevent trigger error
<27>Jul 29 07:06:13 node-5 multipathd: uevent trigger error
<11>Jul 29 07:07:14 node-5 epmd: epmd: node name already occupied rabbitmq-cli-92
<11>Jul 29 07:07:19 node-5 epmd: epmd: node name already occupied rabbitmq-cli-92
<27>Jul 29 07:07:33 node-5 multipathd: uevent trigger error
<27>Jul 29 07:07:33 node-5 multipathd: uevent trigger error
<27>Jul 29 07:07:33 node-5 multipathd: uevent trigger error
<27>Jul 29 07:07:33 node-5 multipathd: uevent trigger error
<27>Jul 29 07:07:33 node-5 multipathd: uevent trigger error
<11>Jul 29 07:08:27 node-5 epmd: epmd: node name already occupied rabbitmq-cli-92
<11>Jul 29 07:09:01 node-5 epmd: epmd: node name already occupied rabbitmq-cli-92
<27>Jul 29 07:10:45 node-5 multipathd: uevent trigger error
<27>Jul 29 07:10:45 node-5 multipathd: uevent trigger error
<27>Jul 29 07:10:45 node-5 multipathd: uevent trigger error
<27>Jul 29 07:10:45 node-5 multipathd: uevent trigger error
<27>Jul 29 07:10:45 node-5 multipathd: uevent trigger error
<43>Jul 29 07:11:56 node-5 apache2_error [Fri Jul 29 07:11:55.114883 2016] [mpm_worker:notice] [pid 12892:tid 140265461770112] AH00295: caught SIGTERM, shutting down
<43>Jul 29 07:11:56 node-5 apache2_error [Fri Jul 29 07:11:55.863224 2016] [mpm_worker:notice] [pid 26032:tid 140581433239424] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 07:11:56 node-5 apache2_error [Fri Jul 29 07:11:55.863274 2016] [core:notice] [pid 26032:tid 140581433239424] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 07:12:33 node-5 multipathd: uevent trigger error
<27>Jul 29 07:12:33 node-5 multipathd: uevent trigger error
<27>Jul 29 07:12:33 node-5 multipathd: uevent trigger error
<27>Jul 29 07:12:33 node-5 multipathd: uevent trigger error
<27>Jul 29 07:12:33 node-5 multipathd: uevent trigger error
<43>Jul 29 07:12:36 node-5 apache2_error [Fri Jul 29 07:12:27.873169 2016] [mpm_worker:notice] [pid 26032:tid 140581433239424] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 07:12:36 node-5 apache2_error [Fri Jul 29 07:12:27.884639 2016] [mpm_worker:warn] [pid 26032:tid 140581433239424] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 07:12:36 node-5 apache2_error [Fri Jul 29 07:12:27.888952 2016] [mpm_worker:notice] [pid 26032:tid 140581433239424] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 07:12:36 node-5 apache2_error [Fri Jul 29 07:12:27.888973 2016] [core:notice] [pid 26032:tid 140581433239424] AH00094: Command line: '/usr/sbin/apache2'
<11>Jul 29 07:13:00 node-5 epmd: epmd: node name already occupied rabbitmq-cli-92
<27>Jul 29 07:13:29 node-5 multipathd: uevent trigger error
<27>Jul 29 07:13:29 node-5 multipathd: uevent trigger error
<27>Jul 29 07:13:29 node-5 multipathd: uevent trigger error
<27>Jul 29 07:13:29 node-5 multipathd: uevent trigger error
<27>Jul 29 07:13:29 node-5 multipathd: uevent trigger error
<11>Jul 29 07:14:36 node-5 epmd: epmd: node name already occupied rabbitmq-cli-92
<27>Jul 29 07:14:43 node-5 multipathd: uevent trigger error
<27>Jul 29 07:14:43 node-5 multipathd: uevent trigger error
<27>Jul 29 07:14:43 node-5 multipathd: uevent trigger error
<27>Jul 29 07:14:44 node-5 multipathd: uevent trigger error
<27>Jul 29 07:14:44 node-5 multipathd: uevent trigger error
<11>Jul 29 07:18:44 node-5 epmd: epmd: node name already occupied rabbitmq-cli-92
<27>Jul 29 07:19:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:19:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:19:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:19:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:19:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:19:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:19:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:19:20 node-5 multipathd: uevent trigger error
<11>Jul 29 07:20:28 node-5 epmd: epmd: node name already occupied rabbitmq-cli-92
<27>Jul 29 07:21:32 node-5 multipathd: uevent trigger error
<27>Jul 29 07:21:32 node-5 multipathd: uevent trigger error
<27>Jul 29 07:21:32 node-5 multipathd: uevent trigger error
<27>Jul 29 07:21:32 node-5 multipathd: uevent trigger error
<27>Jul 29 07:21:32 node-5 multipathd: uevent trigger error
<27>Jul 29 07:22:41 node-5 multipathd: uevent trigger error
<27>Jul 29 07:22:41 node-5 multipathd: uevent trigger error
<27>Jul 29 07:22:41 node-5 multipathd: uevent trigger error
<27>Jul 29 07:22:41 node-5 multipathd: uevent trigger error
<27>Jul 29 07:22:41 node-5 multipathd: uevent trigger error
<27>Jul 29 07:22:41 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:17 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:17 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:17 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:17 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:17 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:17 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:26 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:26 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:26 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:26 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:26 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:26 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:38 node-5 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Jul 29 07:23:38 node-5 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Jul 29 07:23:38 node-5 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Jul 29 07:23:39 node-5 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Jul 29 07:23:40 node-5 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Jul 29 07:23:40 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:40 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:40 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:40 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:40 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:59 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:59 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:59 node-5 multipathd: uevent trigger error
<27>Jul 29 07:23:59 node-5 multipathd: uevent trigger error
<27>Jul 29 07:24:04 node-5 multipathd: uevent trigger error
<27>Jul 29 07:24:04 node-5 multipathd: uevent trigger error
<27>Jul 29 07:24:04 node-5 multipathd: uevent trigger error
<27>Jul 29 07:24:04 node-5 multipathd: uevent trigger error
<27>Jul 29 07:24:04 node-5 multipathd: uevent trigger error
<43>Jul 29 07:24:57 node-5 apache2_error [Fri Jul 29 07:24:50.505687 2016] [mpm_worker:notice] [pid 26032:tid 140581433239424] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 07:24:57 node-5 apache2_error [Fri Jul 29 07:24:50.890575 2016] [mpm_worker:warn] [pid 26032:tid 140581433239424] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 07:24:57 node-5 apache2_error [Fri Jul 29 07:24:50.897053 2016] [mpm_worker:notice] [pid 26032:tid 140581433239424] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 07:24:57 node-5 apache2_error [Fri Jul 29 07:24:50.897090 2016] [core:notice] [pid 26032:tid 140581433239424] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 07:25:32 node-5 multipathd: uevent trigger error
<27>Jul 29 07:25:32 node-5 multipathd: uevent trigger error
<27>Jul 29 07:25:32 node-5 multipathd: uevent trigger error
<27>Jul 29 07:25:32 node-5 multipathd: uevent trigger error
<27>Jul 29 07:25:32 node-5 multipathd: uevent trigger error
<27>Jul 29 07:25:32 node-5 multipathd: uevent trigger error
<43>Jul 29 07:25:37 node-5 apache2_error [Fri Jul 29 07:25:27.654573 2016] [mpm_worker:notice] [pid 26032:tid 140581433239424] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 07:25:37 node-5 apache2_error [Fri Jul 29 07:25:28.040364 2016] [mpm_worker:warn] [pid 26032:tid 140581433239424] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 07:25:37 node-5 apache2_error [Fri Jul 29 07:25:28.048592 2016] [mpm_worker:notice] [pid 26032:tid 140581433239424] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 07:25:37 node-5 apache2_error [Fri Jul 29 07:25:28.048623 2016] [core:notice] [pid 26032:tid 140581433239424] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 07:26:11 node-5 multipathd: uevent trigger error
<27>Jul 29 07:26:11 node-5 multipathd: uevent trigger error
<27>Jul 29 07:26:11 node-5 multipathd: uevent trigger error
<27>Jul 29 07:26:11 node-5 multipathd: uevent trigger error
<27>Jul 29 07:26:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:26:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:26:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:26:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:26:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:27:51 node-5 multipathd: uevent trigger error
<27>Jul 29 07:27:51 node-5 multipathd: uevent trigger error
<27>Jul 29 07:27:51 node-5 multipathd: uevent trigger error
<27>Jul 29 07:27:51 node-5 multipathd: uevent trigger error
<27>Jul 29 07:27:51 node-5 multipathd: uevent trigger error
<27>Jul 29 07:28:40 node-5 multipathd: uevent trigger error
<27>Jul 29 07:28:40 node-5 multipathd: uevent trigger error
<27>Jul 29 07:28:40 node-5 multipathd: uevent trigger error
<27>Jul 29 07:28:40 node-5 multipathd: uevent trigger error
<27>Jul 29 07:28:40 node-5 multipathd: uevent trigger error
<27>Jul 29 07:28:52 node-5 multipathd: uevent trigger error
<27>Jul 29 07:28:52 node-5 multipathd: uevent trigger error
<27>Jul 29 07:28:52 node-5 multipathd: uevent trigger error
<27>Jul 29 07:28:52 node-5 multipathd: uevent trigger error
<27>Jul 29 07:28:52 node-5 multipathd: uevent trigger error
<11>Jul 29 07:29:01 node-5 liberasurecode[26481]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:01 node-5 liberasurecode[26481]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:01 node-5 liberasurecode[26481]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:01 node-5 liberasurecode[26481]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:01 node-5 liberasurecode[26505]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:01 node-5 liberasurecode[26505]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:01 node-5 liberasurecode[26505]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:01 node-5 liberasurecode[26505]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:04 node-5 liberasurecode[27056]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:04 node-5 liberasurecode[27056]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:04 node-5 liberasurecode[27056]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:04 node-5 liberasurecode[27056]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[28967]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[28967]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[28967]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[28967]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[29041]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[29041]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[29041]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[29041]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[29155]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[29155]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[29155]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[29155]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[29328]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[29328]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[29328]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[29328]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[29342]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[29342]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[29342]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:09 node-5 liberasurecode[29342]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:10 node-5 liberasurecode[29354]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:10 node-5 liberasurecode[29354]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:10 node-5 liberasurecode[29354]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:10 node-5 liberasurecode[29354]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:10 node-5 liberasurecode[29398]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:10 node-5 liberasurecode[29398]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:10 node-5 liberasurecode[29398]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:29:10 node-5 liberasurecode[29398]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 29 07:29:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:29:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:29:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:29:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:29:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:29:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:29:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:29:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:29:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:29:25 node-5 multipathd: uevent trigger error
<27>Jul 29 07:29:26 node-5 multipathd: uevent trigger error
<27>Jul 29 07:29:26 node-5 multipathd: uevent trigger error
<27>Jul 29 07:29:26 node-5 multipathd: uevent trigger error
<27>Jul 29 07:29:26 node-5 multipathd: uevent trigger error
<11>Jul 29 07:30:02 node-5 liberasurecode[7368]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:30:02 node-5 liberasurecode[7368]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:30:02 node-5 liberasurecode[7368]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:30:02 node-5 liberasurecode[7368]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 29 07:31:53 node-5 multipathd: uevent trigger error
<27>Jul 29 07:31:54 node-5 multipathd: uevent trigger error
<27>Jul 29 07:31:54 node-5 multipathd: uevent trigger error
<27>Jul 29 07:31:54 node-5 multipathd: uevent trigger error
<11>Jul 29 07:32:52 node-5 epmd: epmd: node name already occupied rabbitmq-cli-92
<11>Jul 29 07:32:55 node-5 epmd: epmd: node name already occupied rabbitmq-cli-92
<11>Jul 29 07:34:13 node-5 epmd: epmd: node name already occupied rabbitmq-cli-92
<27>Jul 29 07:34:43 node-5 multipathd: uevent trigger error
<27>Jul 29 07:34:43 node-5 multipathd: uevent trigger error
<27>Jul 29 07:34:43 node-5 multipathd: uevent trigger error
<27>Jul 29 07:34:43 node-5 multipathd: uevent trigger error
<27>Jul 29 07:34:49 node-5 multipathd: uevent trigger error
<27>Jul 29 07:34:49 node-5 multipathd: uevent trigger error
<27>Jul 29 07:34:49 node-5 multipathd: uevent trigger error
<27>Jul 29 07:34:49 node-5 multipathd: uevent trigger error
<27>Jul 29 07:34:49 node-5 multipathd: uevent trigger error
<27>Jul 29 07:34:57 node-5 multipathd: uevent trigger error
<27>Jul 29 07:34:57 node-5 multipathd: uevent trigger error
<27>Jul 29 07:34:57 node-5 multipathd: uevent trigger error
<27>Jul 29 07:34:57 node-5 multipathd: uevent trigger error
<11>Jul 29 07:35:01 node-5 liberasurecode[32103]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:35:01 node-5 liberasurecode[32103]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:35:01 node-5 liberasurecode[32103]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 07:35:01 node-5 liberasurecode[32103]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<129>Jul 29 07:35:08 node-5 haproxy[28452]: 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.
<27>Jul 29 07:35:08 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:08 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:08 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:08 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:08 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:15 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:15 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:15 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:15 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:15 node-5 multipathd: uevent trigger error
<129>Jul 29 07:35:18 node-5 haproxy[28452]: Server neutron/node-1 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 29 07:35:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:20 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:34 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:34 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:34 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:34 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:34 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:34 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:45 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:45 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:45 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:45 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:45 node-5 multipathd: uevent trigger error
<129>Jul 29 07:35:58 node-5 haproxy[28452]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 07:35:58 node-5 haproxy[28452]: proxy neutron has no server available!
<27>Jul 29 07:35:58 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:58 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:58 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:58 node-5 multipathd: uevent trigger error
<27>Jul 29 07:35:58 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:03 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:03 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:03 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:03 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:03 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:07 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:07 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:07 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:07 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:12 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:12 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:12 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:12 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:12 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:12 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:16 node-5 multipathd: uevent trigger error
<27>Jul 29 07:36:16 node-5 multipathd: uevent trigger error
