Jul 24 09:52:18 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8406" x-info="http://www.rsyslog.com"] start
Jul 24 09:52:18 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 24 09:52:18 node-4 rsyslogd: rsyslogd's groupid changed to 104
Jul 24 09:52:18 node-4 rsyslogd: rsyslogd's userid changed to 101
Jul 24 09:52:18 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 24 09:52:18 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 24 09:52:18 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 24 09:52:18 node-4 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 24 09:52:18 node-4 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=5fce98ac-35c2-462c-a14c-31fdc31d12e2 nomdmonddf nomdmonisw
Jul 24 09:52:18 node-4 kernel: [    0.000000] KERNEL supported cpus:
Jul 24 09:52:18 node-4 kernel: [    0.000000]   Intel GenuineIntel
Jul 24 09:52:18 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Jul 24 09:52:18 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Jul 24 09:52:18 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 24 09:52:18 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 24 09:52:18 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 24 09:52:18 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 24 09:52:18 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 24 09:52:18 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 24 09:52:18 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 24 09:52:18 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 24 09:52:18 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 24 09:52:18 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 24 09:52:18 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 24 09:52:18 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 24 09:52:18 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 24 09:52:18 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 24 09:52:18 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 24 09:52:18 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 24 09:52:18 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 24 09:52:18 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 24 09:52:18 node-4 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 24 09:52:18 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 24 09:52:18 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 24 09:52:18 node-4 kernel: [    0.000000] No AGP bridge found
Jul 24 09:52:18 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 24 09:52:18 node-4 kernel: [    0.000000] MTRR default type: write-back
Jul 24 09:52:18 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 24 09:52:18 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Jul 24 09:52:18 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 24 09:52:18 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 24 09:52:18 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 24 09:52:18 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 24 09:52:18 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 24 09:52:18 node-4 kernel: [    0.000000]   2 disabled
Jul 24 09:52:18 node-4 kernel: [    0.000000]   3 disabled
Jul 24 09:52:18 node-4 kernel: [    0.000000]   4 disabled
Jul 24 09:52:18 node-4 kernel: [    0.000000]   5 disabled
Jul 24 09:52:18 node-4 kernel: [    0.000000]   6 disabled
Jul 24 09:52:18 node-4 kernel: [    0.000000]   7 disabled
Jul 24 09:52:18 node-4 kernel: [    0.000000]   8 disabled
Jul 24 09:52:18 node-4 kernel: [    0.000000]   9 disabled
Jul 24 09:52:18 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 24 09:52:18 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 24 09:52:18 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 24 09:52:18 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 24 09:52:18 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 24 09:52:18 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Jul 24 09:52:18 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 24 09:52:18 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 24 09:52:18 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 24 09:52:18 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 24 09:52:18 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 24 09:52:18 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 24 09:52:18 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 24 09:52:18 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 24 09:52:18 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 24 09:52:18 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 24 09:52:18 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 24 09:52:18 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 24 09:52:18 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 24 09:52:18 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 24 09:52:18 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 24 09:52:18 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 24 09:52:18 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 24 09:52:18 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 24 09:52:18 node-4 kernel: [    0.000000] Zone ranges:
Jul 24 09:52:18 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] Movable zone start for each node
Jul 24 09:52:18 node-4 kernel: [    0.000000] Early memory node ranges
Jul 24 09:52:18 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 24 09:52:18 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 24 09:52:18 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 24 09:52:18 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 24 09:52:18 node-4 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 24 09:52:18 node-4 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 24 09:52:18 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 24 09:52:18 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 24 09:52:18 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 24 09:52:18 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 24 09:52:18 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 24 09:52:18 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 24 09:52:18 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 24 09:52:18 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 24 09:52:18 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 24 09:52:18 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 24 09:52:18 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 24 09:52:18 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 24 09:52:18 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 24 09:52:18 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 24 09:52:18 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 24 09:52:18 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 24 09:52:18 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 24 09:52:18 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 24 09:52:18 node-4 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 24 09:52:18 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 24 09:52:18 node-4 kernel: [    0.000000] Policy zone: Normal
Jul 24 09:52:18 node-4 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=5fce98ac-35c2-462c-a14c-31fdc31d12e2 nomdmonddf nomdmonisw
Jul 24 09:52:18 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 24 09:52:18 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 24 09:52:18 node-4 kernel: [    0.000000] Checking aperture...
Jul 24 09:52:18 node-4 kernel: [    0.000000] No AGP bridge found
Jul 24 09:52:18 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 24 09:52:18 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 24 09:52:18 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 24 09:52:18 node-4 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 24 09:52:18 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 24 09:52:18 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 24 09:52:18 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 24 09:52:18 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 24 09:52:18 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 24 09:52:18 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 24 09:52:18 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 24 09:52:18 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 24 09:52:18 node-4 kernel: [    0.000000] console [tty0] enabled
Jul 24 09:52:18 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 24 09:52:18 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 24 09:52:18 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 24 09:52:18 node-4 kernel: [    0.000000] hpet clockevent registered
Jul 24 09:52:18 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 24 09:52:18 node-4 kernel: [    0.004000] tsc: Detected 3492.212 MHz processor
Jul 24 09:52:18 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.42 BogoMIPS (lpj=13968848)
Jul 24 09:52:18 node-4 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 24 09:52:18 node-4 kernel: [    0.000049] Security Framework initialized
Jul 24 09:52:18 node-4 kernel: [    0.000067] AppArmor: AppArmor initialized
Jul 24 09:52:18 node-4 kernel: [    0.000069] Yama: becoming mindful.
Jul 24 09:52:18 node-4 kernel: [    0.001463] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 24 09:52:18 node-4 kernel: [    0.006363] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 24 09:52:18 node-4 kernel: [    0.008290] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 24 09:52:18 node-4 kernel: [    0.008318] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 24 09:52:18 node-4 kernel: [    0.008610] Initializing cgroup subsys memory
Jul 24 09:52:18 node-4 kernel: [    0.008618] Initializing cgroup subsys devices
Jul 24 09:52:18 node-4 kernel: [    0.008620] Initializing cgroup subsys freezer
Jul 24 09:52:18 node-4 kernel: [    0.008621] Initializing cgroup subsys blkio
Jul 24 09:52:18 node-4 kernel: [    0.008623] Initializing cgroup subsys perf_event
Jul 24 09:52:18 node-4 kernel: [    0.008625] Initializing cgroup subsys hugetlb
Jul 24 09:52:18 node-4 kernel: [    0.008645] CPU: Physical Processor ID: 0
Jul 24 09:52:18 node-4 kernel: [    0.008646] CPU: Processor Core ID: 0
Jul 24 09:52:18 node-4 kernel: [    0.008650] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 24 09:52:18 node-4 kernel: [    0.008650] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 24 09:52:18 node-4 kernel: [    0.009343] mce: CPU supports 22 MCE banks
Jul 24 09:52:18 node-4 kernel: [    0.009371] CPU0: Thermal monitoring enabled (TM1)
Jul 24 09:52:18 node-4 kernel: [    0.009391] process: using mwait in idle threads
Jul 24 09:52:18 node-4 kernel: [    0.009394] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 24 09:52:18 node-4 kernel: [    0.009394] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 24 09:52:18 node-4 kernel: [    0.009394] tlb_flushall_shift: 6
Jul 24 09:52:18 node-4 kernel: [    0.009483] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 24 09:52:18 node-4 kernel: [    0.010207] ACPI: Core revision 20131115
Jul 24 09:52:18 node-4 kernel: [    0.022871] ACPI: All ACPI Tables successfully acquired
Jul 24 09:52:18 node-4 kernel: [    0.023033] ftrace: allocating 28617 entries in 112 pages
Jul 24 09:52:18 node-4 kernel: [    0.031830] dmar: Host address width 46
Jul 24 09:52:18 node-4 kernel: [    0.031832] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 24 09:52:18 node-4 kernel: [    0.031838] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 24 09:52:18 node-4 kernel: [    0.031840] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 24 09:52:18 node-4 kernel: [    0.031844] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 24 09:52:18 node-4 kernel: [    0.031845] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 24 09:52:18 node-4 kernel: [    0.031847] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 24 09:52:18 node-4 kernel: [    0.031848] dmar: ATSR flags: 0x0
Jul 24 09:52:18 node-4 kernel: [    0.031849] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 24 09:52:18 node-4 kernel: [    0.031850] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 24 09:52:18 node-4 kernel: [    0.031966] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 24 09:52:18 node-4 kernel: [    0.031967] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 24 09:52:18 node-4 kernel: [    0.031968] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 24 09:52:18 node-4 kernel: [    0.031969] HPET id 0 under DRHD base 0xc7ffc000
Jul 24 09:52:18 node-4 kernel: [    0.031970] Your BIOS is broken and requested that x2apic be disabled.
Jul 24 09:52:18 node-4 kernel: [    0.031970] This will slightly decrease performance.
Jul 24 09:52:18 node-4 kernel: [    0.031970] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 24 09:52:18 node-4 kernel: [    0.032402] Enabled IRQ remapping in xapic mode
Jul 24 09:52:18 node-4 kernel: [    0.032403] x2apic not enabled, IRQ remapping is in xapic mode
Jul 24 09:52:18 node-4 kernel: [    0.032407] Switched APIC routing to physical flat.
Jul 24 09:52:18 node-4 kernel: [    0.033035] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 24 09:52:18 node-4 kernel: [    0.072688] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 24 09:52:18 node-4 kernel: [    0.072693] TSC deadline timer enabled
Jul 24 09:52:18 node-4 kernel: [    0.072700] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 24 09:52:18 node-4 kernel: [    0.072707] ... version:                3
Jul 24 09:52:18 node-4 kernel: [    0.072708] ... bit width:              48
Jul 24 09:52:18 node-4 kernel: [    0.072708] ... generic registers:      4
Jul 24 09:52:18 node-4 kernel: [    0.072709] ... value mask:             0000ffffffffffff
Jul 24 09:52:18 node-4 kernel: [    0.072710] ... max period:             0000ffffffffffff
Jul 24 09:52:18 node-4 kernel: [    0.072711] ... fixed-purpose events:   3
Jul 24 09:52:18 node-4 kernel: [    0.072712] ... event mask:             000000070000000f
Jul 24 09:52:18 node-4 kernel: [    0.074154] x86: Booting SMP configuration:
Jul 24 09:52:18 node-4 kernel: [    0.088360] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 24 09:52:18 node-4 kernel: [    0.074156] .... node  #0, CPUs:        #1  #2  #3
Jul 24 09:52:18 node-4 kernel: [    0.116271] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 24 09:52:18 node-4 kernel: [    0.270423] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 24 09:52:18 node-4 kernel: [    0.326047] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 24 09:52:18 node-4 kernel: [    0.383116] x86: Booted up 2 nodes, 16 CPUs
Jul 24 09:52:18 node-4 kernel: [    0.383119] smpboot: Total of 16 processors activated (111762.66 BogoMIPS)
Jul 24 09:52:18 node-4 kernel: [    0.407433] devtmpfs: initialized
Jul 24 09:52:18 node-4 kernel: [    0.410554] EVM: security.selinux
Jul 24 09:52:18 node-4 kernel: [    0.410556] EVM: security.SMACK64
Jul 24 09:52:18 node-4 kernel: [    0.410557] EVM: security.ima
Jul 24 09:52:18 node-4 kernel: [    0.410558] EVM: security.capability
Jul 24 09:52:18 node-4 kernel: [    0.410607] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 24 09:52:18 node-4 kernel: [    0.411286] pinctrl core: initialized pinctrl subsystem
Jul 24 09:52:18 node-4 kernel: [    0.411347] regulator-dummy: no parameters
Jul 24 09:52:18 node-4 kernel: [    0.411380] RTC time:  9:51:40, date: 07/24/16
Jul 24 09:52:18 node-4 kernel: [    0.411415] NET: Registered protocol family 16
Jul 24 09:52:18 node-4 kernel: [    0.411499] cpuidle: using governor ladder
Jul 24 09:52:18 node-4 kernel: [    0.411500] cpuidle: using governor menu
Jul 24 09:52:18 node-4 kernel: [    0.411534] ACPI: bus type PCI registered
Jul 24 09:52:18 node-4 kernel: [    0.411536] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 24 09:52:18 node-4 kernel: [    0.411583] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 24 09:52:18 node-4 kernel: [    0.411585] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 24 09:52:18 node-4 kernel: [    0.425316] PCI: Using configuration type 1 for base access
Jul 24 09:52:18 node-4 kernel: [    0.426318] bio: create slab <bio-0> at 0
Jul 24 09:52:18 node-4 kernel: [    0.426596] ACPI: Added _OSI(Module Device)
Jul 24 09:52:18 node-4 kernel: [    0.426597] ACPI: Added _OSI(Processor Device)
Jul 24 09:52:18 node-4 kernel: [    0.426598] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 24 09:52:18 node-4 kernel: [    0.426599] ACPI: Added _OSI(Processor Aggregator Device)
Jul 24 09:52:18 node-4 kernel: [    0.439247] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 24 09:52:18 node-4 kernel: [    0.451017] ACPI: Interpreter enabled
Jul 24 09:52:18 node-4 kernel: [    0.451022] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 24 09:52:18 node-4 kernel: [    0.451026] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 24 09:52:18 node-4 kernel: [    0.451029] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 24 09:52:18 node-4 kernel: [    0.451036] ACPI: (supports S0 S4 S5)
Jul 24 09:52:18 node-4 kernel: [    0.451037] ACPI: Using IOAPIC for interrupt routing
Jul 24 09:52:18 node-4 kernel: [    0.451081] HEST: Table parsing has been initialized.
Jul 24 09:52:18 node-4 kernel: [    0.451084] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 24 09:52:18 node-4 kernel: [    0.451637] ACPI: No dock devices found.
Jul 24 09:52:18 node-4 kernel: [    0.463210] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 24 09:52:18 node-4 kernel: [    0.463215] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 09:52:18 node-4 kernel: [    0.463219] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 24 09:52:18 node-4 kernel: [    0.463245] PCI host bridge to bus 0000:ff
Jul 24 09:52:18 node-4 kernel: [    0.463247] pci_bus 0000:ff: root bus resource [bus ff]
Jul 24 09:52:18 node-4 kernel: [    0.463255] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463292] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 24 09:52:18 node-4 kernel: [    0.463323] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463357] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463386] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 24 09:52:18 node-4 kernel: [    0.463415] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 24 09:52:18 node-4 kernel: [    0.463445] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463472] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463500] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463530] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463556] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463583] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463613] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463640] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463666] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463692] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463720] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463747] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463773] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 24 09:52:18 node-4 kernel: [    0.463801] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463826] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 24 09:52:18 node-4 kernel: [    0.463852] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463877] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463907] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 24 09:52:18 node-4 kernel: [    0.463941] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.463972] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464001] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464032] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464062] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464094] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464126] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464157] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464187] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464219] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464251] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464283] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464316] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464345] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464373] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464403] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464436] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464473] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464508] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464540] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464570] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464598] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464628] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464658] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464690] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464720] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464752] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464779] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464808] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464836] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464865] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464896] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464927] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.464983] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 24 09:52:18 node-4 kernel: [    0.464985] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 09:52:18 node-4 kernel: [    0.464988] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 24 09:52:18 node-4 kernel: [    0.465006] PCI host bridge to bus 0000:7f
Jul 24 09:52:18 node-4 kernel: [    0.465007] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 24 09:52:18 node-4 kernel: [    0.465012] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465039] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 24 09:52:18 node-4 kernel: [    0.465071] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465100] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465122] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 24 09:52:18 node-4 kernel: [    0.465146] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 24 09:52:18 node-4 kernel: [    0.465171] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465197] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465218] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465241] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465263] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465285] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465309] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465333] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465357] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465383] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465404] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465427] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465450] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 24 09:52:18 node-4 kernel: [    0.465476] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465500] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 24 09:52:18 node-4 kernel: [    0.465523] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465547] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465573] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 24 09:52:18 node-4 kernel: [    0.465605] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465631] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465658] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465687] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465712] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465738] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465763] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465791] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465815] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465843] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465870] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465897] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465925] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465950] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.465974] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466001] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466026] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466052] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466080] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466108] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466134] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466158] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466184] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466210] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466238] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466265] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466295] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466321] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466343] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466369] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466394] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466426] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.466453] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.467708] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 24 09:52:18 node-4 kernel: [    0.467711] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 09:52:18 node-4 kernel: [    0.468829] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 24 09:52:18 node-4 kernel: [    0.469340] PCI host bridge to bus 0000:00
Jul 24 09:52:18 node-4 kernel: [    0.469342] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 24 09:52:18 node-4 kernel: [    0.469344] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 24 09:52:18 node-4 kernel: [    0.469345] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 24 09:52:18 node-4 kernel: [    0.469346] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 24 09:52:18 node-4 kernel: [    0.469348] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 24 09:52:18 node-4 kernel: [    0.469349] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 24 09:52:18 node-4 kernel: [    0.469350] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 24 09:52:18 node-4 kernel: [    0.469356] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 24 09:52:18 node-4 kernel: [    0.469438] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 24 09:52:18 node-4 kernel: [    0.469469] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 24 09:52:18 node-4 kernel: [    0.469510] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 24 09:52:18 node-4 kernel: [    0.469529] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 24 09:52:18 node-4 kernel: [    0.469558] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 24 09:52:18 node-4 kernel: [    0.469598] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 24 09:52:18 node-4 kernel: [    0.469617] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 24 09:52:18 node-4 kernel: [    0.469646] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 24 09:52:18 node-4 kernel: [    0.469689] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 24 09:52:18 node-4 kernel: [    0.469705] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.469775] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.469851] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.469926] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 24 09:52:18 node-4 kernel: [    0.469931] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 24 09:52:18 node-4 kernel: [    0.470015] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 24 09:52:18 node-4 kernel: [    0.470163] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 24 09:52:18 node-4 kernel: [    0.470180] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 24 09:52:18 node-4 kernel: [    0.470257] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 24 09:52:18 node-4 kernel: [    0.470315] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 24 09:52:18 node-4 kernel: [    0.470336] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 24 09:52:18 node-4 kernel: [    0.470391] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 24 09:52:18 node-4 kernel: [    0.470434] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 24 09:52:18 node-4 kernel: [    0.470461] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 24 09:52:18 node-4 kernel: [    0.470517] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 24 09:52:18 node-4 kernel: [    0.470559] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 24 09:52:18 node-4 kernel: [    0.470583] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 24 09:52:18 node-4 kernel: [    0.470601] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 24 09:52:18 node-4 kernel: [    0.470678] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 24 09:52:18 node-4 kernel: [    0.470727] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 24 09:52:18 node-4 kernel: [    0.470752] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 24 09:52:18 node-4 kernel: [    0.470998] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 24 09:52:18 node-4 kernel: [    0.471004] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 24 09:52:18 node-4 kernel: [    0.471010] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 24 09:52:18 node-4 kernel: [    0.471016] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 24 09:52:18 node-4 kernel: [    0.471023] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 24 09:52:18 node-4 kernel: [    0.471053] pci 0000:01:00.0: supports D1 D2
Jul 24 09:52:18 node-4 kernel: [    0.477081] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 24 09:52:18 node-4 kernel: [    0.477087] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 24 09:52:18 node-4 kernel: [    0.477091] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 24 09:52:18 node-4 kernel: [    0.477351] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 24 09:52:18 node-4 kernel: [    0.477411] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 24 09:52:18 node-4 kernel: [    0.485078] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 24 09:52:18 node-4 kernel: [    0.485084] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 24 09:52:18 node-4 kernel: [    0.485100] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 09:52:18 node-4 kernel: [    0.485155] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 24 09:52:18 node-4 kernel: [    0.485249] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 24 09:52:18 node-4 kernel: [    0.485327] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 24 09:52:18 node-4 kernel: [    0.485372] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 24 09:52:18 node-4 kernel: [    0.485376] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 09:52:18 node-4 kernel: [    0.485377] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 09:52:18 node-4 kernel: [    0.485430] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 24 09:52:18 node-4 kernel: [    0.485552] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 24 09:52:18 node-4 kernel: [    0.485605] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 24 09:52:18 node-4 kernel: [    0.485607] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 09:52:18 node-4 kernel: [    0.485610] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 09:52:18 node-4 kernel: [    0.485659] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 24 09:52:18 node-4 kernel: [    0.485778] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 24 09:52:18 node-4 kernel: [    0.485817] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 24 09:52:18 node-4 kernel: [    0.485937] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 24 09:52:18 node-4 kernel: [    0.485973] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 24 09:52:18 node-4 kernel: [    0.486092] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 24 09:52:18 node-4 kernel: [    0.486128] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 24 09:52:18 node-4 kernel: [    0.486269] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 24 09:52:18 node-4 kernel: [    0.486313] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 24 09:52:18 node-4 kernel: [    0.486315] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 09:52:18 node-4 kernel: [    0.486317] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 09:52:18 node-4 kernel: [    0.486378] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 24 09:52:18 node-4 kernel: [    0.486441] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 24 09:52:18 node-4 kernel: [    0.486493] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 24 09:52:18 node-4 kernel: [    0.486534] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 24 09:52:18 node-4 kernel: [    0.486616] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 24 09:52:18 node-4 kernel: [    0.486722] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 24 09:52:18 node-4 kernel: [    0.486725] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 09:52:18 node-4 kernel: [    0.486727] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 24 09:52:18 node-4 kernel: [    0.486783] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 24 09:52:18 node-4 kernel: [    0.486838] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 24 09:52:18 node-4 kernel: [    0.486887] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 24 09:52:18 node-4 kernel: [    0.487098] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 24 09:52:18 node-4 kernel: [    0.487101] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 24 09:52:18 node-4 kernel: [    0.487165] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 24 09:52:18 node-4 kernel: [    0.487242] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 24 09:52:18 node-4 kernel: [    0.487290] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 24 09:52:18 node-4 kernel: [    0.487500] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 24 09:52:18 node-4 kernel: [    0.487504] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 24 09:52:18 node-4 kernel: [    0.487563] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 24 09:52:18 node-4 kernel: [    0.487623] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 24 09:52:18 node-4 kernel: [    0.487676] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 24 09:52:18 node-4 kernel: [    0.487898] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 24 09:52:18 node-4 kernel: [    0.487901] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 24 09:52:18 node-4 kernel: [    0.488075] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 24 09:52:18 node-4 kernel: [    0.488114] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 24 09:52:18 node-4 kernel: [    0.488189] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 24 09:52:18 node-4 kernel: [    0.488208] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 24 09:52:18 node-4 kernel: [    0.488221] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 24 09:52:18 node-4 kernel: [    0.488234] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 24 09:52:18 node-4 kernel: [    0.488284] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 24 09:52:18 node-4 kernel: [    0.493085] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 24 09:52:18 node-4 kernel: [    0.493094] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 24 09:52:18 node-4 kernel: [    0.493146] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 24 09:52:18 node-4 kernel: [    0.493904] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 24 09:52:18 node-4 kernel: [    0.493907] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 09:52:18 node-4 kernel: [    0.494032] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 24 09:52:18 node-4 kernel: [    0.494139] PCI host bridge to bus 0000:80
Jul 24 09:52:18 node-4 kernel: [    0.494141] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 24 09:52:18 node-4 kernel: [    0.494142] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 24 09:52:18 node-4 kernel: [    0.494144] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 24 09:52:18 node-4 kernel: [    0.494152] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.494215] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.494286] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 24 09:52:18 node-4 kernel: [    0.494349] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 24 09:52:18 node-4 kernel: [    0.494354] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 24 09:52:18 node-4 kernel: [    0.494427] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 24 09:52:18 node-4 kernel: [    0.494727] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 24 09:52:18 node-4 kernel: [    0.494758] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 24 09:52:18 node-4 kernel: [    0.494788] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 24 09:52:18 node-4 kernel: [    0.494817] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 24 09:52:18 node-4 kernel: [    0.494846] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 09:52:18 node-4 kernel: [    0.494876] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 09:52:18 node-4 kernel: [    0.494905] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 09:52:18 node-4 kernel: [    0.494934] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 09:52:18 node-4 kernel: [    0.495019] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 24 09:52:18 node-4 kernel: [    0.495023] ACPI: \_SB_.UNC1: notify handler is installed
Jul 24 09:52:18 node-4 kernel: [    0.495025] ACPI: \_SB_.UNC0: notify handler is installed
Jul 24 09:52:18 node-4 kernel: [    0.495040] ACPI: \_SB_.PCI0: notify handler is installed
Jul 24 09:52:18 node-4 kernel: [    0.495092] ACPI: \_SB_.PCI1: notify handler is installed
Jul 24 09:52:18 node-4 kernel: [    0.495172] Found 4 acpi root devices
Jul 24 09:52:18 node-4 kernel: [    0.495281] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 24 09:52:18 node-4 kernel: [    0.495283] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 24 09:52:18 node-4 kernel: [    0.495285] vgaarb: loaded
Jul 24 09:52:18 node-4 kernel: [    0.495286] vgaarb: bridge control possible 0000:0c:00.0
Jul 24 09:52:18 node-4 kernel: [    0.495409] SCSI subsystem initialized
Jul 24 09:52:18 node-4 kernel: [    0.495473] libata version 3.00 loaded.
Jul 24 09:52:18 node-4 kernel: [    0.495488] ACPI: bus type USB registered
Jul 24 09:52:18 node-4 kernel: [    0.495498] usbcore: registered new interface driver usbfs
Jul 24 09:52:18 node-4 kernel: [    0.495503] usbcore: registered new interface driver hub
Jul 24 09:52:18 node-4 kernel: [    0.495527] usbcore: registered new device driver usb
Jul 24 09:52:18 node-4 kernel: [    0.495695] PCI: Using ACPI for IRQ routing
Jul 24 09:52:18 node-4 kernel: [    0.499295] PCI: pci_cache_line_size set to 64 bytes
Jul 24 09:52:18 node-4 kernel: [    0.499496] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 24 09:52:18 node-4 kernel: [    0.499497] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 24 09:52:18 node-4 kernel: [    0.499498] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 24 09:52:18 node-4 kernel: [    0.499564] NetLabel: Initializing
Jul 24 09:52:18 node-4 kernel: [    0.499565] NetLabel:  domain hash size = 128
Jul 24 09:52:18 node-4 kernel: [    0.499566] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 24 09:52:18 node-4 kernel: [    0.499576] NetLabel:  unlabeled traffic allowed by default
Jul 24 09:52:18 node-4 kernel: [    0.499631] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 24 09:52:18 node-4 kernel: [    0.499636] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 24 09:52:18 node-4 kernel: [    0.501695] Switched to clocksource hpet
Jul 24 09:52:18 node-4 kernel: [    0.505678] AppArmor: AppArmor Filesystem Enabled
Jul 24 09:52:18 node-4 kernel: [    0.505697] pnp: PnP ACPI init
Jul 24 09:52:18 node-4 kernel: [    0.505703] ACPI: bus type PNP registered
Jul 24 09:52:18 node-4 kernel: [    0.505810] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 24 09:52:18 node-4 kernel: [    0.505818] pnp 00:01: [dma 4]
Jul 24 09:52:18 node-4 kernel: [    0.505829] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 24 09:52:18 node-4 kernel: [    0.505858] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 24 09:52:18 node-4 kernel: [    0.505877] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 24 09:52:18 node-4 kernel: [    0.505894] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 24 09:52:18 node-4 kernel: [    0.505927] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 24 09:52:18 node-4 kernel: [    0.505978] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 24 09:52:18 node-4 kernel: [    0.505980] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 24 09:52:18 node-4 kernel: [    0.505982] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 24 09:52:18 node-4 kernel: [    0.505983] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 24 09:52:18 node-4 kernel: [    0.505985] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 24 09:52:18 node-4 kernel: [    0.505989] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 24 09:52:18 node-4 kernel: [    0.505991] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 24 09:52:18 node-4 kernel: [    0.505993] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 24 09:52:18 node-4 kernel: [    0.505994] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 24 09:52:18 node-4 kernel: [    0.505996] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 24 09:52:18 node-4 kernel: [    0.505997] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 24 09:52:18 node-4 kernel: [    0.505999] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 24 09:52:18 node-4 kernel: [    0.506000] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 24 09:52:18 node-4 kernel: [    0.506003] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 24 09:52:18 node-4 kernel: [    0.506087] pnp 00:07: [dma 0 disabled]
Jul 24 09:52:18 node-4 kernel: [    0.506115] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 24 09:52:18 node-4 kernel: [    0.506189] pnp 00:08: [dma 0 disabled]
Jul 24 09:52:18 node-4 kernel: [    0.506220] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 24 09:52:18 node-4 kernel: [    0.506270] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 24 09:52:18 node-4 kernel: [    0.506615] pnp: PnP ACPI: found 10 devices
Jul 24 09:52:18 node-4 kernel: [    0.506616] ACPI: bus type PNP unregistered
Jul 24 09:52:18 node-4 kernel: [    0.512950] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 24 09:52:18 node-4 kernel: [    0.512953] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 24 09:52:18 node-4 kernel: [    0.512955] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 24 09:52:18 node-4 kernel: [    0.512960] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 24 09:52:18 node-4 kernel: [    0.512961] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 09:52:18 node-4 kernel: [    0.512976] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 24 09:52:18 node-4 kernel: [    0.513005] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 24 09:52:18 node-4 kernel: [    0.513020] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 24 09:52:18 node-4 kernel: [    0.513049] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 24 09:52:18 node-4 kernel: [    0.513063] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 24 09:52:18 node-4 kernel: [    0.513092] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 24 09:52:18 node-4 kernel: [    0.513107] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 24 09:52:18 node-4 kernel: [    0.513136] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 24 09:52:18 node-4 kernel: [    0.513137] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 09:52:18 node-4 kernel: [    0.513152] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 09:52:18 node-4 kernel: [    0.513203] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 24 09:52:18 node-4 kernel: [    0.513205] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 09:52:18 node-4 kernel: [    0.513220] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 09:52:18 node-4 kernel: [    0.513252] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 24 09:52:18 node-4 kernel: [    0.513254] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 09:52:18 node-4 kernel: [    0.513257] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 09:52:18 node-4 kernel: [    0.513261] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 24 09:52:18 node-4 kernel: [    0.513262] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 24 09:52:18 node-4 kernel: [    0.513265] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 09:52:18 node-4 kernel: [    0.513268] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 24 09:52:18 node-4 kernel: [    0.513273] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 24 09:52:18 node-4 kernel: [    0.513281] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 24 09:52:18 node-4 kernel: [    0.513285] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 24 09:52:18 node-4 kernel: [    0.513291] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 24 09:52:18 node-4 kernel: [    0.513292] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 24 09:52:18 node-4 kernel: [    0.513293] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 24 09:52:18 node-4 kernel: [    0.513294] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 24 09:52:18 node-4 kernel: [    0.513294] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 24 09:52:18 node-4 kernel: [    0.513295] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 24 09:52:18 node-4 kernel: [    0.513296] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 24 09:52:18 node-4 kernel: [    0.513297] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 24 09:52:18 node-4 kernel: [    0.513298] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 24 09:52:18 node-4 kernel: [    0.513299] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 24 09:52:18 node-4 kernel: [    0.513300] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 24 09:52:18 node-4 kernel: [    0.513301] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 24 09:52:18 node-4 kernel: [    0.513301] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 24 09:52:18 node-4 kernel: [    0.513302] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 24 09:52:18 node-4 kernel: [    0.513303] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 24 09:52:18 node-4 kernel: [    0.513304] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 24 09:52:18 node-4 kernel: [    0.513305] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 24 09:52:18 node-4 kernel: [    0.513306] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 24 09:52:18 node-4 kernel: [    0.513307] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 24 09:52:18 node-4 kernel: [    0.513308] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 24 09:52:18 node-4 kernel: [    0.513309] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 24 09:52:18 node-4 kernel: [    0.513310] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 24 09:52:18 node-4 kernel: [    0.513312] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 24 09:52:18 node-4 kernel: [    0.513313] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 24 09:52:18 node-4 kernel: [    0.513351] NET: Registered protocol family 2
Jul 24 09:52:18 node-4 kernel: [    0.513605] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 24 09:52:18 node-4 kernel: [    0.513936] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 24 09:52:18 node-4 kernel: [    0.514079] TCP: Hash tables configured (established 262144 bind 65536)
Jul 24 09:52:18 node-4 kernel: [    0.514121] TCP: reno registered
Jul 24 09:52:18 node-4 kernel: [    0.514149] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 24 09:52:18 node-4 kernel: [    0.514244] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 24 09:52:18 node-4 kernel: [    0.514391] NET: Registered protocol family 1
Jul 24 09:52:18 node-4 kernel: [    0.553799] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 24 09:52:18 node-4 kernel: [    0.553806] PCI: CLS 64 bytes, default 64
Jul 24 09:52:18 node-4 kernel: [    0.553847] Trying to unpack rootfs image as initramfs...
Jul 24 09:52:18 node-4 kernel: [    0.772735] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 24 09:52:18 node-4 kernel: [    0.772781] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 24 09:52:18 node-4 kernel: [    0.772783] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 24 09:52:18 node-4 kernel: [    0.773194] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 09:52:18 node-4 kernel: [    0.773200] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 09:52:18 node-4 kernel: [    0.773204] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 09:52:18 node-4 kernel: [    0.773210] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 09:52:18 node-4 kernel: [    0.773222] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 09:52:18 node-4 kernel: [    0.773239] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 09:52:18 node-4 kernel: [    0.773254] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 09:52:18 node-4 kernel: [    0.773269] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 09:52:18 node-4 kernel: [    0.773281] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 09:52:18 node-4 kernel: [    0.773291] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 09:52:18 node-4 kernel: [    0.773297] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 09:52:18 node-4 kernel: [    0.773303] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 09:52:18 node-4 kernel: [    0.773312] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 09:52:18 node-4 kernel: [    0.773326] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 09:52:18 node-4 kernel: [    0.773338] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 09:52:18 node-4 kernel: [    0.773351] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 09:52:18 node-4 kernel: [    0.773489] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 24 09:52:18 node-4 kernel: [    0.773496] Scanning for low memory corruption every 60 seconds
Jul 24 09:52:18 node-4 kernel: [    0.773893] Initialise system trusted keyring
Jul 24 09:52:18 node-4 kernel: [    0.773948] audit: initializing netlink socket (disabled)
Jul 24 09:52:18 node-4 kernel: [    0.773964] type=2000 audit(1469353900.728:1): initialized
Jul 24 09:52:18 node-4 kernel: [    0.791855] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 24 09:52:18 node-4 kernel: [    0.793391] zbud: loaded
Jul 24 09:52:18 node-4 kernel: [    0.793524] VFS: Disk quotas dquot_6.5.2
Jul 24 09:52:18 node-4 kernel: [    0.793560] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 24 09:52:18 node-4 kernel: [    0.793951] fuse init (API version 7.22)
Jul 24 09:52:18 node-4 kernel: [    0.794015] msgmni has been set to 32768
Jul 24 09:52:18 node-4 kernel: [    0.794065] Key type big_key registered
Jul 24 09:52:18 node-4 kernel: [    0.794564] Key type asymmetric registered
Jul 24 09:52:18 node-4 kernel: [    0.794566] Asymmetric key parser 'x509' registered
Jul 24 09:52:18 node-4 kernel: [    0.794588] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 24 09:52:18 node-4 kernel: [    0.794658] io scheduler noop registered
Jul 24 09:52:18 node-4 kernel: [    0.794659] io scheduler deadline registered (default)
Jul 24 09:52:18 node-4 kernel: [    0.794678] io scheduler cfq registered
Jul 24 09:52:18 node-4 kernel: [    0.795078] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    0.795198] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    0.795311] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    0.795416] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    0.795526] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    0.795632] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    0.796040] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 24 09:52:18 node-4 kernel: [    0.796079] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 24 09:52:18 node-4 kernel: [    0.796110] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 24 09:52:18 node-4 kernel: [    0.796119] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796122] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796124] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 24 09:52:18 node-4 kernel: [    0.796129] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796131] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796132] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796134] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796135] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796137] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796138] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796140] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796141] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796143] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796144] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796145] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796148] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 24 09:52:18 node-4 kernel: [    0.796153] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796155] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 24 09:52:18 node-4 kernel: [    0.796167] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796171] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 24 09:52:18 node-4 kernel: [    0.796181] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796182] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 24 09:52:18 node-4 kernel: [    0.796185] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 24 09:52:18 node-4 kernel: [    0.796222] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 24 09:52:18 node-4 kernel: [    0.796227] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 24 09:52:18 node-4 kernel: [    0.796232] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 24 09:52:18 node-4 kernel: [    0.796241] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 24 09:52:18 node-4 kernel: [    0.796280] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 24 09:52:18 node-4 kernel: [    0.796282] vesafb: scrolling: redraw
Jul 24 09:52:18 node-4 kernel: [    0.796283] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 24 09:52:18 node-4 kernel: [    0.816858] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 24 09:52:18 node-4 kernel: [    0.825433] Console: switching to colour frame buffer device 80x30
Jul 24 09:52:18 node-4 kernel: [    0.834167] fb0: VESA VGA frame buffer device
Jul 24 09:52:18 node-4 kernel: [    0.834363] intel_idle: MWAIT substates: 0x2120
Jul 24 09:52:18 node-4 kernel: [    0.834364] intel_idle: v0.4 model 0x3F
Jul 24 09:52:18 node-4 kernel: [    0.834365] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 24 09:52:18 node-4 kernel: [    0.834604] ipmi message handler version 39.2
Jul 24 09:52:18 node-4 kernel: [    0.834879] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 24 09:52:18 node-4 kernel: [    0.835314] ACPI: AC Adapter [P111] (on-line)
Jul 24 09:52:18 node-4 kernel: [    0.840535] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 24 09:52:18 node-4 kernel: [    0.851575] ACPI: Power Button [PWRB]
Jul 24 09:52:18 node-4 kernel: [    0.857317] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 24 09:52:18 node-4 kernel: [    0.868931] ACPI: Power Button [PWRF]
Jul 24 09:52:18 node-4 kernel: [    0.895251] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 24 09:52:18 node-4 kernel: [    0.906864] pstore: Registered erst as persistent store backend
Jul 24 09:52:18 node-4 kernel: [    0.913058] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 24 09:52:18 node-4 kernel: [    0.924972] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 24 09:52:18 node-4 kernel: [    0.951712] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 24 09:52:18 node-4 kernel: [    0.984954] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 24 09:52:18 node-4 kernel: [    0.998969] Linux agpgart interface v0.103
Jul 24 09:52:18 node-4 kernel: [    1.006585] brd: module loaded
Jul 24 09:52:18 node-4 kernel: [    1.013602] loop: module loaded
Jul 24 09:52:18 node-4 kernel: [    1.020303] libphy: Fixed MDIO Bus: probed
Jul 24 09:52:18 node-4 kernel: [    1.026746] tun: Universal TUN/TAP device driver, 1.6
Jul 24 09:52:18 node-4 kernel: [    1.033221] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 24 09:52:18 node-4 kernel: [    1.039752] PPP generic driver version 2.4.2
Jul 24 09:52:18 node-4 kernel: [    1.046136] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 24 09:52:18 node-4 kernel: [    1.052574] ehci-pci: EHCI PCI platform driver
Jul 24 09:52:18 node-4 kernel: [    1.059084] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 24 09:52:18 node-4 kernel: [    1.065488] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 24 09:52:18 node-4 kernel: [    1.078028] ehci-pci 0000:00:1a.0: debug port 2
Jul 24 09:52:18 node-4 kernel: [    1.088236] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 24 09:52:18 node-4 kernel: [    1.088254] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 24 09:52:18 node-4 kernel: [    1.105184] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 24 09:52:18 node-4 kernel: [    1.111246] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 24 09:52:18 node-4 kernel: [    1.117406] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 24 09:52:18 node-4 kernel: [    1.129291] usb usb1: Product: EHCI Host Controller
Jul 24 09:52:18 node-4 kernel: [    1.135301] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 24 09:52:18 node-4 kernel: [    1.141372] usb usb1: SerialNumber: 0000:00:1a.0
Jul 24 09:52:18 node-4 kernel: [    1.147303] hub 1-0:1.0: USB hub found
Jul 24 09:52:18 node-4 kernel: [    1.153053] hub 1-0:1.0: 2 ports detected
Jul 24 09:52:18 node-4 kernel: [    1.158859] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 24 09:52:18 node-4 kernel: [    1.164513] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 24 09:52:18 node-4 kernel: [    1.175374] ehci-pci 0000:00:1d.0: debug port 2
Jul 24 09:52:18 node-4 kernel: [    1.184645] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 24 09:52:18 node-4 kernel: [    1.184651] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 24 09:52:18 node-4 kernel: [    1.201102] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 24 09:52:18 node-4 kernel: [    1.206289] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 24 09:52:18 node-4 kernel: [    1.211578] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 24 09:52:18 node-4 kernel: [    1.222112] usb usb2: Product: EHCI Host Controller
Jul 24 09:52:18 node-4 kernel: [    1.227565] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 24 09:52:18 node-4 kernel: [    1.233118] usb usb2: SerialNumber: 0000:00:1d.0
Jul 24 09:52:18 node-4 kernel: [    1.238621] hub 2-0:1.0: USB hub found
Jul 24 09:52:18 node-4 kernel: [    1.243960] hub 2-0:1.0: 2 ports detected
Jul 24 09:52:18 node-4 kernel: [    1.249248] ehci-platform: EHCI generic platform driver
Jul 24 09:52:18 node-4 kernel: [    1.254456] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 24 09:52:18 node-4 kernel: [    1.259763] ohci-pci: OHCI PCI platform driver
Jul 24 09:52:18 node-4 kernel: [    1.265052] ohci-platform: OHCI generic platform driver
Jul 24 09:52:18 node-4 kernel: [    1.270236] uhci_hcd: USB Universal Host Controller Interface driver
Jul 24 09:52:18 node-4 kernel: [    1.275570] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 24 09:52:18 node-4 kernel: [    1.468882] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 24 09:52:18 node-4 kernel: [    1.768687] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 24 09:52:18 node-4 kernel: [    1.784897] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 24 09:52:18 node-4 kernel: [    1.790498] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 24 09:52:18 node-4 kernel: [    1.796164] hub 1-1:1.0: USB hub found
Jul 24 09:52:18 node-4 kernel: [    1.801758] hub 1-1:1.0: 6 ports detected
Jul 24 09:52:18 node-4 kernel: [    1.916522] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 24 09:52:18 node-4 kernel: [    2.314462] i8042: No controller found
Jul 24 09:52:18 node-4 kernel: [    2.319994] mousedev: PS/2 mouse device common for all mice
Jul 24 09:52:18 node-4 kernel: [    2.325707] rtc_cmos 00:02: RTC can wake from S4
Jul 24 09:52:18 node-4 kernel: [    2.329006] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 24 09:52:18 node-4 kernel: [    2.329007] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 24 09:52:18 node-4 kernel: [    2.329644] hub 2-1:1.0: USB hub found
Jul 24 09:52:18 node-4 kernel: [    2.329876] hub 2-1:1.0: 8 ports detected
Jul 24 09:52:18 node-4 kernel: [    2.353988] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 24 09:52:18 node-4 kernel: [    2.359740] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 24 09:52:18 node-4 kernel: [    2.371045] device-mapper: uevent: version 1.0.3
Jul 24 09:52:18 node-4 kernel: [    2.376744] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 24 09:52:18 node-4 kernel: [    2.388086] ledtrig-cpu: registered to indicate activity on CPUs
Jul 24 09:52:18 node-4 kernel: [    2.394049] TCP: cubic registered
Jul 24 09:52:18 node-4 kernel: [    2.399895] NET: Registered protocol family 10
Jul 24 09:52:18 node-4 kernel: [    2.405959] NET: Registered protocol family 17
Jul 24 09:52:18 node-4 kernel: [    2.411717] Key type dns_resolver registered
Jul 24 09:52:18 node-4 kernel: [    2.417748] Loading compiled-in X.509 certificates
Jul 24 09:52:18 node-4 kernel: [    2.423934] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 24 09:52:18 node-4 kernel: [    2.435539] registered taskstats version 1
Jul 24 09:52:18 node-4 kernel: [    2.443563] Key type trusted registered
Jul 24 09:52:18 node-4 kernel: [    2.451158] Key type encrypted registered
Jul 24 09:52:18 node-4 kernel: [    2.456647] AppArmor: AppArmor sha1 policy hashing enabled
Jul 24 09:52:18 node-4 kernel: [    2.462157] IMA: No TPM chip found, activating TPM-bypass!
Jul 24 09:52:18 node-4 kernel: [    2.468246] regulator-dummy: disabling
Jul 24 09:52:18 node-4 kernel: [    2.473746]   Magic number: 8:103:880
Jul 24 09:52:18 node-4 kernel: [    2.479469] rtc_cmos 00:02: setting system clock to 2016-07-24 09:51:42 UTC (1469353902)
Jul 24 09:52:18 node-4 kernel: [    2.491970] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 24 09:52:18 node-4 kernel: [    2.497636] EDD information not available.
Jul 24 09:52:18 node-4 kernel: [    2.503259] PM: Hibernation image not present or could not be loaded.
Jul 24 09:52:18 node-4 kernel: [    2.504129] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 24 09:52:18 node-4 kernel: [    2.515460] Write protecting the kernel read-only data: 12288k
Jul 24 09:52:18 node-4 kernel: [    2.521742] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 24 09:52:18 node-4 kernel: [    2.534686] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 24 09:52:18 node-4 kernel: [    2.566783] device-mapper: multipath: version 1.6.0 loaded
Jul 24 09:52:18 node-4 kernel: [    2.574878] systemd-udevd[216]: starting version 204
Jul 24 09:52:18 node-4 kernel: [    2.598817] md: linear personality registered for level -1
Jul 24 09:52:18 node-4 kernel: [    2.604059] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 24 09:52:18 node-4 kernel: [    2.619002] md: multipath personality registered for level -4
Jul 24 09:52:18 node-4 kernel: [    2.627286] md: raid0 personality registered for level 0
Jul 24 09:52:18 node-4 kernel: [    2.635764] md: raid1 personality registered for level 1
Jul 24 09:52:18 node-4 kernel: [    2.642527] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 24 09:52:18 node-4 kernel: [    2.648955] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 24 09:52:18 node-4 kernel: [    2.655277] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 24 09:52:18 node-4 kernel: [    2.655713] megasas: FW now in Ready state
Jul 24 09:52:18 node-4 kernel: [    2.655776] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.655813] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.655909] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.655946] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.655986] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.656022] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.656064] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.656097] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.656134] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.656172] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.656210] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.656253] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.656291] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.656329] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.656364] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.656399] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.656569] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 24 09:52:18 node-4 kernel: [    2.689104] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 24 09:52:18 node-4 kernel: [    2.702482] 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 24 09:52:18 node-4 kernel: [    2.716193] raid6: sse2x1    6096 MB/s
Jul 24 09:52:18 node-4 kernel: [    2.723395] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 09:52:18 node-4 kernel: [    2.730459] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.730470] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.730475] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.730481] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.730523] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 09:52:18 node-4 kernel: [    2.754277] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 24 09:52:18 node-4 kernel: [    2.767757] 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 24 09:52:18 node-4 kernel: [    2.781473] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 09:52:18 node-4 kernel: [    2.784097] raid6: sse2x2    3095 MB/s
Jul 24 09:52:18 node-4 kernel: [    2.851712] raid6: sse2x4    9163 MB/s
Jul 24 09:52:18 node-4 kernel: [    2.923651] raid6: avx2x1   14949 MB/s
Jul 24 09:52:18 node-4 kernel: [    2.995591] raid6: avx2x2   18855 MB/s
Jul 24 09:52:18 node-4 kernel: [    3.067537] raid6: avx2x4   21333 MB/s
Jul 24 09:52:18 node-4 kernel: [    3.073589] raid6: using algorithm avx2x4 (21333 MB/s)
Jul 24 09:52:18 node-4 kernel: [    3.079608] raid6: using avx2x2 recovery algorithm
Jul 24 09:52:18 node-4 kernel: [    3.085469] megasas:IOC Init cmd success
Jul 24 09:52:18 node-4 kernel: [    3.085472] Switched to clocksource tsc
Jul 24 09:52:18 node-4 kernel: [    3.097034] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    3.097039] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    3.097043] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    3.097047] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    3.097102] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 09:52:18 node-4 kernel: [    3.108995] xor: automatically using best checksumming function:
Jul 24 09:52:18 node-4 kernel: [    3.112551] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 24 09:52:18 node-4 kernel: [    3.112552] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 24 09:52:18 node-4 kernel: [    3.112560] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 24 09:52:18 node-4 kernel: [    3.112568] usb 2-1.4: Manufacturer: Avocent
Jul 24 09:52:18 node-4 kernel: [    3.112569] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 24 09:52:18 node-4 kernel: [    3.125707] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 24 09:52:18 node-4 kernel: [    3.125708] 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 24 09:52:18 node-4 kernel: [    3.125709] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 09:52:18 node-4 kernel: [    3.126133] megasas: INIT adapter done
Jul 24 09:52:18 node-4 kernel: [    3.126445] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    3.126597] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    3.126714] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    3.126880] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    3.127370] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 09:52:18 node-4 kernel: [    3.144063] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 24 09:52:18 node-4 kernel: [    3.144092] 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 24 09:52:18 node-4 kernel: [    3.144093] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 09:52:18 node-4 kernel: [    3.144332] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    3.144400] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    3.144487] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    3.144553] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 24 09:52:18 node-4 kernel: [    3.144967] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 09:52:18 node-4 kernel: [    3.195891] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 24 09:52:18 node-4 kernel: [    3.197739] scsi0 : LSI SAS based MegaRAID driver
Jul 24 09:52:18 node-4 kernel: [    3.205604] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 24 09:52:18 node-4 kernel: [    3.265287] hidraw: raw HID events driver (C) Jiri Kosina
Jul 24 09:52:18 node-4 kernel: [    3.268824] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 24 09:52:18 node-4 kernel: [    3.273211] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 24 09:52:18 node-4 kernel: [    3.273287] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 24 09:52:18 node-4 kernel: [    3.273597] sd 0:2:0:0: [sda] Write Protect is off
Jul 24 09:52:18 node-4 kernel: [    3.273598] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 24 09:52:18 node-4 kernel: [    3.273666] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 24 09:52:18 node-4 kernel: [    3.300655]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 24 09:52:18 node-4 kernel: [    3.302150] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 24 09:52:18 node-4 kernel: [    3.303338]    avx       : 35711.000 MB/sec
Jul 24 09:52:18 node-4 kernel: [    3.346487] async_tx: api initialized (async)
Jul 24 09:52:18 node-4 kernel: [    3.354862] usbcore: registered new interface driver usbhid
Jul 24 09:52:18 node-4 kernel: [    3.361374] usbhid: USB HID core driver
Jul 24 09:52:18 node-4 kernel: [    3.368658] 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 24 09:52:18 node-4 kernel: [    3.381788] 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 24 09:52:18 node-4 kernel: [    3.381790] md: raid6 personality registered for level 6
Jul 24 09:52:18 node-4 kernel: [    3.381790] md: raid5 personality registered for level 5
Jul 24 09:52:18 node-4 kernel: [    3.381790] md: raid4 personality registered for level 4
Jul 24 09:52:18 node-4 kernel: [    3.414022] 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 24 09:52:18 node-4 kernel: [    3.426489] 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 24 09:52:18 node-4 kernel: [    3.439355] 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 24 09:52:18 node-4 kernel: [    3.452491] md: raid10 personality registered for level 10
Jul 24 09:52:18 node-4 kernel: [    3.452981] 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 24 09:52:18 node-4 kernel: [    3.481196] random: lvm urandom read with 31 bits of entropy available
Jul 24 09:52:18 node-4 kernel: [    3.534213] multipathd (369): /proc/369/oom_adj is deprecated, please use /proc/369/oom_score_adj instead.
Jul 24 09:52:18 node-4 kernel: [    3.651201] bio: create slab <bio-1> at 1
Jul 24 09:52:18 node-4 kernel: [    4.535043] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 09:52:18 node-4 kernel: [    5.086303] init: plymouth-upstart-bridge main process (574) terminated with status 1
Jul 24 09:52:18 node-4 kernel: [    5.100152] init: plymouth-upstart-bridge main process ended, respawning
Jul 24 09:52:18 node-4 kernel: [    5.117895] random: nonblocking pool is initialized
Jul 24 09:52:18 node-4 kernel: [    5.245408] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 24 09:52:18 node-4 kernel: [    5.276954] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 24 09:52:18 node-4 kernel: [    5.385323] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 24 09:52:18 node-4 kernel: [    5.415245] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 24 09:52:18 node-4 kernel: [    5.479082] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 09:52:18 node-4 kernel: [    5.707645] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 24 09:52:18 node-4 kernel: [    5.739289] XFS (dm-1): Mounting Filesystem
Jul 24 09:52:18 node-4 kernel: [    6.001274] XFS (dm-1): Ending clean mount
Jul 24 09:52:18 node-4 kernel: [    6.065697] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 09:52:18 node-4 kernel: [    6.096694] XFS (dm-2): Mounting Filesystem
Jul 24 09:52:18 node-4 kernel: [    6.266289] XFS (dm-2): Ending clean mount
Jul 24 09:52:18 node-4 kernel: [    6.404366] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 09:52:18 node-4 kernel: [    8.056371] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 24 09:52:18 node-4 kernel: [    8.070777] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 24 09:52:18 node-4 kernel: [    8.196481] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 24 09:52:18 node-4 kernel: [    8.196487] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 24 09:52:18 node-4 kernel: [    8.196492] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 24 09:52:18 node-4 kernel: [    8.196497] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 24 09:52:18 node-4 kernel: [    8.239692] systemd-udevd[803]: starting version 204
Jul 24 09:52:18 node-4 kernel: [    8.435951] IPMI System Interface driver.
Jul 24 09:52:18 node-4 kernel: [    8.436030] ipmi_si: probing via ACPI
Jul 24 09:52:18 node-4 kernel: [    8.436042] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 24 09:52:18 node-4 kernel: [    8.436043] ipmi_si: Adding ACPI-specified kcs state machine
Jul 24 09:52:18 node-4 kernel: [    8.436058] ipmi_si: probing via SMBIOS
Jul 24 09:52:18 node-4 kernel: [    8.436059] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 24 09:52:18 node-4 kernel: [    8.436060] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 24 09:52:18 node-4 kernel: [    8.436062] ipmi_si: probing via SPMI
Jul 24 09:52:18 node-4 kernel: [    8.436062] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 24 09:52:18 node-4 kernel: [    8.436063] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 24 09:52:18 node-4 kernel: [    8.436064] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 24 09:52:18 node-4 kernel: [    8.441812] power_meter ACPI000D:00: Found ACPI power meter.
Jul 24 09:52:18 node-4 kernel: [    8.441820] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 24 09:52:18 node-4 kernel: [    8.480283] wmi: Mapper loaded
Jul 24 09:52:18 node-4 kernel: [    8.511395] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 24 09:52:18 node-4 kernel: [    8.511400] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 24 09:52:18 node-4 kernel: [    8.511403] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 24 09:52:18 node-4 kernel: [    8.511404] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 24 09:52:18 node-4 kernel: [    8.511417] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 24 09:52:18 node-4 kernel: [    8.517864] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 24 09:52:18 node-4 kernel: [    8.584812] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 24 09:52:18 node-4 kernel: [    8.584817] ipmi_si 00:09: IPMI kcs interface initialized
Jul 24 09:52:18 node-4 kernel: [    8.591331] systemd-udevd[831]: renamed network interface eth1 to enp7s0
Jul 24 09:52:18 node-4 kernel: [    8.615184] systemd-udevd[822]: renamed network interface eth2 to enp8s0
Jul 24 09:52:18 node-4 kernel: [    8.648376] systemd-udevd[820]: renamed network interface eth0 to enp6s0
Jul 24 09:52:18 node-4 kernel: [    8.671154] systemd-udevd[840]: renamed network interface eth3 to enp9s0
Jul 24 09:52:18 node-4 kernel: [    8.927784] type=1400 audit(1469353908.951:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1096 comm="apparmor_parser"
Jul 24 09:52:18 node-4 kernel: [    8.928018] type=1400 audit(1469353908.951:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1096 comm="apparmor_parser"
Jul 24 09:52:18 node-4 kernel: [    8.928226] type=1400 audit(1469353908.951:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1096 comm="apparmor_parser"
Jul 24 09:52:18 node-4 kernel: [    8.933565] type=1400 audit(1469353908.955:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1092 comm="apparmor_parser"
Jul 24 09:52:18 node-4 kernel: [    8.933827] type=1400 audit(1469353908.955:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1092 comm="apparmor_parser"
Jul 24 09:52:18 node-4 kernel: [    8.933869] type=1400 audit(1469353908.955:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1094 comm="apparmor_parser"
Jul 24 09:52:18 node-4 kernel: [    8.933958] type=1400 audit(1469353908.955:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1092 comm="apparmor_parser"
Jul 24 09:52:18 node-4 kernel: [    8.934016] type=1400 audit(1469353908.955:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1094 comm="apparmor_parser"
Jul 24 09:52:18 node-4 kernel: [    8.934137] type=1400 audit(1469353908.955:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1094 comm="apparmor_parser"
Jul 24 09:52:18 node-4 kernel: [    8.947453] type=1400 audit(1469353908.971:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1093 comm="apparmor_parser"
Jul 24 09:52:18 node-4 kernel: [    9.400461] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 24 09:52:18 node-4 kernel: [    9.401322] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 24 09:52:18 node-4 kernel: [    9.579255] enic 0000:06:00.0 enp6s0: Link UP
Jul 24 09:52:18 node-4 kernel: [    9.581370] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 24 09:52:18 node-4 kernel: [    9.581378] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 24 09:52:18 node-4 kernel: [   20.087295] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 24 09:52:19 node-4 failsafe: Failsafe of 120 seconds reached.
Jul 24 09:52:19 node-4 kernel: [   38.921027] init: failsafe main process (8433) killed by TERM signal
Jul 24 09:52:19 node-4 dbus[8497]: [system] AppArmor D-Bus mediation is enabled
Jul 24 09:52:19 node-4 kernel: [   39.172831] audit_printk_skb: 30 callbacks suppressed
Jul 24 09:52:19 node-4 kernel: [   39.172834] type=1400 audit(1469353939.426:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8549 comm="apparmor_parser"
Jul 24 09:52:19 node-4 kernel: [   39.173096] type=1400 audit(1469353939.426:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8548 comm="apparmor_parser"
Jul 24 09:52:19 node-4 kernel: [   39.173100] type=1400 audit(1469353939.426:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8548 comm="apparmor_parser"
Jul 24 09:52:19 node-4 kernel: [   39.173102] type=1400 audit(1469353939.426:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8548 comm="apparmor_parser"
Jul 24 09:52:19 node-4 kernel: [   39.173325] type=1400 audit(1469353939.426:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8548 comm="apparmor_parser"
Jul 24 09:52:19 node-4 kernel: [   39.173326] type=1400 audit(1469353939.426:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8548 comm="apparmor_parser"
Jul 24 09:52:19 node-4 kernel: [   39.173450] type=1400 audit(1469353939.426:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8548 comm="apparmor_parser"
Jul 24 09:52:19 node-4 kernel: [   39.295763] type=1400 audit(1469353939.546:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8551 comm="apparmor_parser"
Jul 24 09:52:19 node-4 anacron[8626]: Anacron 2.3 started on 2016-07-24
Jul 24 09:52:19 node-4 anacron[8626]: Will run job `cron.daily' in 5 min.
Jul 24 09:52:19 node-4 anacron[8626]: Will run job `cron.weekly' in 10 min.
Jul 24 09:52:19 node-4 anacron[8626]: Will run job `cron.monthly' in 15 min.
Jul 24 09:52:19 node-4 anacron[8626]: Jobs will be executed sequentially
Jul 24 09:52:19 node-4 cron[8591]: (CRON) INFO (pidfile fd = 3)
Jul 24 09:52:19 node-4 cron[8633]: (CRON) STARTUP (fork ok)
Jul 24 09:52:19 node-4 cron[8633]: (CRON) INFO (Running @reboot jobs)
Jul 24 09:52:19 node-4 multipathd: path checkers start up
Jul 24 09:52:20 node-4 postfix/master[8770]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 24 09:52:23 node-4 puppet-agent[8954]: Reopening log files
Jul 24 09:52:24 node-4 puppet-agent[8954]: Could not request certificate: Connection refused - connect(2)
Jul 24 09:52:35 node-4 puppet-user[9162]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 24 09:52:35 node-4 puppet-user[9162]: Compiled catalog for node-4.domain.tld in environment production in 0.05 seconds
Jul 24 09:52:35 node-4 puppet-user[9162]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 24 09:52:35 node-4 puppet-user[9162]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 24 09:52:35 node-4 puppet-user[9162]: Finished catalog run in 0.44 seconds
Jul 24 09:52:37 node-4 multipathd: uevent trigger error
Jul 24 09:52:37 node-4 puppet-user[9582]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 24 09:52:37 node-4 puppet-user[9582]: Compiled catalog for node-4.domain.tld in environment production in 0.11 seconds
Jul 24 09:52:37 node-4 puppet-user[9582]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 24 09:52:37 node-4 puppet-user[9582]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 24 09:52:37 node-4 puppet-user[9582]: (/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 24 09:52:37 node-4 puppet-user[9582]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 24 09:52:37 node-4 puppet-user[9582]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 24 09:52:37 node-4 puppet-user[9582]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 24 09:52:37 node-4 puppet-user[9582]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 24 09:52:37 node-4 puppet-user[9582]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 24 09:52:37 node-4 puppet-user[9582]: Finished catalog run in 0.09 seconds
Jul 24 09:52:39 node-4 puppet-user[10232]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 24 09:52:39 node-4 puppet-user[10232]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Jul 24 09:52:39 node-4 puppet-user[10232]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 24 09:52:39 node-4 puppet-user[10232]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 24 09:52:39 node-4 puppet-user[10232]: Finished catalog run in 0.05 seconds
Jul 24 09:52:40 node-4 puppet-user[10687]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 24 09:52:40 node-4 puppet-user[10687]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 24 09:52:40 node-4 puppet-user[10687]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 24 09:52:41 node-4 puppet-user[10687]: Finished catalog run in 0.03 seconds
Jul 24 09:52:42 node-4 puppet-user[11136]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 24 09:52:42 node-4 puppet-user[11136]: Compiled catalog for node-4.domain.tld in environment production in 0.42 seconds
Jul 24 09:52:42 node-4 puppet-user[11136]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 24 09:52:44 node-4 puppet-user[11136]: (/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 24 09:52:44 node-4 puppet-user[11136]: Finished catalog run in 1.84 seconds
Jul 24 09:52:45 node-4 puppet-user[11662]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 24 09:52:46 node-4 puppet-user[11662]: Compiled catalog for node-4.domain.tld in environment production in 0.19 seconds
Jul 24 09:52:46 node-4 puppet-user[11662]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 24 09:52:46 node-4 puppet-user[11662]: (/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 24 09:52:46 node-4 puppet-user[11662]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 24 09:52:46 node-4 puppet-user[11662]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 24 09:52:46 node-4 puppet-user[11662]: Finished catalog run in 0.26 seconds
Jul 24 09:52:47 node-4 puppet-user[12148]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 24 09:52:48 node-4 puppet-user[12148]: Compiled catalog for node-4.domain.tld in environment production in 0.13 seconds
Jul 24 09:52:48 node-4 puppet-user[12148]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 24 09:52:48 node-4 kernel: [   67.903031] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 24 09:52:48 node-4 kernel: [   67.903083] 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 24 09:52:48 node-4 puppet-user[12148]: (/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 24 09:52:48 node-4 puppet-user[12148]: Finished catalog run in 0.07 seconds
Jul 24 09:52:49 node-4 puppet-user[12602]: (Scope(Class[main])) MODULAR: sync_time
Jul 24 09:52:49 node-4 puppet-user[12602]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 24 09:52:49 node-4 ntpdate[13135]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 24 09:52:50 node-4 kernel: [   69.846012] init: plymouth-upstart-bridge main process ended, respawning
Jul 24 09:52:50 node-4 puppet-agent[8954]: Could not run: SIGTERM
Jul 24 09:52:50 node-4 kernel: [   70.122115] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 24 09:52:50 node-4 ec2: 
Jul 24 09:52:50 node-4 ec2: #############################################################
Jul 24 09:52:50 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 24 09:52:50 node-4 ec2: 1024 0c:16:56:e1:9e:b4:69:46:2e:39:4c:21:bf:1d:55:53  root@node-4.domain.tld (DSA)
Jul 24 09:52:50 node-4 ec2: 256 49:83:02:de:16:0a:08:7b:0e:bd:17:eb:ba:a4:01:3a  root@node-4.domain.tld (ECDSA)
Jul 24 09:52:50 node-4 ec2: 256 25:cd:00:a8:3a:bd:73:21:84:64:2a:49:9f:34:61:58  root@node-4.domain.tld (ED25519)
Jul 24 09:52:50 node-4 ec2: 2048 76:76:0b:0d:d2:81:0f:f5:e7:7e:59:af:b1:4c:bb:ec  root@node-4.domain.tld (RSA)
Jul 24 09:52:50 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 24 09:52:50 node-4 ec2: #############################################################
Jul 24 09:52:56 node-4 ntpdate[13135]: adjust time server 10.20.0.2 offset 0.001597 sec
Jul 24 09:52:56 node-4 puppet-user[12602]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 24 09:52:56 node-4 puppet-user[12602]: Finished catalog run in 6.17 seconds
Jul 24 09:53:00 node-4 puppet-user[13382]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 24 09:53:00 node-4 puppet-user[13382]: Compiled catalog for node-4.domain.tld in environment production in 0.08 seconds
Jul 24 09:53:01 node-4 puppet-user[13382]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 24 09:53:01 node-4 puppet-user[13382]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Jul 24 09:53:01 node-4 puppet-user[13382]: Finished catalog run in 0.07 seconds
Jul 24 09:53:01 node-4 CRON[13845]: (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 24 09:53:02 node-4 puppet-user[13837]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 24 09:53:03 node-4 puppet-user[13837]: Compiled catalog for node-4.domain.tld in environment production in 1.01 seconds
Jul 24 09:53:03 node-4 puppet-user[13837]: (/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 24 09:53:03 node-4 puppet-user[13837]: (/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 24 09:53:03 node-4 puppet-user[13837]: (/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 24 09:53:03 node-4 puppet-user[13837]: (/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 24 09:53:03 node-4 puppet-user[13837]: (/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 24 09:53:03 node-4 puppet-user[13837]: (/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 24 09:53:03 node-4 puppet-user[13837]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 24 09:53:03 node-4 puppet-user[13837]: (/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 24 09:53:03 node-4 puppet-user[13837]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 24 09:53:03 node-4 puppet-user[13837]: (/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 24 09:53:04 node-4 puppet-user[13837]: (/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 24 09:53:04 node-4 puppet-user[13837]: (/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 24 09:53:04 node-4 puppet-user[13837]: (/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 24 09:53:04 node-4 puppet-user[13837]: (/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 24 09:53:04 node-4 puppet-user[13837]: (/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 24 09:53:04 node-4 puppet-user[13837]: (/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 24 09:53:11 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 09:53:11 node-4 nailgun-agent: I, [2016-07-24T09:53:11.920533 #13848]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 24 09:53:21 node-4 puppet-user[13837]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 24 09:53:21 node-4 puppet-user[13837]: Finished catalog run in 17.96 seconds
Jul 24 09:53:23 node-4 puppet-user[14997]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 24 09:53:24 node-4 puppet-user[14997]: Compiled catalog for node-4.domain.tld in environment production in 0.13 seconds
Jul 24 09:53:24 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 09:53:24 node-4 nailgun-agent: I, [2016-07-24T09:53:24.885858 #13848]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 24 09:53:29 node-4 puppet-user[14997]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 24 09:54:01 node-4 CRON[17518]: (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 24 09:54:06 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 09:54:06 node-4 nailgun-agent: I, [2016-07-24T09:54:06.075998 #17521]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 24 09:54:06 node-4 puppet-user[14997]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 24 09:54:06 node-4 puppet-user[14997]: Finished catalog run in 42.24 seconds
Jul 24 09:54:08 node-4 puppet-user[17884]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 24 09:54:08 node-4 puppet-user[17884]: Compiled catalog for node-4.domain.tld in environment production in 0.54 seconds
Jul 24 09:54:08 node-4 puppet-user[17884]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 24 09:54:08 node-4 puppet-user[17884]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 24 09:54:08 node-4 puppet-user[17884]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 24 09:54:08 node-4 puppet-user[17884]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 24 09:54:08 node-4 puppet-user[17884]: Finished catalog run in 0.11 seconds
Jul 24 09:54:10 node-4 puppet-user[18353]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 24 09:54:11 node-4 puppet-user[18353]: Compiled catalog for node-4.domain.tld in environment production in 0.86 seconds
Jul 24 09:54:12 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 24 09:54:12 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 24 09:54:12 node-4 crontab[18780]: (root) LIST (root)
Jul 24 09:54:12 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 24 09:54:12 node-4 crontab[18781]: (root) REPLACE (root)
Jul 24 09:54:14 node-4 puppet-user[18353]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 24 09:54:15 node-4 puppet-user[18353]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 24 09:54:15 node-4 puppet-user[18353]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 24 09:54:15 node-4 puppet-user[18353]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 24 09:54:15 node-4 puppet-user[18353]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 24 09:54:15 node-4 puppet-user[18353]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 24 09:54:15 node-4 puppet-user[18353]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 24 09:54:15 node-4 puppet-user[18353]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 24 09:54:15 node-4 puppet-user[18353]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 24 09:54:15 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 24 09:54:15 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 24 09:54:15 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 24 09:54:15 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/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 24 09:54:16 node-4 puppet-user[18353]: (/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 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/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 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/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 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/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 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/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 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/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 24 09:54:16 node-4 puppet-user[18353]: (/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 24 09:54:16 node-4 puppet-user[18353]: (/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 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/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 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/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 24 09:54:16 node-4 puppet-user[18353]: (/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 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 24 09:54:16 node-4 puppet-user[18353]: (/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 24 09:54:16 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8406" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 09:54:16 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 24 09:54:18 node-4 multipathd: uevent trigger error
<27>Jul 24 09:54:18 node-4 multipathd: uevent trigger error
<27>Jul 24 09:54:18 node-4 multipathd: uevent trigger error
<27>Jul 24 09:54:18 node-4 multipathd: uevent trigger error
<27>Jul 24 09:54:18 node-4 multipathd: uevent trigger error
<27>Jul 24 09:54:39 node-4 multipathd: uevent trigger error
<27>Jul 24 09:54:39 node-4 multipathd: uevent trigger error
<27>Jul 24 09:54:39 node-4 multipathd: uevent trigger error
<27>Jul 24 09:54:39 node-4 multipathd: uevent trigger error
<27>Jul 24 09:54:39 node-4 multipathd: uevent trigger error
<27>Jul 24 09:55:30 node-4 multipathd: uevent trigger error
<27>Jul 24 09:55:30 node-4 multipathd: uevent trigger error
<27>Jul 24 09:55:30 node-4 multipathd: uevent trigger error
<27>Jul 24 09:55:30 node-4 multipathd: uevent trigger error
<27>Jul 24 09:55:30 node-4 multipathd: uevent trigger error
<27>Jul 24 09:56:14 node-4 ntpdate[2415]: no servers can be used, exiting
<27>Jul 24 09:56:14 node-4 ntpdate[2635]: no servers can be used, exiting
<27>Jul 24 09:56:46 node-4 multipathd: uevent trigger error
<27>Jul 24 09:56:46 node-4 multipathd: uevent trigger error
<27>Jul 24 09:56:46 node-4 multipathd: uevent trigger error
<27>Jul 24 09:56:46 node-4 multipathd: uevent trigger error
<27>Jul 24 09:56:46 node-4 multipathd: uevent trigger error
<27>Jul 24 09:56:49 node-4 multipathd: uevent trigger error
<27>Jul 24 09:56:49 node-4 multipathd: uevent trigger error
<27>Jul 24 09:56:49 node-4 multipathd: uevent trigger error
<27>Jul 24 09:56:49 node-4 multipathd: uevent trigger error
<27>Jul 24 09:56:49 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:01 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:01 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:01 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:01 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:01 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:04 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:04 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:04 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:04 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:04 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:11 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:11 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:11 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:11 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:11 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:55 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:55 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:55 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:55 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:55 node-4 multipathd: uevent trigger error
<27>Jul 24 09:57:55 node-4 multipathd: uevent trigger error
<43>Jul 24 09:58:18 node-4 apache2_error [Sun Jul 24 09:58:09.637079 2016] [mpm_event:notice] [pid 15713:tid 140391305914240] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 09:58:18 node-4 apache2_error [Sun Jul 24 09:58:09.637221 2016] [core:notice] [pid 15713:tid 140391305914240] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 24 09:58:18 node-4 apache2_error [Sun Jul 24 09:58:12.931494 2016] [mpm_event:notice] [pid 15713:tid 140391305914240] AH00491: caught SIGTERM, shutting down
<43>Jul 24 09:58:18 node-4 apache2_error [Sun Jul 24 09:58:14.022165 2016] [mpm_worker:notice] [pid 16022:tid 140714227099520] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 09:58:18 node-4 apache2_error [Sun Jul 24 09:58:14.022219 2016] [core:notice] [pid 16022:tid 140714227099520] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 09:58:18 node-4 multipathd: uevent trigger error
<27>Jul 24 09:58:18 node-4 multipathd: uevent trigger error
<27>Jul 24 09:58:18 node-4 multipathd: uevent trigger error
<27>Jul 24 09:58:18 node-4 multipathd: uevent trigger error
<27>Jul 24 09:58:18 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:00 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 24 09:59:04 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:04 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:04 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:04 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:04 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:08 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:08 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:08 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:08 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:08 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:14 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:14 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:14 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:14 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:14 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:14 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:14 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:22 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:22 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:23 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:23 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:23 node-4 multipathd: uevent trigger error
<129>Jul 24 09:59:25 node-4 haproxy[26684]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 09:59:28 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:28 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:28 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:28 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:28 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:31 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:31 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:31 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:31 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:31 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:31 node-4 multipathd: uevent trigger error
<129>Jul 24 09:59:34 node-4 haproxy[28949]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:35 node-4 haproxy[28953]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 09:59:37 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:37 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:37 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:37 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:37 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:37 node-4 multipathd: uevent trigger error
<129>Jul 24 09:59:39 node-4 haproxy[30113]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:40 node-4 haproxy[30134]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:40 node-4 haproxy[30134]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 09:59:42 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:42 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:42 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:42 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:42 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:42 node-4 multipathd: uevent trigger error
<129>Jul 24 09:59:44 node-4 haproxy[31413]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:45 node-4 haproxy[31417]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:45 node-4 haproxy[31417]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:46 node-4 haproxy[31417]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:46 node-4 haproxy[31417]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 09:59:47 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:47 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:47 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:47 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:47 node-4 multipathd: uevent trigger error
<129>Jul 24 09:59:49 node-4 haproxy[32533]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:50 node-4 haproxy[32537]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:50 node-4 haproxy[32537]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:50 node-4 haproxy[32537]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:51 node-4 haproxy[32537]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:51 node-4 haproxy[32537]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 09:59:52 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:52 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:52 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:53 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:53 node-4 multipathd: uevent trigger error
<129>Jul 24 09:59:53 node-4 haproxy[32537]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:53 node-4 haproxy[32537]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 09:59:53 node-4 haproxy[32537]: proxy aodh has no server available!
<129>Jul 24 09:59:55 node-4 haproxy[1236]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:55 node-4 haproxy[1236]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:55 node-4 haproxy[1236]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:56 node-4 haproxy[1240]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:56 node-4 haproxy[1240]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:56 node-4 haproxy[1240]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:56 node-4 haproxy[1240]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 09:59:58 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:58 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:58 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:58 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:58 node-4 multipathd: uevent trigger error
<27>Jul 24 09:59:58 node-4 multipathd: uevent trigger error
<129>Jul 24 09:59:58 node-4 haproxy[1240]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:58 node-4 haproxy[1240]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 09:59:58 node-4 haproxy[1240]: proxy aodh has no server available!
<129>Jul 24 09:59:58 node-4 haproxy[1240]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 09:59:59 node-4 haproxy[1240]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 09:59:59 node-4 haproxy[1240]: proxy ceilometer has no server available!
<129>Jul 24 10:00:00 node-4 haproxy[2356]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:00 node-4 haproxy[2356]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:01 node-4 haproxy[2360]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:01 node-4 haproxy[2360]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:01 node-4 haproxy[2360]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:02 node-4 haproxy[2360]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:02 node-4 haproxy[2360]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 10:00:03 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:03 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:03 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:03 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:03 node-4 multipathd: uevent trigger error
<129>Jul 24 10:00:03 node-4 haproxy[2360]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:04 node-4 haproxy[2360]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:04 node-4 haproxy[2360]: proxy aodh has no server available!
<129>Jul 24 10:00:04 node-4 haproxy[2360]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:04 node-4 haproxy[2360]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:04 node-4 haproxy[2360]: proxy ceilometer has no server available!
<129>Jul 24 10:00:06 node-4 haproxy[3519]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:06 node-4 haproxy[3519]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:06 node-4 haproxy[3519]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:06 node-4 haproxy[3519]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:07 node-4 haproxy[3519]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:07 node-4 haproxy[3519]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:07 node-4 haproxy[3519]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:07 node-4 haproxy[3519]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:07 node-4 haproxy[3519]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 10:00:08 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:08 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:08 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:08 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:08 node-4 multipathd: uevent trigger error
<129>Jul 24 10:00:09 node-4 haproxy[3519]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:09 node-4 haproxy[3519]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:09 node-4 haproxy[3519]: proxy aodh has no server available!
<129>Jul 24 10:00:09 node-4 haproxy[3519]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:09 node-4 haproxy[3519]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:09 node-4 haproxy[3519]: proxy ceilometer has no server available!
<129>Jul 24 10:00:11 node-4 haproxy[4700]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:11 node-4 haproxy[4700]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:11 node-4 haproxy[4700]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:12 node-4 haproxy[4706]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:12 node-4 haproxy[4706]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:12 node-4 haproxy[4706]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:12 node-4 haproxy[4706]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:12 node-4 haproxy[4706]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:13 node-4 haproxy[4706]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:13 node-4 haproxy[4706]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:13 node-4 haproxy[4706]: Server horizon/node-2 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 24 10:00:13 node-4 haproxy[4706]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 10:00:14 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:14 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:14 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:14 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:14 node-4 multipathd: uevent trigger error
<129>Jul 24 10:00:14 node-4 haproxy[4706]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:14 node-4 haproxy[4706]: Server glance-registry/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:14 node-4 haproxy[4706]: proxy glance-registry has no server available!
<27>Jul 24 10:00:14 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Jul 24 10:00:14 node-4 haproxy[4706]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:15 node-4 haproxy[4706]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:15 node-4 haproxy[4706]: proxy aodh has no server available!
<129>Jul 24 10:00:15 node-4 haproxy[4706]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:15 node-4 haproxy[4706]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:15 node-4 haproxy[4706]: proxy ceilometer has no server available!
<129>Jul 24 10:00:17 node-4 haproxy[5913]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:17 node-4 haproxy[5913]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:17 node-4 haproxy[5913]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:17 node-4 haproxy[5913]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:17 node-4 haproxy[5913]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:18 node-4 haproxy[5917]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:18 node-4 haproxy[5917]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:18 node-4 haproxy[5917]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:18 node-4 haproxy[5917]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:18 node-4 haproxy[5917]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:18 node-4 haproxy[5917]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:18 node-4 haproxy[5917]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:19 node-4 haproxy[5917]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:19 node-4 haproxy[5917]: Server horizon/node-2 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 24 10:00:19 node-4 haproxy[5917]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 10:00:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:20 node-4 multipathd: uevent trigger error
<129>Jul 24 10:00:20 node-4 haproxy[5917]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:20 node-4 haproxy[5917]: Server glance-registry/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:20 node-4 haproxy[5917]: proxy glance-registry has no server available!
<129>Jul 24 10:00:20 node-4 haproxy[5917]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:20 node-4 haproxy[5917]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:20 node-4 haproxy[5917]: proxy aodh has no server available!
<129>Jul 24 10:00:20 node-4 haproxy[5917]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:20 node-4 haproxy[5917]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:20 node-4 haproxy[5917]: proxy ceilometer has no server available!
<129>Jul 24 10:00:20 node-4 haproxy[5917]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:21 node-4 haproxy[5917]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:21 node-4 haproxy[5917]: proxy nova-novncproxy has no server available!
<129>Jul 24 10:00:22 node-4 haproxy[7058]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:22 node-4 haproxy[7058]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:22 node-4 haproxy[7058]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:22 node-4 haproxy[7058]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:23 node-4 haproxy[7062]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:23 node-4 haproxy[7062]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:23 node-4 haproxy[7062]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:23 node-4 haproxy[7062]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:23 node-4 haproxy[7062]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:23 node-4 haproxy[7062]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:23 node-4 haproxy[7062]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:23 node-4 haproxy[7062]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:24 node-4 haproxy[7062]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:24 node-4 haproxy[7062]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:24 node-4 haproxy[7062]: Server horizon/node-2 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 24 10:00:24 node-4 haproxy[7062]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 10:00:25 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:25 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:25 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:25 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:25 node-4 multipathd: uevent trigger error
<129>Jul 24 10:00:25 node-4 haproxy[7062]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:25 node-4 haproxy[7062]: Server glance-registry/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:25 node-4 haproxy[7062]: proxy glance-registry has no server available!
<129>Jul 24 10:00:25 node-4 haproxy[7062]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:25 node-4 haproxy[7062]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:25 node-4 haproxy[7062]: proxy aodh has no server available!
<129>Jul 24 10:00:26 node-4 haproxy[7062]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:26 node-4 haproxy[7062]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:26 node-4 haproxy[7062]: proxy ceilometer has no server available!
<129>Jul 24 10:00:26 node-4 haproxy[7062]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:26 node-4 haproxy[7062]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:26 node-4 haproxy[7062]: proxy nova-novncproxy has no server available!
<129>Jul 24 10:00:28 node-4 haproxy[8261]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:28 node-4 haproxy[8261]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:28 node-4 haproxy[8261]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:28 node-4 haproxy[8261]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:28 node-4 haproxy[8261]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:28 node-4 haproxy[8261]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:28 node-4 haproxy[8261]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:29 node-4 haproxy[8290]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:29 node-4 haproxy[8290]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:29 node-4 haproxy[8290]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:29 node-4 haproxy[8290]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:29 node-4 haproxy[8290]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:29 node-4 haproxy[8290]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:29 node-4 haproxy[8290]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:29 node-4 haproxy[8290]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:29 node-4 haproxy[8290]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:30 node-4 haproxy[8290]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:30 node-4 haproxy[8290]: Server horizon/node-2 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 24 10:00:30 node-4 haproxy[8290]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:31 node-4 haproxy[8290]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:31 node-4 haproxy[8290]: Server glance-registry/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:31 node-4 haproxy[8290]: proxy glance-registry has no server available!
<27>Jul 24 10:00:31 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:31 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:31 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:31 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:31 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:31 node-4 multipathd: uevent trigger error
<129>Jul 24 10:00:31 node-4 haproxy[8290]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:31 node-4 haproxy[8290]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:31 node-4 haproxy[8290]: proxy aodh has no server available!
<129>Jul 24 10:00:31 node-4 haproxy[8290]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:31 node-4 haproxy[8290]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:31 node-4 haproxy[8290]: proxy ceilometer has no server available!
<129>Jul 24 10:00:32 node-4 haproxy[8290]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:32 node-4 haproxy[8290]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:32 node-4 haproxy[8290]: proxy nova-novncproxy has no server available!
<27>Jul 24 10:00:34 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:34 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:34 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:34 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:34 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:34 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:38 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:38 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:38 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:38 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:38 node-4 multipathd: uevent trigger error
<27>Jul 24 10:00:38 node-4 multipathd: uevent trigger error
<129>Jul 24 10:00:38 node-4 haproxy[8290]: Server keystone-1/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:38 node-4 haproxy[8290]: Server keystone-1/node-5 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:38 node-4 haproxy[8290]: proxy keystone-1 has no server available!
<129>Jul 24 10:00:38 node-4 haproxy[8290]: Server keystone-2/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:38 node-4 haproxy[8290]: Server keystone-2/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:38 node-4 haproxy[8290]: proxy keystone-2 has no server available!
<129>Jul 24 10:00:38 node-4 haproxy[8290]: Server nova-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:38 node-4 haproxy[8290]: Server nova-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:38 node-4 haproxy[8290]: proxy nova-api has no server available!
<129>Jul 24 10:00:38 node-4 haproxy[8290]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:38 node-4 haproxy[8290]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:38 node-4 haproxy[8290]: proxy nova-metadata-api has no server available!
<129>Jul 24 10:00:38 node-4 haproxy[8290]: Server cinder-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:38 node-4 haproxy[8290]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:38 node-4 haproxy[8290]: proxy cinder-api has no server available!
<129>Jul 24 10:00:38 node-4 haproxy[8290]: Server glance-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:38 node-4 haproxy[8290]: Server glance-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:38 node-4 haproxy[8290]: proxy glance-api has no server available!
<129>Jul 24 10:00:38 node-4 haproxy[8290]: Server glance-glare/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:39 node-4 haproxy[8290]: Server glance-glare/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:39 node-4 haproxy[8290]: proxy glance-glare has no server available!
<129>Jul 24 10:00:39 node-4 haproxy[8290]: Server neutron/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:39 node-4 haproxy[8290]: Server neutron/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:39 node-4 haproxy[8290]: proxy neutron has no server available!
<129>Jul 24 10:00:39 node-4 haproxy[8290]: Server mysqld/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:39 node-4 haproxy[8290]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:39 node-4 haproxy[8290]: proxy mysqld has no server available!
<129>Jul 24 10:00:39 node-4 haproxy[8290]: Server object-storage/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:39 node-4 haproxy[8290]: Server object-storage/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:39 node-4 haproxy[8290]: proxy object-storage has no server available!
<129>Jul 24 10:00:39 node-4 haproxy[8290]: Server heat-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:39 node-4 haproxy[8290]: Server heat-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:39 node-4 haproxy[8290]: proxy heat-api has no server available!
<129>Jul 24 10:00:39 node-4 haproxy[8290]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:39 node-4 haproxy[8290]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:39 node-4 haproxy[8290]: proxy heat-api-cfn has no server available!
<129>Jul 24 10:00:39 node-4 haproxy[8290]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 10:00:40 node-4 haproxy[8290]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 10:00:40 node-4 haproxy[8290]: proxy heat-api-cloudwatch has no server available!
<27>Jul 24 10:01:08 node-4 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 10:01:08 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 24 10:01:14 node-4 multipathd: uevent trigger error
<27>Jul 24 10:01:14 node-4 multipathd: uevent trigger error
<27>Jul 24 10:01:14 node-4 multipathd: uevent trigger error
<27>Jul 24 10:01:14 node-4 multipathd: uevent trigger error
<27>Jul 24 10:01:14 node-4 multipathd: uevent trigger error
<43>Jul 24 10:01:18 node-4 apache2_error [Sun Jul 24 10:01:11.309318 2016] [mpm_worker:notice] [pid 16022:tid 140714227099520] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 10:01:18 node-4 apache2_error [Sun Jul 24 10:01:11.316961 2016] [mpm_worker:warn] [pid 16022:tid 140714227099520] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 10:01:18 node-4 apache2_error [Sun Jul 24 10:01:11.317303 2016] [mpm_worker:notice] [pid 16022:tid 140714227099520] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 10:01:18 node-4 apache2_error [Sun Jul 24 10:01:11.317309 2016] [core:notice] [pid 16022:tid 140714227099520] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 10:01:18 node-4 multipathd: uevent trigger error
<27>Jul 24 10:01:18 node-4 multipathd: uevent trigger error
<27>Jul 24 10:01:18 node-4 multipathd: uevent trigger error
<27>Jul 24 10:01:18 node-4 multipathd: uevent trigger error
<27>Jul 24 10:01:19 node-4 multipathd: uevent trigger error
<27>Jul 24 10:01:19 node-4 multipathd: uevent trigger error
<27>Jul 24 10:01:39 node-4 multipathd: uevent trigger error
<27>Jul 24 10:01:43 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 24 10:02:19 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 24 10:02:21 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 24 10:03:37 node-4 multipathd: uevent trigger error
<27>Jul 24 10:03:37 node-4 multipathd: uevent trigger error
<27>Jul 24 10:03:37 node-4 multipathd: uevent trigger error
<27>Jul 24 10:03:37 node-4 multipathd: uevent trigger error
<27>Jul 24 10:03:37 node-4 multipathd: uevent trigger error
<27>Jul 24 10:03:46 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 24 10:03:52 node-4 multipathd: uevent trigger error
<27>Jul 24 10:03:52 node-4 multipathd: uevent trigger error
<27>Jul 24 10:03:52 node-4 multipathd: uevent trigger error
<27>Jul 24 10:03:52 node-4 multipathd: uevent trigger error
<27>Jul 24 10:03:52 node-4 multipathd: uevent trigger error
<27>Jul 24 10:03:59 node-4 multipathd: uevent trigger error
<27>Jul 24 10:03:59 node-4 multipathd: uevent trigger error
<27>Jul 24 10:03:59 node-4 multipathd: uevent trigger error
<27>Jul 24 10:03:59 node-4 multipathd: uevent trigger error
<27>Jul 24 10:03:59 node-4 multipathd: uevent trigger error
<27>Jul 24 10:03:59 node-4 multipathd: uevent trigger error
<27>Jul 24 10:07:15 node-4 multipathd: uevent trigger error
<27>Jul 24 10:07:15 node-4 multipathd: uevent trigger error
<27>Jul 24 10:07:15 node-4 multipathd: uevent trigger error
<27>Jul 24 10:07:15 node-4 multipathd: uevent trigger error
<27>Jul 24 10:07:15 node-4 multipathd: uevent trigger error
<27>Jul 24 10:07:15 node-4 multipathd: uevent trigger error
<43>Jul 24 10:08:39 node-4 apache2_error [Sun Jul 24 10:08:34.635551 2016] [mpm_worker:notice] [pid 16022:tid 140714227099520] AH00295: caught SIGTERM, shutting down
<43>Jul 24 10:08:39 node-4 apache2_error [Sun Jul 24 10:08:35.386134 2016] [mpm_worker:notice] [pid 14680:tid 139674953131904] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 10:08:39 node-4 apache2_error [Sun Jul 24 10:08:35.386163 2016] [core:notice] [pid 14680:tid 139674953131904] AH00094: Command line: '/usr/sbin/apache2'
<11>Jul 24 10:08:44 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<43>Jul 24 10:09:09 node-4 apache2_error [Sun Jul 24 10:09:07.520229 2016] [mpm_worker:notice] [pid 14680:tid 139674953131904] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 10:09:09 node-4 apache2_error [Sun Jul 24 10:09:07.526679 2016] [mpm_worker:warn] [pid 14680:tid 139674953131904] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 10:09:09 node-4 apache2_error [Sun Jul 24 10:09:07.532397 2016] [mpm_worker:notice] [pid 14680:tid 139674953131904] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 10:09:09 node-4 apache2_error [Sun Jul 24 10:09:07.532420 2016] [core:notice] [pid 14680:tid 139674953131904] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 10:09:13 node-4 multipathd: uevent trigger error
<27>Jul 24 10:09:13 node-4 multipathd: uevent trigger error
<27>Jul 24 10:09:13 node-4 multipathd: uevent trigger error
<27>Jul 24 10:09:13 node-4 multipathd: uevent trigger error
<27>Jul 24 10:09:13 node-4 multipathd: uevent trigger error
<27>Jul 24 10:09:13 node-4 multipathd: uevent trigger error
<27>Jul 24 10:10:13 node-4 multipathd: uevent trigger error
<27>Jul 24 10:10:13 node-4 multipathd: uevent trigger error
<27>Jul 24 10:10:13 node-4 multipathd: uevent trigger error
<27>Jul 24 10:10:13 node-4 multipathd: uevent trigger error
<27>Jul 24 10:10:13 node-4 multipathd: uevent trigger error
<27>Jul 24 10:11:32 node-4 multipathd: uevent trigger error
<27>Jul 24 10:11:32 node-4 multipathd: uevent trigger error
<27>Jul 24 10:11:32 node-4 multipathd: uevent trigger error
<27>Jul 24 10:11:32 node-4 multipathd: uevent trigger error
<27>Jul 24 10:11:32 node-4 multipathd: uevent trigger error
<11>Jul 24 10:13:26 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<27>Jul 24 10:16:16 node-4 multipathd: uevent trigger error
<27>Jul 24 10:16:16 node-4 multipathd: uevent trigger error
<27>Jul 24 10:16:16 node-4 multipathd: uevent trigger error
<27>Jul 24 10:16:16 node-4 multipathd: uevent trigger error
<27>Jul 24 10:16:16 node-4 multipathd: uevent trigger error
<27>Jul 24 10:16:16 node-4 multipathd: uevent trigger error
<11>Jul 24 10:16:47 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<27>Jul 24 10:18:26 node-4 multipathd: uevent trigger error
<27>Jul 24 10:18:26 node-4 multipathd: uevent trigger error
<27>Jul 24 10:18:26 node-4 multipathd: uevent trigger error
<27>Jul 24 10:18:26 node-4 multipathd: uevent trigger error
<27>Jul 24 10:18:26 node-4 multipathd: uevent trigger error
<27>Jul 24 10:19:36 node-4 multipathd: uevent trigger error
<27>Jul 24 10:19:36 node-4 multipathd: uevent trigger error
<27>Jul 24 10:19:36 node-4 multipathd: uevent trigger error
<27>Jul 24 10:19:36 node-4 multipathd: uevent trigger error
<27>Jul 24 10:19:36 node-4 multipathd: uevent trigger error
<27>Jul 24 10:19:36 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:11 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:11 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:11 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:11 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:11 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:11 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:32 node-4 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Jul 24 10:20:32 node-4 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Jul 24 10:20:32 node-4 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Jul 24 10:20:33 node-4 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Jul 24 10:20:33 node-4 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Jul 24 10:20:34 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:34 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:34 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:34 node-4 multipathd: uevent trigger error
<27>Jul 24 10:20:34 node-4 multipathd: uevent trigger error
<43>Jul 24 10:21:29 node-4 apache2_error [Sun Jul 24 10:21:20.240137 2016] [mpm_worker:notice] [pid 14680:tid 139674953131904] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 10:21:29 node-4 apache2_error [Sun Jul 24 10:21:20.623620 2016] [mpm_worker:warn] [pid 14680:tid 139674953131904] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 10:21:29 node-4 apache2_error [Sun Jul 24 10:21:20.628607 2016] [mpm_worker:notice] [pid 14680:tid 139674953131904] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 10:21:29 node-4 apache2_error [Sun Jul 24 10:21:20.628623 2016] [core:notice] [pid 14680:tid 139674953131904] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 24 10:21:59 node-4 apache2_error [Sun Jul 24 10:21:57.487511 2016] [mpm_worker:notice] [pid 14680:tid 139674953131904] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 10:21:59 node-4 apache2_error [Sun Jul 24 10:21:58.245488 2016] [mpm_worker:warn] [pid 14680:tid 139674953131904] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 10:21:59 node-4 apache2_error [Sun Jul 24 10:21:58.252649 2016] [mpm_worker:notice] [pid 14680:tid 139674953131904] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 10:21:59 node-4 apache2_error [Sun Jul 24 10:21:58.252666 2016] [core:notice] [pid 14680:tid 139674953131904] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 10:22:01 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:01 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:01 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:01 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:01 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:01 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:01 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:01 node-4 multipathd: uevent trigger error
<11>Jul 24 10:22:10 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<27>Jul 24 10:22:19 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:19 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:19 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:19 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:19 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:53 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:53 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:53 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:53 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:53 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:59 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:59 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:59 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:59 node-4 multipathd: uevent trigger error
<27>Jul 24 10:22:59 node-4 multipathd: uevent trigger error
<27>Jul 24 10:23:03 node-4 multipathd: uevent trigger error
<27>Jul 24 10:23:03 node-4 multipathd: uevent trigger error
<27>Jul 24 10:23:03 node-4 multipathd: uevent trigger error
<27>Jul 24 10:23:03 node-4 multipathd: uevent trigger error
<27>Jul 24 10:23:36 node-4 multipathd: uevent trigger error
<27>Jul 24 10:23:36 node-4 multipathd: uevent trigger error
<27>Jul 24 10:23:36 node-4 multipathd: uevent trigger error
<27>Jul 24 10:23:36 node-4 multipathd: uevent trigger error
<27>Jul 24 10:23:36 node-4 multipathd: uevent trigger error
<27>Jul 24 10:24:28 node-4 multipathd: uevent trigger error
<27>Jul 24 10:24:28 node-4 multipathd: uevent trigger error
<27>Jul 24 10:24:28 node-4 multipathd: uevent trigger error
<27>Jul 24 10:24:28 node-4 multipathd: uevent trigger error
<27>Jul 24 10:24:28 node-4 multipathd: uevent trigger error
<27>Jul 24 10:24:41 node-4 multipathd: uevent trigger error
<27>Jul 24 10:24:41 node-4 multipathd: uevent trigger error
<27>Jul 24 10:24:41 node-4 multipathd: uevent trigger error
<27>Jul 24 10:24:41 node-4 multipathd: uevent trigger error
<27>Jul 24 10:24:41 node-4 multipathd: uevent trigger error
<27>Jul 24 10:24:41 node-4 multipathd: uevent trigger error
<11>Jul 24 10:24:51 node-4 liberasurecode[5735]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:51 node-4 liberasurecode[5735]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:51 node-4 liberasurecode[5735]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:51 node-4 liberasurecode[5735]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:51 node-4 liberasurecode[5759]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:51 node-4 liberasurecode[5759]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:51 node-4 liberasurecode[5759]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:51 node-4 liberasurecode[5759]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:53 node-4 liberasurecode[6149]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:53 node-4 liberasurecode[6149]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:53 node-4 liberasurecode[6149]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:53 node-4 liberasurecode[6149]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:59 node-4 liberasurecode[6864]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:59 node-4 liberasurecode[6864]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:59 node-4 liberasurecode[6864]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:59 node-4 liberasurecode[6864]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:59 node-4 liberasurecode[6903]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:59 node-4 liberasurecode[6903]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:59 node-4 liberasurecode[6903]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:59 node-4 liberasurecode[6903]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:59 node-4 liberasurecode[6941]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:59 node-4 liberasurecode[6941]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:59 node-4 liberasurecode[6941]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:59 node-4 liberasurecode[6941]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:59 node-4 liberasurecode[7006]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:59 node-4 liberasurecode[7006]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:59 node-4 liberasurecode[7006]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:24:59 node-4 liberasurecode[7006]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 10:25:00 node-4 liberasurecode[7018]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:25:00 node-4 liberasurecode[7018]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:25:00 node-4 liberasurecode[7018]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:25:00 node-4 liberasurecode[7018]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 10:25:00 node-4 liberasurecode[7030]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:25:00 node-4 liberasurecode[7030]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:25:00 node-4 liberasurecode[7030]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:25:00 node-4 liberasurecode[7030]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 10:25:00 node-4 liberasurecode[7042]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:25:00 node-4 liberasurecode[7042]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:25:00 node-4 liberasurecode[7042]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:25:00 node-4 liberasurecode[7042]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 10:25:02 node-4 liberasurecode[7334]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:25:02 node-4 liberasurecode[7334]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:25:02 node-4 liberasurecode[7334]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:25:02 node-4 liberasurecode[7334]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 24 10:25:06 node-4 multipathd: uevent trigger error
<27>Jul 24 10:25:06 node-4 multipathd: uevent trigger error
<27>Jul 24 10:25:06 node-4 multipathd: uevent trigger error
<27>Jul 24 10:25:06 node-4 multipathd: uevent trigger error
<27>Jul 24 10:25:06 node-4 multipathd: uevent trigger error
<11>Jul 24 10:25:10 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<27>Jul 24 10:25:11 node-4 multipathd: uevent trigger error
<27>Jul 24 10:25:11 node-4 multipathd: uevent trigger error
<27>Jul 24 10:25:11 node-4 multipathd: uevent trigger error
<27>Jul 24 10:25:11 node-4 multipathd: uevent trigger error
<27>Jul 24 10:25:11 node-4 multipathd: uevent trigger error
<27>Jul 24 10:26:12 node-4 multipathd: uevent trigger error
<27>Jul 24 10:26:12 node-4 multipathd: uevent trigger error
<27>Jul 24 10:26:12 node-4 multipathd: uevent trigger error
<27>Jul 24 10:26:12 node-4 multipathd: uevent trigger error
<27>Jul 24 10:26:12 node-4 multipathd: uevent trigger error
<11>Jul 24 10:28:06 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<27>Jul 24 10:28:10 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:10 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:10 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:10 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:10 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:15 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:15 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:15 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:15 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:15 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:15 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:29 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:29 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:29 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:29 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:29 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:33 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:33 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:33 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:33 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:33 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:34 node-4 multipathd: uevent trigger error
<11>Jul 24 10:28:47 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<27>Jul 24 10:28:48 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:48 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:48 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:48 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:48 node-4 multipathd: uevent trigger error
<27>Jul 24 10:28:48 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:01 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:01 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:01 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:01 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:01 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:06 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:06 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:06 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:06 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:06 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:10 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:10 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:10 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:10 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:10 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:15 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:15 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:15 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:15 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:15 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:20 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:25 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:25 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:25 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:25 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:25 node-4 multipathd: uevent trigger error
<27>Jul 24 10:29:30 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 24 10:29:30 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<11>Jul 24 10:30:02 node-4 liberasurecode[31626]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:30:02 node-4 liberasurecode[31626]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:30:02 node-4 liberasurecode[31626]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:30:02 node-4 liberasurecode[31626]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 24 10:31:05 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:05 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:05 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:05 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:05 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:13 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:13 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:13 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:13 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:13 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:24 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:24 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:24 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:24 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:24 node-4 multipathd: uevent trigger error
<129>Jul 24 10:31:34 node-4 haproxy[9963]: 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 24 10:31:34 node-4 haproxy[9963]: Server neutron/node-4 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 24 10:31:35 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:35 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:35 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:35 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:35 node-4 multipathd: uevent trigger error
<27>Jul 24 10:31:35 node-4 multipathd: uevent trigger error
<11>Jul 24 10:32:19 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<129>Jul 24 10:32:54 node-4 haproxy[9963]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<11>Jul 24 10:35:01 node-4 liberasurecode[14403]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:35:01 node-4 liberasurecode[14403]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:35:01 node-4 liberasurecode[14403]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 10:35:01 node-4 liberasurecode[14403]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
