Jul 25 14:21:26 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8374" x-info="http://www.rsyslog.com"] start
Jul 25 14:21:26 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 25 14:21:26 node-4 rsyslogd: rsyslogd's groupid changed to 104
Jul 25 14:21:26 node-4 rsyslogd: rsyslogd's userid changed to 101
Jul 25 14:21:26 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 25 14:21:26 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 25 14:21:26 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 25 14:21:26 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 25 14:21:26 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=7f830f36-5ee4-49df-8419-c0facfc77428 nomdmonddf nomdmonisw
Jul 25 14:21:26 node-4 kernel: [    0.000000] KERNEL supported cpus:
Jul 25 14:21:26 node-4 kernel: [    0.000000]   Intel GenuineIntel
Jul 25 14:21:26 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Jul 25 14:21:26 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Jul 25 14:21:26 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 25 14:21:26 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 25 14:21:26 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 25 14:21:26 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 25 14:21:26 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 25 14:21:26 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 25 14:21:26 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 25 14:21:26 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 25 14:21:26 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 25 14:21:26 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 25 14:21:26 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 25 14:21:26 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 25 14:21:26 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 25 14:21:26 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 25 14:21:26 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 25 14:21:26 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 25 14:21:26 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 25 14:21:26 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 25 14:21:26 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 25 14:21:26 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 25 14:21:26 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 25 14:21:26 node-4 kernel: [    0.000000] No AGP bridge found
Jul 25 14:21:26 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 25 14:21:26 node-4 kernel: [    0.000000] MTRR default type: write-back
Jul 25 14:21:26 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 25 14:21:26 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Jul 25 14:21:26 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 25 14:21:26 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 25 14:21:26 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 25 14:21:26 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 25 14:21:26 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 25 14:21:26 node-4 kernel: [    0.000000]   2 disabled
Jul 25 14:21:26 node-4 kernel: [    0.000000]   3 disabled
Jul 25 14:21:26 node-4 kernel: [    0.000000]   4 disabled
Jul 25 14:21:26 node-4 kernel: [    0.000000]   5 disabled
Jul 25 14:21:26 node-4 kernel: [    0.000000]   6 disabled
Jul 25 14:21:26 node-4 kernel: [    0.000000]   7 disabled
Jul 25 14:21:26 node-4 kernel: [    0.000000]   8 disabled
Jul 25 14:21:26 node-4 kernel: [    0.000000]   9 disabled
Jul 25 14:21:26 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 25 14:21:26 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 25 14:21:26 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 25 14:21:26 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 25 14:21:26 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 25 14:21:26 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Jul 25 14:21:26 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 25 14:21:26 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 25 14:21:26 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 25 14:21:26 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 25 14:21:26 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 25 14:21:26 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 25 14:21:26 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 25 14:21:26 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 25 14:21:26 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 25 14:21:26 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 25 14:21:26 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 25 14:21:26 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 25 14:21:26 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 25 14:21:26 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 25 14:21:26 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 25 14:21:26 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 25 14:21:26 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 25 14:21:26 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 25 14:21:26 node-4 kernel: [    0.000000] Zone ranges:
Jul 25 14:21:26 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] Movable zone start for each node
Jul 25 14:21:26 node-4 kernel: [    0.000000] Early memory node ranges
Jul 25 14:21:26 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 25 14:21:26 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 25 14:21:26 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 25 14:21:26 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 25 14:21:26 node-4 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 25 14:21:26 node-4 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 25 14:21:26 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 25 14:21:26 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 25 14:21:26 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 25 14:21:26 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 25 14:21:26 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 25 14:21:26 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 25 14:21:26 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 25 14:21:26 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 25 14:21:26 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 25 14:21:26 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 25 14:21:26 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 25 14:21:26 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 25 14:21:26 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 25 14:21:26 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 25 14:21:26 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 25 14:21:26 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 25 14:21:26 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 25 14:21:26 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 25 14:21:26 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 25 14:21:26 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 25 14:21:26 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 25 14:21:26 node-4 kernel: [    0.000000] Policy zone: Normal
Jul 25 14:21:26 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=7f830f36-5ee4-49df-8419-c0facfc77428 nomdmonddf nomdmonisw
Jul 25 14:21:26 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 25 14:21:26 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 25 14:21:26 node-4 kernel: [    0.000000] Checking aperture...
Jul 25 14:21:26 node-4 kernel: [    0.000000] No AGP bridge found
Jul 25 14:21:26 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 25 14:21:26 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 25 14:21:26 node-4 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 25 14:21:26 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 25 14:21:26 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 25 14:21:26 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 25 14:21:26 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 25 14:21:26 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 25 14:21:26 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 25 14:21:26 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 25 14:21:26 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 25 14:21:26 node-4 kernel: [    0.000000] console [tty0] enabled
Jul 25 14:21:26 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 25 14:21:26 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 25 14:21:26 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 25 14:21:26 node-4 kernel: [    0.000000] hpet clockevent registered
Jul 25 14:21:26 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 25 14:21:26 node-4 kernel: [    0.004000] tsc: Detected 3491.690 MHz processor
Jul 25 14:21:26 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.38 BogoMIPS (lpj=13966760)
Jul 25 14:21:26 node-4 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Jul 25 14:21:26 node-4 kernel: [    0.000043] Security Framework initialized
Jul 25 14:21:26 node-4 kernel: [    0.000061] AppArmor: AppArmor initialized
Jul 25 14:21:26 node-4 kernel: [    0.000062] Yama: becoming mindful.
Jul 25 14:21:26 node-4 kernel: [    0.001452] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 25 14:21:26 node-4 kernel: [    0.006326] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 25 14:21:26 node-4 kernel: [    0.008254] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 25 14:21:26 node-4 kernel: [    0.008282] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 25 14:21:26 node-4 kernel: [    0.008572] Initializing cgroup subsys memory
Jul 25 14:21:26 node-4 kernel: [    0.008580] Initializing cgroup subsys devices
Jul 25 14:21:26 node-4 kernel: [    0.008582] Initializing cgroup subsys freezer
Jul 25 14:21:26 node-4 kernel: [    0.008584] Initializing cgroup subsys blkio
Jul 25 14:21:26 node-4 kernel: [    0.008585] Initializing cgroup subsys perf_event
Jul 25 14:21:26 node-4 kernel: [    0.008588] Initializing cgroup subsys hugetlb
Jul 25 14:21:26 node-4 kernel: [    0.008608] CPU: Physical Processor ID: 0
Jul 25 14:21:26 node-4 kernel: [    0.008609] CPU: Processor Core ID: 0
Jul 25 14:21:26 node-4 kernel: [    0.008613] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 25 14:21:26 node-4 kernel: [    0.008613] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 25 14:21:26 node-4 kernel: [    0.009307] mce: CPU supports 22 MCE banks
Jul 25 14:21:26 node-4 kernel: [    0.009334] CPU0: Thermal monitoring enabled (TM1)
Jul 25 14:21:26 node-4 kernel: [    0.009355] process: using mwait in idle threads
Jul 25 14:21:26 node-4 kernel: [    0.009358] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 25 14:21:26 node-4 kernel: [    0.009358] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 25 14:21:26 node-4 kernel: [    0.009358] tlb_flushall_shift: 6
Jul 25 14:21:26 node-4 kernel: [    0.009446] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 25 14:21:26 node-4 kernel: [    0.010170] ACPI: Core revision 20131115
Jul 25 14:21:26 node-4 kernel: [    0.022809] ACPI: All ACPI Tables successfully acquired
Jul 25 14:21:26 node-4 kernel: [    0.022981] ftrace: allocating 28617 entries in 112 pages
Jul 25 14:21:26 node-4 kernel: [    0.031799] dmar: Host address width 46
Jul 25 14:21:26 node-4 kernel: [    0.031801] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 25 14:21:26 node-4 kernel: [    0.031807] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 25 14:21:26 node-4 kernel: [    0.031808] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 25 14:21:26 node-4 kernel: [    0.031812] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 25 14:21:26 node-4 kernel: [    0.031814] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 25 14:21:26 node-4 kernel: [    0.031815] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 25 14:21:26 node-4 kernel: [    0.031816] dmar: ATSR flags: 0x0
Jul 25 14:21:26 node-4 kernel: [    0.031818] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 25 14:21:26 node-4 kernel: [    0.031819] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 25 14:21:26 node-4 kernel: [    0.031934] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 25 14:21:26 node-4 kernel: [    0.031936] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 25 14:21:26 node-4 kernel: [    0.031937] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 25 14:21:26 node-4 kernel: [    0.031938] HPET id 0 under DRHD base 0xc7ffc000
Jul 25 14:21:26 node-4 kernel: [    0.031939] Your BIOS is broken and requested that x2apic be disabled.
Jul 25 14:21:26 node-4 kernel: [    0.031939] This will slightly decrease performance.
Jul 25 14:21:26 node-4 kernel: [    0.031939] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 25 14:21:26 node-4 kernel: [    0.032370] Enabled IRQ remapping in xapic mode
Jul 25 14:21:26 node-4 kernel: [    0.032371] x2apic not enabled, IRQ remapping is in xapic mode
Jul 25 14:21:26 node-4 kernel: [    0.032375] Switched APIC routing to physical flat.
Jul 25 14:21:26 node-4 kernel: [    0.032996] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 25 14:21:26 node-4 kernel: [    0.072643] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 25 14:21:26 node-4 kernel: [    0.072649] TSC deadline timer enabled
Jul 25 14:21:26 node-4 kernel: [    0.072656] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 25 14:21:26 node-4 kernel: [    0.072662] ... version:                3
Jul 25 14:21:26 node-4 kernel: [    0.072663] ... bit width:              48
Jul 25 14:21:26 node-4 kernel: [    0.072664] ... generic registers:      4
Jul 25 14:21:26 node-4 kernel: [    0.072665] ... value mask:             0000ffffffffffff
Jul 25 14:21:26 node-4 kernel: [    0.072666] ... max period:             0000ffffffffffff
Jul 25 14:21:26 node-4 kernel: [    0.072667] ... fixed-purpose events:   3
Jul 25 14:21:26 node-4 kernel: [    0.072668] ... event mask:             000000070000000f
Jul 25 14:21:26 node-4 kernel: [    0.074112] x86: Booting SMP configuration:
Jul 25 14:21:26 node-4 kernel: [    0.088218] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 25 14:21:26 node-4 kernel: [    0.074114] .... node  #0, CPUs:        #1  #2  #3
Jul 25 14:21:26 node-4 kernel: [    0.116123] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 25 14:21:26 node-4 kernel: [    0.270256] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 25 14:21:26 node-4 kernel: [    0.325870] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 25 14:21:26 node-4 kernel: [    0.382922] x86: Booted up 2 nodes, 16 CPUs
Jul 25 14:21:26 node-4 kernel: [    0.382925] smpboot: Total of 16 processors activated (111746.63 BogoMIPS)
Jul 25 14:21:26 node-4 kernel: [    0.406849] devtmpfs: initialized
Jul 25 14:21:26 node-4 kernel: [    0.409971] EVM: security.selinux
Jul 25 14:21:26 node-4 kernel: [    0.409973] EVM: security.SMACK64
Jul 25 14:21:26 node-4 kernel: [    0.409974] EVM: security.ima
Jul 25 14:21:26 node-4 kernel: [    0.409975] EVM: security.capability
Jul 25 14:21:26 node-4 kernel: [    0.410024] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 25 14:21:26 node-4 kernel: [    0.410691] pinctrl core: initialized pinctrl subsystem
Jul 25 14:21:26 node-4 kernel: [    0.410752] regulator-dummy: no parameters
Jul 25 14:21:26 node-4 kernel: [    0.410783] RTC time: 14:20:49, date: 07/25/16
Jul 25 14:21:26 node-4 kernel: [    0.410818] NET: Registered protocol family 16
Jul 25 14:21:26 node-4 kernel: [    0.410904] cpuidle: using governor ladder
Jul 25 14:21:26 node-4 kernel: [    0.410906] cpuidle: using governor menu
Jul 25 14:21:26 node-4 kernel: [    0.410940] ACPI: bus type PCI registered
Jul 25 14:21:26 node-4 kernel: [    0.410942] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 25 14:21:26 node-4 kernel: [    0.410988] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 25 14:21:26 node-4 kernel: [    0.410990] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 25 14:21:26 node-4 kernel: [    0.424724] PCI: Using configuration type 1 for base access
Jul 25 14:21:26 node-4 kernel: [    0.425727] bio: create slab <bio-0> at 0
Jul 25 14:21:26 node-4 kernel: [    0.426012] ACPI: Added _OSI(Module Device)
Jul 25 14:21:26 node-4 kernel: [    0.426014] ACPI: Added _OSI(Processor Device)
Jul 25 14:21:26 node-4 kernel: [    0.426015] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 25 14:21:26 node-4 kernel: [    0.426016] ACPI: Added _OSI(Processor Aggregator Device)
Jul 25 14:21:26 node-4 kernel: [    0.438627] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 25 14:21:26 node-4 kernel: [    0.449339] ACPI: Interpreter enabled
Jul 25 14:21:26 node-4 kernel: [    0.449344] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 25 14:21:26 node-4 kernel: [    0.449348] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 25 14:21:26 node-4 kernel: [    0.449351] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 25 14:21:26 node-4 kernel: [    0.449358] ACPI: (supports S0 S4 S5)
Jul 25 14:21:26 node-4 kernel: [    0.449359] ACPI: Using IOAPIC for interrupt routing
Jul 25 14:21:26 node-4 kernel: [    0.449402] HEST: Table parsing has been initialized.
Jul 25 14:21:26 node-4 kernel: [    0.449404] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 25 14:21:26 node-4 kernel: [    0.449956] ACPI: No dock devices found.
Jul 25 14:21:26 node-4 kernel: [    0.461459] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 25 14:21:26 node-4 kernel: [    0.461464] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 14:21:26 node-4 kernel: [    0.461468] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 25 14:21:26 node-4 kernel: [    0.461494] PCI host bridge to bus 0000:ff
Jul 25 14:21:26 node-4 kernel: [    0.461496] pci_bus 0000:ff: root bus resource [bus ff]
Jul 25 14:21:26 node-4 kernel: [    0.461504] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.461542] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 25 14:21:26 node-4 kernel: [    0.461573] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.461608] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.461637] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 25 14:21:26 node-4 kernel: [    0.461666] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 25 14:21:26 node-4 kernel: [    0.461697] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.461725] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.461756] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.461783] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.461810] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.461837] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.461865] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.461892] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.461918] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.461947] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.461979] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462007] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462034] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 25 14:21:26 node-4 kernel: [    0.462062] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462088] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 25 14:21:26 node-4 kernel: [    0.462114] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462140] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462171] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 25 14:21:26 node-4 kernel: [    0.462206] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462237] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462267] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462298] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462329] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462361] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462392] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462422] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462453] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462488] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462522] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462553] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462585] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462614] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462642] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462675] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462711] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462749] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462783] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462816] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462847] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462877] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462907] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462938] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.462973] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463005] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463037] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463067] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463097] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463127] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463157] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463189] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463223] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463280] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 25 14:21:26 node-4 kernel: [    0.463283] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 14:21:26 node-4 kernel: [    0.463285] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 25 14:21:26 node-4 kernel: [    0.463303] PCI host bridge to bus 0000:7f
Jul 25 14:21:26 node-4 kernel: [    0.463305] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 25 14:21:26 node-4 kernel: [    0.463310] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463338] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 25 14:21:26 node-4 kernel: [    0.463365] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463393] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463418] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 25 14:21:26 node-4 kernel: [    0.463443] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 25 14:21:26 node-4 kernel: [    0.463470] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463497] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463519] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463542] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463566] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463591] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463617] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463641] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463666] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463691] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463713] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463736] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463759] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 25 14:21:26 node-4 kernel: [    0.463782] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463804] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 25 14:21:26 node-4 kernel: [    0.463826] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463849] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463877] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 25 14:21:26 node-4 kernel: [    0.463911] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463937] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463963] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.463989] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464014] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464040] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464066] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464094] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464118] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464147] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464175] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464203] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464233] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464259] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464286] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464316] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464341] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464368] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464396] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464427] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464451] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464476] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464503] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464531] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464557] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464584] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464611] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464637] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464659] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464684] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464710] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464738] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.464764] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.466007] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 25 14:21:26 node-4 kernel: [    0.466010] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 14:21:26 node-4 kernel: [    0.467135] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 25 14:21:26 node-4 kernel: [    0.467648] PCI host bridge to bus 0000:00
Jul 25 14:21:26 node-4 kernel: [    0.467650] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 25 14:21:26 node-4 kernel: [    0.467652] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 25 14:21:26 node-4 kernel: [    0.467653] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 25 14:21:26 node-4 kernel: [    0.467655] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 25 14:21:26 node-4 kernel: [    0.467656] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 25 14:21:26 node-4 kernel: [    0.467657] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 25 14:21:26 node-4 kernel: [    0.467659] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 25 14:21:26 node-4 kernel: [    0.467664] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 25 14:21:26 node-4 kernel: [    0.467746] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 25 14:21:26 node-4 kernel: [    0.467777] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:26 node-4 kernel: [    0.467818] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 25 14:21:26 node-4 kernel: [    0.467837] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 25 14:21:26 node-4 kernel: [    0.467866] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:26 node-4 kernel: [    0.467906] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 25 14:21:26 node-4 kernel: [    0.467925] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 25 14:21:26 node-4 kernel: [    0.467954] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:26 node-4 kernel: [    0.467996] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 25 14:21:26 node-4 kernel: [    0.468013] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.468083] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.468158] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.468232] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 25 14:21:26 node-4 kernel: [    0.468237] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 25 14:21:26 node-4 kernel: [    0.468321] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 25 14:21:26 node-4 kernel: [    0.468469] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 25 14:21:26 node-4 kernel: [    0.468486] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 25 14:21:26 node-4 kernel: [    0.468564] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:26 node-4 kernel: [    0.468617] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 25 14:21:26 node-4 kernel: [    0.468638] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 25 14:21:26 node-4 kernel: [    0.468694] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:26 node-4 kernel: [    0.468737] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 25 14:21:26 node-4 kernel: [    0.468764] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 25 14:21:26 node-4 kernel: [    0.468820] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 25 14:21:26 node-4 kernel: [    0.468862] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 25 14:21:26 node-4 kernel: [    0.468886] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 25 14:21:26 node-4 kernel: [    0.468904] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 25 14:21:26 node-4 kernel: [    0.468982] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:26 node-4 kernel: [    0.469031] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 25 14:21:26 node-4 kernel: [    0.469058] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 25 14:21:26 node-4 kernel: [    0.469306] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 25 14:21:26 node-4 kernel: [    0.469312] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 25 14:21:26 node-4 kernel: [    0.469318] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 25 14:21:26 node-4 kernel: [    0.469324] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 25 14:21:26 node-4 kernel: [    0.469331] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 25 14:21:26 node-4 kernel: [    0.469362] pci 0000:01:00.0: supports D1 D2
Jul 25 14:21:26 node-4 kernel: [    0.475437] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 25 14:21:26 node-4 kernel: [    0.475443] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 25 14:21:26 node-4 kernel: [    0.475447] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 25 14:21:26 node-4 kernel: [    0.475597] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 25 14:21:26 node-4 kernel: [    0.475630] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 25 14:21:26 node-4 kernel: [    0.483433] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 25 14:21:26 node-4 kernel: [    0.483439] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:26 node-4 kernel: [    0.483443] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 14:21:26 node-4 kernel: [    0.483527] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 25 14:21:26 node-4 kernel: [    0.483604] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 25 14:21:26 node-4 kernel: [    0.483698] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:26 node-4 kernel: [    0.483784] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 25 14:21:26 node-4 kernel: [    0.483787] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:26 node-4 kernel: [    0.483789] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 14:21:26 node-4 kernel: [    0.483847] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 25 14:21:26 node-4 kernel: [    0.483969] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:26 node-4 kernel: [    0.484023] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 25 14:21:26 node-4 kernel: [    0.484026] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:26 node-4 kernel: [    0.484028] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 14:21:26 node-4 kernel: [    0.484077] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 25 14:21:26 node-4 kernel: [    0.484199] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:26 node-4 kernel: [    0.484241] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 25 14:21:26 node-4 kernel: [    0.484360] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:26 node-4 kernel: [    0.484397] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 25 14:21:26 node-4 kernel: [    0.484516] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:26 node-4 kernel: [    0.484552] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 25 14:21:26 node-4 kernel: [    0.484673] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 25 14:21:26 node-4 kernel: [    0.484715] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 25 14:21:26 node-4 kernel: [    0.484717] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:26 node-4 kernel: [    0.484719] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 14:21:26 node-4 kernel: [    0.484778] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 25 14:21:26 node-4 kernel: [    0.484849] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 25 14:21:26 node-4 kernel: [    0.484900] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 25 14:21:26 node-4 kernel: [    0.484941] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 25 14:21:26 node-4 kernel: [    0.485020] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 25 14:21:26 node-4 kernel: [    0.485128] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 25 14:21:26 node-4 kernel: [    0.485130] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:26 node-4 kernel: [    0.485132] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 25 14:21:26 node-4 kernel: [    0.485188] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 25 14:21:26 node-4 kernel: [    0.485242] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 25 14:21:26 node-4 kernel: [    0.485291] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 25 14:21:26 node-4 kernel: [    0.485502] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 25 14:21:26 node-4 kernel: [    0.485506] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 25 14:21:26 node-4 kernel: [    0.485569] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 25 14:21:26 node-4 kernel: [    0.485624] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 25 14:21:26 node-4 kernel: [    0.485672] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 25 14:21:26 node-4 kernel: [    0.485907] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 25 14:21:26 node-4 kernel: [    0.485910] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 25 14:21:26 node-4 kernel: [    0.485969] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 25 14:21:26 node-4 kernel: [    0.486030] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 25 14:21:26 node-4 kernel: [    0.486083] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 25 14:21:26 node-4 kernel: [    0.486308] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 25 14:21:26 node-4 kernel: [    0.486311] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 25 14:21:26 node-4 kernel: [    0.486485] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 25 14:21:26 node-4 kernel: [    0.486523] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 25 14:21:26 node-4 kernel: [    0.486599] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 25 14:21:26 node-4 kernel: [    0.486617] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 25 14:21:26 node-4 kernel: [    0.486631] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 25 14:21:26 node-4 kernel: [    0.486644] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 25 14:21:26 node-4 kernel: [    0.486694] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 25 14:21:26 node-4 kernel: [    0.491439] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 25 14:21:26 node-4 kernel: [    0.491457] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 25 14:21:26 node-4 kernel: [    0.491489] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 25 14:21:26 node-4 kernel: [    0.491977] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 25 14:21:26 node-4 kernel: [    0.491980] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 14:21:26 node-4 kernel: [    0.492104] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 25 14:21:26 node-4 kernel: [    0.492211] PCI host bridge to bus 0000:80
Jul 25 14:21:26 node-4 kernel: [    0.492213] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 25 14:21:26 node-4 kernel: [    0.492214] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 25 14:21:26 node-4 kernel: [    0.492216] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 25 14:21:26 node-4 kernel: [    0.492224] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.492289] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.492357] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 25 14:21:26 node-4 kernel: [    0.492419] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 25 14:21:26 node-4 kernel: [    0.492424] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 25 14:21:26 node-4 kernel: [    0.492496] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 25 14:21:26 node-4 kernel: [    0.492795] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 25 14:21:26 node-4 kernel: [    0.492827] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 25 14:21:26 node-4 kernel: [    0.492856] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 25 14:21:26 node-4 kernel: [    0.492885] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 25 14:21:26 node-4 kernel: [    0.492914] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 14:21:26 node-4 kernel: [    0.492944] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 14:21:26 node-4 kernel: [    0.492974] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 14:21:26 node-4 kernel: [    0.493003] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 14:21:26 node-4 kernel: [    0.493088] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 25 14:21:26 node-4 kernel: [    0.493092] ACPI: \_SB_.UNC1: notify handler is installed
Jul 25 14:21:26 node-4 kernel: [    0.493093] ACPI: \_SB_.UNC0: notify handler is installed
Jul 25 14:21:26 node-4 kernel: [    0.493108] ACPI: \_SB_.PCI0: notify handler is installed
Jul 25 14:21:26 node-4 kernel: [    0.493161] ACPI: \_SB_.PCI1: notify handler is installed
Jul 25 14:21:26 node-4 kernel: [    0.493240] Found 4 acpi root devices
Jul 25 14:21:26 node-4 kernel: [    0.493347] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 25 14:21:26 node-4 kernel: [    0.493349] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 25 14:21:26 node-4 kernel: [    0.493350] vgaarb: loaded
Jul 25 14:21:26 node-4 kernel: [    0.493351] vgaarb: bridge control possible 0000:0c:00.0
Jul 25 14:21:26 node-4 kernel: [    0.493467] SCSI subsystem initialized
Jul 25 14:21:26 node-4 kernel: [    0.493531] libata version 3.00 loaded.
Jul 25 14:21:26 node-4 kernel: [    0.493546] ACPI: bus type USB registered
Jul 25 14:21:26 node-4 kernel: [    0.493556] usbcore: registered new interface driver usbfs
Jul 25 14:21:26 node-4 kernel: [    0.493561] usbcore: registered new interface driver hub
Jul 25 14:21:26 node-4 kernel: [    0.493585] usbcore: registered new device driver usb
Jul 25 14:21:26 node-4 kernel: [    0.493756] PCI: Using ACPI for IRQ routing
Jul 25 14:21:26 node-4 kernel: [    0.497367] PCI: pci_cache_line_size set to 64 bytes
Jul 25 14:21:26 node-4 kernel: [    0.497576] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 25 14:21:26 node-4 kernel: [    0.497577] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 25 14:21:26 node-4 kernel: [    0.497578] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 25 14:21:26 node-4 kernel: [    0.497645] NetLabel: Initializing
Jul 25 14:21:26 node-4 kernel: [    0.497646] NetLabel:  domain hash size = 128
Jul 25 14:21:26 node-4 kernel: [    0.497647] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 25 14:21:26 node-4 kernel: [    0.497657] NetLabel:  unlabeled traffic allowed by default
Jul 25 14:21:26 node-4 kernel: [    0.497725] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 25 14:21:26 node-4 kernel: [    0.497729] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 25 14:21:26 node-4 kernel: [    0.499785] Switched to clocksource hpet
Jul 25 14:21:26 node-4 kernel: [    0.503661] AppArmor: AppArmor Filesystem Enabled
Jul 25 14:21:26 node-4 kernel: [    0.503674] pnp: PnP ACPI init
Jul 25 14:21:26 node-4 kernel: [    0.503681] ACPI: bus type PNP registered
Jul 25 14:21:26 node-4 kernel: [    0.503801] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 25 14:21:26 node-4 kernel: [    0.503810] pnp 00:01: [dma 4]
Jul 25 14:21:26 node-4 kernel: [    0.503821] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 25 14:21:26 node-4 kernel: [    0.503847] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 25 14:21:26 node-4 kernel: [    0.503867] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 25 14:21:26 node-4 kernel: [    0.503885] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 25 14:21:26 node-4 kernel: [    0.503917] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 25 14:21:26 node-4 kernel: [    0.503970] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 25 14:21:26 node-4 kernel: [    0.503972] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 25 14:21:26 node-4 kernel: [    0.503973] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 25 14:21:26 node-4 kernel: [    0.503975] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 25 14:21:26 node-4 kernel: [    0.503977] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 25 14:21:26 node-4 kernel: [    0.503981] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 25 14:21:26 node-4 kernel: [    0.503984] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 25 14:21:26 node-4 kernel: [    0.503985] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 25 14:21:26 node-4 kernel: [    0.503987] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 25 14:21:26 node-4 kernel: [    0.503988] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 25 14:21:26 node-4 kernel: [    0.503990] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 25 14:21:26 node-4 kernel: [    0.503991] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 25 14:21:26 node-4 kernel: [    0.503993] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 25 14:21:26 node-4 kernel: [    0.503995] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 25 14:21:26 node-4 kernel: [    0.504078] pnp 00:07: [dma 0 disabled]
Jul 25 14:21:26 node-4 kernel: [    0.504106] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 25 14:21:26 node-4 kernel: [    0.504179] pnp 00:08: [dma 0 disabled]
Jul 25 14:21:26 node-4 kernel: [    0.504212] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 25 14:21:26 node-4 kernel: [    0.504262] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 25 14:21:26 node-4 kernel: [    0.504608] pnp: PnP ACPI: found 10 devices
Jul 25 14:21:26 node-4 kernel: [    0.504610] ACPI: bus type PNP unregistered
Jul 25 14:21:26 node-4 kernel: [    0.510965] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 25 14:21:26 node-4 kernel: [    0.510968] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 25 14:21:26 node-4 kernel: [    0.510971] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 25 14:21:26 node-4 kernel: [    0.510975] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 25 14:21:26 node-4 kernel: [    0.510977] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:26 node-4 kernel: [    0.510992] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 25 14:21:26 node-4 kernel: [    0.511021] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 25 14:21:26 node-4 kernel: [    0.511035] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 25 14:21:26 node-4 kernel: [    0.511064] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 25 14:21:26 node-4 kernel: [    0.511079] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 25 14:21:26 node-4 kernel: [    0.511108] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 25 14:21:26 node-4 kernel: [    0.511122] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 25 14:21:26 node-4 kernel: [    0.511151] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 25 14:21:26 node-4 kernel: [    0.511153] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:26 node-4 kernel: [    0.511171] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 14:21:26 node-4 kernel: [    0.511200] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 25 14:21:26 node-4 kernel: [    0.511202] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:26 node-4 kernel: [    0.511216] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 14:21:26 node-4 kernel: [    0.511245] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 25 14:21:26 node-4 kernel: [    0.511247] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:26 node-4 kernel: [    0.511249] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 14:21:26 node-4 kernel: [    0.511254] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 25 14:21:26 node-4 kernel: [    0.511255] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 25 14:21:26 node-4 kernel: [    0.511258] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 14:21:26 node-4 kernel: [    0.511261] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 25 14:21:26 node-4 kernel: [    0.511266] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 25 14:21:26 node-4 kernel: [    0.511274] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 25 14:21:26 node-4 kernel: [    0.511278] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 25 14:21:26 node-4 kernel: [    0.511284] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 25 14:21:26 node-4 kernel: [    0.511285] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 25 14:21:26 node-4 kernel: [    0.511286] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 25 14:21:26 node-4 kernel: [    0.511287] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 25 14:21:26 node-4 kernel: [    0.511287] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 25 14:21:26 node-4 kernel: [    0.511288] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 25 14:21:26 node-4 kernel: [    0.511289] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 25 14:21:26 node-4 kernel: [    0.511290] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 25 14:21:26 node-4 kernel: [    0.511291] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 25 14:21:26 node-4 kernel: [    0.511292] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 25 14:21:26 node-4 kernel: [    0.511293] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 25 14:21:26 node-4 kernel: [    0.511294] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 25 14:21:26 node-4 kernel: [    0.511294] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 25 14:21:26 node-4 kernel: [    0.511295] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 25 14:21:26 node-4 kernel: [    0.511296] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 25 14:21:26 node-4 kernel: [    0.511297] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 25 14:21:26 node-4 kernel: [    0.511298] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 25 14:21:26 node-4 kernel: [    0.511299] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 25 14:21:26 node-4 kernel: [    0.511300] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 25 14:21:26 node-4 kernel: [    0.511301] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 25 14:21:26 node-4 kernel: [    0.511302] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 25 14:21:26 node-4 kernel: [    0.511303] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 25 14:21:26 node-4 kernel: [    0.511305] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 25 14:21:26 node-4 kernel: [    0.511306] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 25 14:21:26 node-4 kernel: [    0.511344] NET: Registered protocol family 2
Jul 25 14:21:26 node-4 kernel: [    0.511599] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 25 14:21:26 node-4 kernel: [    0.511935] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 25 14:21:26 node-4 kernel: [    0.512079] TCP: Hash tables configured (established 262144 bind 65536)
Jul 25 14:21:26 node-4 kernel: [    0.512123] TCP: reno registered
Jul 25 14:21:26 node-4 kernel: [    0.512152] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 25 14:21:26 node-4 kernel: [    0.512247] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 25 14:21:26 node-4 kernel: [    0.512398] NET: Registered protocol family 1
Jul 25 14:21:26 node-4 kernel: [    0.547883] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 25 14:21:26 node-4 kernel: [    0.547897] PCI: CLS 64 bytes, default 64
Jul 25 14:21:26 node-4 kernel: [    0.547971] Trying to unpack rootfs image as initramfs...
Jul 25 14:21:26 node-4 kernel: [    0.767457] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 25 14:21:26 node-4 kernel: [    0.767500] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 25 14:21:26 node-4 kernel: [    0.767504] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 25 14:21:26 node-4 kernel: [    0.767929] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:26 node-4 kernel: [    0.767935] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:26 node-4 kernel: [    0.767939] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:26 node-4 kernel: [    0.767945] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:26 node-4 kernel: [    0.767970] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:26 node-4 kernel: [    0.767981] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:26 node-4 kernel: [    0.767990] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:26 node-4 kernel: [    0.767999] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:26 node-4 kernel: [    0.768007] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:26 node-4 kernel: [    0.768016] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:26 node-4 kernel: [    0.768022] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:26 node-4 kernel: [    0.768028] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:26 node-4 kernel: [    0.768035] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:26 node-4 kernel: [    0.768042] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:26 node-4 kernel: [    0.768050] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:26 node-4 kernel: [    0.768058] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 14:21:26 node-4 kernel: [    0.768135] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 25 14:21:26 node-4 kernel: [    0.768138] Scanning for low memory corruption every 60 seconds
Jul 25 14:21:26 node-4 kernel: [    0.768513] Initialise system trusted keyring
Jul 25 14:21:26 node-4 kernel: [    0.768565] audit: initializing netlink socket (disabled)
Jul 25 14:21:26 node-4 kernel: [    0.768581] type=2000 audit(1469456449.724:1): initialized
Jul 25 14:21:26 node-4 kernel: [    0.786492] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 25 14:21:26 node-4 kernel: [    0.788027] zbud: loaded
Jul 25 14:21:26 node-4 kernel: [    0.788154] VFS: Disk quotas dquot_6.5.2
Jul 25 14:21:26 node-4 kernel: [    0.788189] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 25 14:21:26 node-4 kernel: [    0.788554] fuse init (API version 7.22)
Jul 25 14:21:26 node-4 kernel: [    0.788615] msgmni has been set to 32768
Jul 25 14:21:26 node-4 kernel: [    0.788666] Key type big_key registered
Jul 25 14:21:26 node-4 kernel: [    0.789233] Key type asymmetric registered
Jul 25 14:21:26 node-4 kernel: [    0.789235] Asymmetric key parser 'x509' registered
Jul 25 14:21:26 node-4 kernel: [    0.789257] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 25 14:21:26 node-4 kernel: [    0.789328] io scheduler noop registered
Jul 25 14:21:26 node-4 kernel: [    0.789330] io scheduler deadline registered (default)
Jul 25 14:21:26 node-4 kernel: [    0.789350] io scheduler cfq registered
Jul 25 14:21:26 node-4 kernel: [    0.789859] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    0.790068] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    0.790180] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    0.790285] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    0.790394] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    0.790488] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    0.790871] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 25 14:21:26 node-4 kernel: [    0.790896] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 25 14:21:26 node-4 kernel: [    0.790912] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 25 14:21:26 node-4 kernel: [    0.790921] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790924] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790927] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 25 14:21:26 node-4 kernel: [    0.790932] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790933] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790934] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790936] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790938] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790939] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790940] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790942] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790943] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790944] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790946] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790947] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790950] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 25 14:21:26 node-4 kernel: [    0.790962] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790964] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 25 14:21:26 node-4 kernel: [    0.790978] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790982] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 25 14:21:26 node-4 kernel: [    0.790992] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790994] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 25 14:21:26 node-4 kernel: [    0.790997] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 25 14:21:26 node-4 kernel: [    0.791034] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 25 14:21:26 node-4 kernel: [    0.791041] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 25 14:21:26 node-4 kernel: [    0.791045] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 25 14:21:26 node-4 kernel: [    0.791054] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 25 14:21:26 node-4 kernel: [    0.791095] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 25 14:21:26 node-4 kernel: [    0.791096] vesafb: scrolling: redraw
Jul 25 14:21:26 node-4 kernel: [    0.791097] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 25 14:21:26 node-4 kernel: [    0.811922] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 25 14:21:26 node-4 kernel: [    0.820554] Console: switching to colour frame buffer device 80x30
Jul 25 14:21:26 node-4 kernel: [    0.829336] fb0: VESA VGA frame buffer device
Jul 25 14:21:26 node-4 kernel: [    0.829535] intel_idle: MWAIT substates: 0x2120
Jul 25 14:21:26 node-4 kernel: [    0.829536] intel_idle: v0.4 model 0x3F
Jul 25 14:21:26 node-4 kernel: [    0.829537] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 25 14:21:26 node-4 kernel: [    0.829766] ipmi message handler version 39.2
Jul 25 14:21:26 node-4 kernel: [    0.830048] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 25 14:21:26 node-4 kernel: [    0.830490] ACPI: AC Adapter [P111] (on-line)
Jul 25 14:21:26 node-4 kernel: [    0.835823] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 25 14:21:26 node-4 kernel: [    0.846822] ACPI: Power Button [PWRB]
Jul 25 14:21:26 node-4 kernel: [    0.852588] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 25 14:21:26 node-4 kernel: [    0.864234] ACPI: Power Button [PWRF]
Jul 25 14:21:26 node-4 kernel: [    0.881278] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 25 14:21:26 node-4 kernel: [    0.892923] pstore: Registered erst as persistent store backend
Jul 25 14:21:26 node-4 kernel: [    0.899093] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 25 14:21:26 node-4 kernel: [    0.911028] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 25 14:21:26 node-4 kernel: [    0.937762] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 25 14:21:26 node-4 kernel: [    0.971017] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 25 14:21:26 node-4 kernel: [    0.985022] Linux agpgart interface v0.103
Jul 25 14:21:26 node-4 kernel: [    0.992683] brd: module loaded
Jul 25 14:21:26 node-4 kernel: [    0.999722] loop: module loaded
Jul 25 14:21:26 node-4 kernel: [    1.006431] libphy: Fixed MDIO Bus: probed
Jul 25 14:21:26 node-4 kernel: [    1.012899] tun: Universal TUN/TAP device driver, 1.6
Jul 25 14:21:26 node-4 kernel: [    1.019370] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 25 14:21:26 node-4 kernel: [    1.025892] PPP generic driver version 2.4.2
Jul 25 14:21:26 node-4 kernel: [    1.032270] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 25 14:21:26 node-4 kernel: [    1.038710] ehci-pci: EHCI PCI platform driver
Jul 25 14:21:26 node-4 kernel: [    1.045214] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 25 14:21:26 node-4 kernel: [    1.051631] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 25 14:21:26 node-4 kernel: [    1.064133] ehci-pci 0000:00:1a.0: debug port 2
Jul 25 14:21:26 node-4 kernel: [    1.074338] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 25 14:21:26 node-4 kernel: [    1.074357] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 25 14:21:26 node-4 kernel: [    1.091287] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 25 14:21:26 node-4 kernel: [    1.097353] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 25 14:21:26 node-4 kernel: [    1.103506] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 25 14:21:26 node-4 kernel: [    1.115392] usb usb1: Product: EHCI Host Controller
Jul 25 14:21:26 node-4 kernel: [    1.121505] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 25 14:21:26 node-4 kernel: [    1.127649] usb usb1: SerialNumber: 0000:00:1a.0
Jul 25 14:21:26 node-4 kernel: [    1.133599] hub 1-0:1.0: USB hub found
Jul 25 14:21:26 node-4 kernel: [    1.139355] hub 1-0:1.0: 2 ports detected
Jul 25 14:21:26 node-4 kernel: [    1.145128] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 25 14:21:26 node-4 kernel: [    1.150707] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 25 14:21:26 node-4 kernel: [    1.161643] ehci-pci 0000:00:1d.0: debug port 2
Jul 25 14:21:26 node-4 kernel: [    1.170965] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 25 14:21:26 node-4 kernel: [    1.170968] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 25 14:21:26 node-4 kernel: [    1.187206] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 25 14:21:26 node-4 kernel: [    1.192434] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 25 14:21:26 node-4 kernel: [    1.197756] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 25 14:21:26 node-4 kernel: [    1.208408] usb usb2: Product: EHCI Host Controller
Jul 25 14:21:26 node-4 kernel: [    1.213941] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 25 14:21:26 node-4 kernel: [    1.219562] usb usb2: SerialNumber: 0000:00:1d.0
Jul 25 14:21:26 node-4 kernel: [    1.225159] hub 2-0:1.0: USB hub found
Jul 25 14:21:26 node-4 kernel: [    1.230579] hub 2-0:1.0: 2 ports detected
Jul 25 14:21:26 node-4 kernel: [    1.235913] ehci-platform: EHCI generic platform driver
Jul 25 14:21:26 node-4 kernel: [    1.241183] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 25 14:21:26 node-4 kernel: [    1.246496] ohci-pci: OHCI PCI platform driver
Jul 25 14:21:26 node-4 kernel: [    1.251788] ohci-platform: OHCI generic platform driver
Jul 25 14:21:26 node-4 kernel: [    1.256986] uhci_hcd: USB Universal Host Controller Interface driver
Jul 25 14:21:26 node-4 kernel: [    1.262330] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 25 14:21:26 node-4 kernel: [    1.462969] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 25 14:21:26 node-4 kernel: [    1.766725] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 25 14:21:26 node-4 kernel: [    1.782997] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 25 14:21:26 node-4 kernel: [    1.788608] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 25 14:21:26 node-4 kernel: [    1.794389] hub 1-1:1.0: USB hub found
Jul 25 14:21:26 node-4 kernel: [    1.799984] hub 1-1:1.0: 6 ports detected
Jul 25 14:21:26 node-4 kernel: [    1.914609] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 25 14:21:26 node-4 kernel: [    2.301050] i8042: No controller found
Jul 25 14:21:26 node-4 kernel: [    2.306608] mousedev: PS/2 mouse device common for all mice
Jul 25 14:21:26 node-4 kernel: [    2.312331] rtc_cmos 00:02: RTC can wake from S4
Jul 25 14:21:26 node-4 kernel: [    2.315115] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 25 14:21:26 node-4 kernel: [    2.315116] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 25 14:21:26 node-4 kernel: [    2.315757] hub 2-1:1.0: USB hub found
Jul 25 14:21:26 node-4 kernel: [    2.315988] hub 2-1:1.0: 8 ports detected
Jul 25 14:21:26 node-4 kernel: [    2.340778] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 25 14:21:26 node-4 kernel: [    2.346543] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 25 14:21:26 node-4 kernel: [    2.357891] device-mapper: uevent: version 1.0.3
Jul 25 14:21:26 node-4 kernel: [    2.363651] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 25 14:21:26 node-4 kernel: [    2.375134] ledtrig-cpu: registered to indicate activity on CPUs
Jul 25 14:21:26 node-4 kernel: [    2.381148] TCP: cubic registered
Jul 25 14:21:26 node-4 kernel: [    2.387070] NET: Registered protocol family 10
Jul 25 14:21:26 node-4 kernel: [    2.393169] NET: Registered protocol family 17
Jul 25 14:21:26 node-4 kernel: [    2.399012] Key type dns_resolver registered
Jul 25 14:21:26 node-4 kernel: [    2.405134] Loading compiled-in X.509 certificates
Jul 25 14:21:26 node-4 kernel: [    2.411363] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 25 14:21:26 node-4 kernel: [    2.423026] registered taskstats version 1
Jul 25 14:21:26 node-4 kernel: [    2.431127] Key type trusted registered
Jul 25 14:21:26 node-4 kernel: [    2.438760] Key type encrypted registered
Jul 25 14:21:26 node-4 kernel: [    2.444252] AppArmor: AppArmor sha1 policy hashing enabled
Jul 25 14:21:26 node-4 kernel: [    2.449760] IMA: No TPM chip found, activating TPM-bypass!
Jul 25 14:21:26 node-4 kernel: [    2.455820] regulator-dummy: disabling
Jul 25 14:21:26 node-4 kernel: [    2.461307]   Magic number: 8:640:334
Jul 25 14:21:26 node-4 kernel: [    2.466788] tty tty55: hash matches
Jul 25 14:21:26 node-4 kernel: [    2.472317] memory memory184: hash matches
Jul 25 14:21:26 node-4 kernel: [    2.477689] rtc_cmos 00:02: setting system clock to 2016-07-25 14:20:52 UTC (1469456452)
Jul 25 14:21:26 node-4 kernel: [    2.489917] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 25 14:21:26 node-4 kernel: [    2.495419] EDD information not available.
Jul 25 14:21:26 node-4 kernel: [    2.500903] PM: Hibernation image not present or could not be loaded.
Jul 25 14:21:26 node-4 kernel: [    2.501764] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 25 14:21:26 node-4 kernel: [    2.512932] Write protecting the kernel read-only data: 12288k
Jul 25 14:21:26 node-4 kernel: [    2.519192] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 25 14:21:26 node-4 kernel: [    2.531815] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 25 14:21:26 node-4 kernel: [    2.563737] device-mapper: multipath: version 1.6.0 loaded
Jul 25 14:21:26 node-4 kernel: [    2.571410] systemd-udevd[217]: starting version 204
Jul 25 14:21:26 node-4 kernel: [    2.590037] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 25 14:21:26 node-4 kernel: [    2.598973] md: linear personality registered for level -1
Jul 25 14:21:26 node-4 kernel: [    2.612858] md: multipath personality registered for level -4
Jul 25 14:21:26 node-4 kernel: [    2.621177] md: raid0 personality registered for level 0
Jul 25 14:21:26 node-4 kernel: [    2.629236] md: raid1 personality registered for level 1
Jul 25 14:21:26 node-4 kernel: [    2.640868] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 25 14:21:26 node-4 kernel: [    2.647028] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 25 14:21:26 node-4 kernel: [    2.653201] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 25 14:21:26 node-4 kernel: [    2.655188] megasas: FW now in Ready state
Jul 25 14:21:26 node-4 kernel: [    2.655731] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.655817] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.655924] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.656025] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.656193] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.656250] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.656332] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.656498] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.656607] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.656765] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.656887] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.657015] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.657201] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.657336] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.657487] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.657604] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.658558] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 25 14:21:26 node-4 kernel: [    2.686098] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 25 14:21:26 node-4 kernel: [    2.699210] 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 25 14:21:26 node-4 kernel: [    2.702116] raid6: sse2x1    2163 MB/s
Jul 25 14:21:26 node-4 kernel: [    2.719690] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 14:21:26 node-4 kernel: [    2.726592] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.726598] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.726603] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.726607] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.726657] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 14:21:26 node-4 kernel: [    2.734667] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 25 14:21:26 node-4 kernel: [    2.734668] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 25 14:21:26 node-4 kernel: [    2.734673] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 25 14:21:26 node-4 kernel: [    2.734682] usb 2-1.4: Manufacturer: Avocent
Jul 25 14:21:26 node-4 kernel: [    2.734704] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 25 14:21:26 node-4 kernel: [    2.770200] raid6: sse2x2     822 MB/s
Jul 25 14:21:26 node-4 kernel: [    2.837829] raid6: sse2x4    8620 MB/s
Jul 25 14:21:26 node-4 kernel: [    2.909754] raid6: avx2x1   14926 MB/s
Jul 25 14:21:26 node-4 kernel: [    2.981693] raid6: avx2x2   18916 MB/s
Jul 25 14:21:26 node-4 kernel: [    3.053634] raid6: avx2x4   21286 MB/s
Jul 25 14:21:26 node-4 kernel: [    3.059193] raid6: using algorithm avx2x4 (21286 MB/s)
Jul 25 14:21:26 node-4 kernel: [    3.064685] raid6: using avx2x2 recovery algorithm
Jul 25 14:21:26 node-4 kernel: [    3.070083] Switched to clocksource tsc
Jul 25 14:21:26 node-4 kernel: [    3.070089] megasas:IOC Init cmd success
Jul 25 14:21:26 node-4 kernel: [    3.081792] xor: automatically using best checksumming function:
Jul 25 14:21:26 node-4 kernel: [    3.082018] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 25 14:21:26 node-4 kernel: [    3.082030] 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 25 14:21:26 node-4 kernel: [    3.082031] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 14:21:26 node-4 kernel: [    3.082544] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    3.082656] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    3.082761] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    3.082897] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    3.083296] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 14:21:26 node-4 kernel: [    3.093944] megasas: INIT adapter done
Jul 25 14:21:26 node-4 kernel: [    3.102458] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 25 14:21:26 node-4 kernel: [    3.102465] 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 25 14:21:26 node-4 kernel: [    3.102466] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 14:21:26 node-4 kernel: [    3.102950] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    3.103098] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    3.103196] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    3.103270] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    3.103586] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 14:21:26 node-4 kernel: [    3.122205] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 25 14:21:26 node-4 kernel: [    3.122215] 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 25 14:21:26 node-4 kernel: [    3.122216] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 14:21:26 node-4 kernel: [    3.122570] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    3.122617] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    3.122730] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    3.122894] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 25 14:21:26 node-4 kernel: [    3.123163] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 14:21:26 node-4 kernel: [    3.165751] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 25 14:21:26 node-4 kernel: [    3.167342] scsi0 : LSI SAS based MegaRAID driver
Jul 25 14:21:26 node-4 kernel: [    3.175632] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 25 14:21:26 node-4 kernel: [    3.235770] hidraw: raw HID events driver (C) Jiri Kosina
Jul 25 14:21:26 node-4 kernel: [    3.240621] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 25 14:21:26 node-4 kernel: [    3.244916] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 25 14:21:26 node-4 kernel: [    3.245090] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 25 14:21:26 node-4 kernel: [    3.245276] sd 0:2:0:0: [sda] Write Protect is off
Jul 25 14:21:26 node-4 kernel: [    3.245277] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 25 14:21:26 node-4 kernel: [    3.245351] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 25 14:21:26 node-4 kernel: [    3.273435]    avx       : 36028.000 MB/sec
Jul 25 14:21:26 node-4 kernel: [    3.275036]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 25 14:21:26 node-4 kernel: [    3.276770] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 25 14:21:26 node-4 kernel: [    3.315849] async_tx: api initialized (async)
Jul 25 14:21:26 node-4 kernel: [    3.323861] usbcore: registered new interface driver usbhid
Jul 25 14:21:26 node-4 kernel: [    3.330230] usbhid: USB HID core driver
Jul 25 14:21:26 node-4 kernel: [    3.337316] 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 25 14:21:26 node-4 kernel: [    3.350186] 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 25 14:21:26 node-4 kernel: [    3.350210] md: raid6 personality registered for level 6
Jul 25 14:21:26 node-4 kernel: [    3.350210] md: raid5 personality registered for level 5
Jul 25 14:21:26 node-4 kernel: [    3.350211] md: raid4 personality registered for level 4
Jul 25 14:21:26 node-4 kernel: [    3.382312] 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 25 14:21:26 node-4 kernel: [    3.394712] 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 25 14:21:26 node-4 kernel: [    3.407577] 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 25 14:21:26 node-4 kernel: [    3.420687] md: raid10 personality registered for level 10
Jul 25 14:21:26 node-4 kernel: [    3.421262] 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 25 14:21:26 node-4 kernel: [    3.450055] random: lvm urandom read with 29 bits of entropy available
Jul 25 14:21:26 node-4 kernel: [    3.502449] multipathd (369): /proc/369/oom_adj is deprecated, please use /proc/369/oom_score_adj instead.
Jul 25 14:21:26 node-4 kernel: [    3.597887] bio: create slab <bio-1> at 1
Jul 25 14:21:26 node-4 kernel: [    4.360847] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 25 14:21:26 node-4 kernel: [    4.891378] init: plymouth-upstart-bridge main process (553) terminated with status 1
Jul 25 14:21:26 node-4 kernel: [    4.905239] init: plymouth-upstart-bridge main process ended, respawning
Jul 25 14:21:26 node-4 kernel: [    5.043373] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 25 14:21:26 node-4 kernel: [    5.055321] random: nonblocking pool is initialized
Jul 25 14:21:26 node-4 kernel: [    5.063749] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 25 14:21:26 node-4 kernel: [    5.173152] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 25 14:21:26 node-4 kernel: [    5.245015] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 25 14:21:26 node-4 kernel: [    5.315365] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 25 14:21:26 node-4 kernel: [    5.521756] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 25 14:21:26 node-4 kernel: [    5.558330] XFS (dm-0): Mounting Filesystem
Jul 25 14:21:26 node-4 kernel: [    5.766790] XFS (dm-0): Ending clean mount
Jul 25 14:21:26 node-4 kernel: [    5.863789] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 25 14:21:26 node-4 kernel: [    5.908385] XFS (dm-1): Mounting Filesystem
Jul 25 14:21:26 node-4 kernel: [    5.969600] XFS (dm-1): Ending clean mount
Jul 25 14:21:26 node-4 kernel: [    7.878031] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 25 14:21:26 node-4 kernel: [    7.902651] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 25 14:21:26 node-4 kernel: [    8.024797] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 25 14:21:26 node-4 kernel: [    8.024802] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 25 14:21:26 node-4 kernel: [    8.024806] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 25 14:21:26 node-4 kernel: [    8.024810] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 25 14:21:26 node-4 kernel: [    8.062424] systemd-udevd[777]: starting version 204
Jul 25 14:21:26 node-4 kernel: [    8.306085] power_meter ACPI000D:00: Found ACPI power meter.
Jul 25 14:21:26 node-4 kernel: [    8.306139] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 25 14:21:26 node-4 kernel: [    8.314719] wmi: Mapper loaded
Jul 25 14:21:26 node-4 kernel: [    8.317263] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 25 14:21:26 node-4 kernel: [    8.317268] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 25 14:21:26 node-4 kernel: [    8.317271] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 25 14:21:26 node-4 kernel: [    8.317274] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 25 14:21:26 node-4 kernel: [    8.317315] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 25 14:21:26 node-4 kernel: [    8.328044] IPMI System Interface driver.
Jul 25 14:21:26 node-4 kernel: [    8.328090] ipmi_si: probing via ACPI
Jul 25 14:21:26 node-4 kernel: [    8.328109] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 25 14:21:26 node-4 kernel: [    8.328110] ipmi_si: Adding ACPI-specified kcs state machine
Jul 25 14:21:26 node-4 kernel: [    8.328135] ipmi_si: probing via SMBIOS
Jul 25 14:21:26 node-4 kernel: [    8.328136] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 25 14:21:26 node-4 kernel: [    8.328137] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 25 14:21:26 node-4 kernel: [    8.328139] ipmi_si: probing via SPMI
Jul 25 14:21:26 node-4 kernel: [    8.328140] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 25 14:21:26 node-4 kernel: [    8.328141] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 25 14:21:26 node-4 kernel: [    8.328143] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 25 14:21:26 node-4 kernel: [    8.356658] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 25 14:21:26 node-4 kernel: [    8.417592] systemd-udevd[796]: renamed network interface eth0 to enp6s0
Jul 25 14:21:26 node-4 kernel: [    8.445433] systemd-udevd[805]: renamed network interface eth1 to enp7s0
Jul 25 14:21:26 node-4 kernel: [    8.478607] systemd-udevd[823]: renamed network interface eth2 to enp8s0
Jul 25 14:21:26 node-4 kernel: [    8.497531] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 25 14:21:26 node-4 kernel: [    8.497537] ipmi_si 00:09: IPMI kcs interface initialized
Jul 25 14:21:26 node-4 kernel: [    8.509425] systemd-udevd[795]: renamed network interface eth3 to enp9s0
Jul 25 14:21:26 node-4 kernel: [    8.808927] type=1400 audit(1469456458.835:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1054 comm="apparmor_parser"
Jul 25 14:21:26 node-4 kernel: [    8.809096] type=1400 audit(1469456458.835:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1054 comm="apparmor_parser"
Jul 25 14:21:26 node-4 kernel: [    8.809224] type=1400 audit(1469456458.835:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1054 comm="apparmor_parser"
Jul 25 14:21:26 node-4 kernel: [    8.822369] type=1400 audit(1469456458.847:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1067 comm="apparmor_parser"
Jul 25 14:21:26 node-4 kernel: [    8.822516] type=1400 audit(1469456458.847:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1067 comm="apparmor_parser"
Jul 25 14:21:26 node-4 kernel: [    8.822637] type=1400 audit(1469456458.847:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1067 comm="apparmor_parser"
Jul 25 14:21:26 node-4 kernel: [    8.825946] type=1400 audit(1469456458.851:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1053 comm="apparmor_parser"
Jul 25 14:21:26 node-4 kernel: [    8.826094] type=1400 audit(1469456458.851:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1053 comm="apparmor_parser"
Jul 25 14:21:26 node-4 kernel: [    8.826220] type=1400 audit(1469456458.851:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1053 comm="apparmor_parser"
Jul 25 14:21:26 node-4 kernel: [    8.834824] type=1400 audit(1469456458.859:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1056 comm="apparmor_parser"
Jul 25 14:21:26 node-4 kernel: [    9.377903] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 25 14:21:26 node-4 kernel: [    9.386354] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 25 14:21:26 node-4 kernel: [    9.554650] enic 0000:06:00.0 enp6s0: Link UP
Jul 25 14:21:26 node-4 kernel: [    9.555670] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 25 14:21:26 node-4 kernel: [    9.555675] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 25 14:21:26 node-4 kernel: [   19.292734] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 25 14:21:27 node-4 failsafe: Failsafe of 120 seconds reached.
Jul 25 14:21:27 node-4 kernel: [   38.618151] init: failsafe main process (8401) killed by TERM signal
Jul 25 14:21:27 node-4 dbus[8438]: [system] AppArmor D-Bus mediation is enabled
Jul 25 14:21:28 node-4 kernel: [   38.845452] audit_printk_skb: 30 callbacks suppressed
Jul 25 14:21:28 node-4 kernel: [   38.845454] type=1400 audit(1469456488.059:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8527 comm="apparmor_parser"
Jul 25 14:21:28 node-4 kernel: [   38.845844] type=1400 audit(1469456488.059:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8526 comm="apparmor_parser"
Jul 25 14:21:28 node-4 kernel: [   38.845850] type=1400 audit(1469456488.059:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8526 comm="apparmor_parser"
Jul 25 14:21:28 node-4 kernel: [   38.845855] type=1400 audit(1469456488.059:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8526 comm="apparmor_parser"
Jul 25 14:21:28 node-4 kernel: [   38.846107] type=1400 audit(1469456488.059:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8526 comm="apparmor_parser"
Jul 25 14:21:28 node-4 kernel: [   38.846110] type=1400 audit(1469456488.059:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8526 comm="apparmor_parser"
Jul 25 14:21:28 node-4 kernel: [   38.846224] type=1400 audit(1469456488.059:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8526 comm="apparmor_parser"
Jul 25 14:21:28 node-4 kernel: [   38.920658] type=1400 audit(1469456488.135:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8529 comm="apparmor_parser"
Jul 25 14:21:28 node-4 anacron[8596]: Anacron 2.3 started on 2016-07-25
Jul 25 14:21:28 node-4 cron[8559]: (CRON) INFO (pidfile fd = 3)
Jul 25 14:21:28 node-4 cron[8603]: (CRON) STARTUP (fork ok)
Jul 25 14:21:28 node-4 anacron[8596]: Will run job `cron.daily' in 5 min.
Jul 25 14:21:28 node-4 anacron[8596]: Will run job `cron.weekly' in 10 min.
Jul 25 14:21:28 node-4 anacron[8596]: Will run job `cron.monthly' in 15 min.
Jul 25 14:21:28 node-4 anacron[8596]: Jobs will be executed sequentially
Jul 25 14:21:28 node-4 cron[8603]: (CRON) INFO (Running @reboot jobs)
Jul 25 14:21:28 node-4 multipathd: path checkers start up
Jul 25 14:21:28 node-4 postfix/master[8739]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 25 14:21:32 node-4 puppet-agent[9036]: Reopening log files
Jul 25 14:21:34 node-4 puppet-agent[9036]: Could not request certificate: Connection refused - connect(2)
Jul 25 14:21:47 node-4 puppet-user[9312]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 25 14:21:47 node-4 puppet-user[9312]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Jul 25 14:21:48 node-4 puppet-user[9312]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 25 14:21:48 node-4 puppet-user[9312]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 25 14:21:48 node-4 puppet-user[9312]: Finished catalog run in 0.74 seconds
Jul 25 14:21:49 node-4 multipathd: uevent trigger error
Jul 25 14:21:49 node-4 puppet-user[9742]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 25 14:21:49 node-4 puppet-user[9742]: Compiled catalog for node-4.domain.tld in environment production in 0.09 seconds
Jul 25 14:21:49 node-4 puppet-user[9742]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 25 14:21:49 node-4 puppet-user[9742]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 25 14:21:49 node-4 puppet-user[9742]: (/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 25 14:21:49 node-4 puppet-user[9742]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 25 14:21:49 node-4 puppet-user[9742]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 25 14:21:49 node-4 puppet-user[9742]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 25 14:21:49 node-4 puppet-user[9742]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 25 14:21:49 node-4 puppet-user[9742]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 25 14:21:49 node-4 puppet-user[9742]: Finished catalog run in 0.05 seconds
Jul 25 14:21:51 node-4 puppet-user[10199]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 25 14:21:51 node-4 puppet-user[10199]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Jul 25 14:21:51 node-4 puppet-user[10199]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 25 14:21:51 node-4 puppet-user[10199]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 25 14:21:51 node-4 puppet-user[10199]: Finished catalog run in 0.04 seconds
Jul 25 14:21:53 node-4 puppet-user[10662]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 25 14:21:53 node-4 puppet-user[10662]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 25 14:21:53 node-4 puppet-user[10662]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 25 14:21:53 node-4 puppet-user[10662]: Finished catalog run in 0.04 seconds
Jul 25 14:21:54 node-4 puppet-user[11114]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 25 14:21:54 node-4 puppet-user[11114]: Compiled catalog for node-4.domain.tld in environment production in 0.17 seconds
Jul 25 14:21:54 node-4 puppet-user[11114]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 25 14:21:55 node-4 puppet-user[11114]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Jul 25 14:21:55 node-4 puppet-user[11114]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Jul 25 14:21:55 node-4 puppet-user[11114]: Finished catalog run in 0.84 seconds
Jul 25 14:21:56 node-4 puppet-user[11616]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 25 14:21:57 node-4 puppet-user[11616]: Compiled catalog for node-4.domain.tld in environment production in 0.21 seconds
Jul 25 14:21:57 node-4 puppet-user[11616]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Jul 25 14:21:57 node-4 puppet-user[11616]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 25 14:21:57 node-4 puppet-user[11616]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 25 14:21:57 node-4 puppet-user[11616]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Jul 25 14:21:57 node-4 puppet-user[11616]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 25 14:21:57 node-4 puppet-user[11616]: Finished catalog run in 0.32 seconds
Jul 25 14:21:57 node-4 kernel: [   67.998841] init: plymouth-upstart-bridge main process ended, respawning
Jul 25 14:21:57 node-4 puppet-agent[9036]: Could not run: SIGTERM
Jul 25 14:21:57 node-4 kernel: [   68.270738] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 25 14:21:58 node-4 ec2: 
Jul 25 14:21:58 node-4 ec2: #############################################################
Jul 25 14:21:58 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 25 14:21:58 node-4 ec2: 1024 e0:50:bf:74:27:ac:44:4a:f5:6f:82:a4:10:2a:a2:b7  root@node-4.domain.tld (DSA)
Jul 25 14:21:58 node-4 ec2: 256 bd:67:ee:cd:42:0b:b5:0a:85:ab:d5:f4:76:6f:d6:2c  root@node-4.domain.tld (ECDSA)
Jul 25 14:21:58 node-4 ec2: 256 48:f8:4f:af:a1:c4:1a:b8:e1:d1:03:48:53:ce:c3:ce  root@node-4.domain.tld (ED25519)
Jul 25 14:21:58 node-4 ec2: 2048 b3:09:14:bc:7e:a8:8e:d1:b8:0c:9c:76:0e:85:40:61  root@node-4.domain.tld (RSA)
Jul 25 14:21:58 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 25 14:21:58 node-4 ec2: #############################################################
Jul 25 14:21:59 node-4 puppet-user[12263]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 25 14:21:59 node-4 puppet-user[12263]: Compiled catalog for node-4.domain.tld in environment production in 0.19 seconds
Jul 25 14:21:59 node-4 puppet-user[12263]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 25 14:21:59 node-4 kernel: [   69.825165] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 25 14:21:59 node-4 kernel: [   69.825218] 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 25 14:21:59 node-4 puppet-user[12263]: (/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 25 14:21:59 node-4 puppet-user[12263]: Finished catalog run in 0.05 seconds
Jul 25 14:22:01 node-4 puppet-user[12721]: (Scope(Class[main])) MODULAR: sync_time
Jul 25 14:22:01 node-4 puppet-user[12721]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Jul 25 14:22:01 node-4 ntpdate[13146]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 25 14:22:01 node-4 CRON[13158]: (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 25 14:22:03 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 14:22:03 node-4 nailgun-agent: I, [2016-07-25T14:22:03.977865 #13161]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 25 14:22:07 node-4 ntpdate[13146]: adjust time server 10.20.0.2 offset 0.001425 sec
Jul 25 14:22:07 node-4 puppet-user[12721]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 25 14:22:07 node-4 puppet-user[12721]: Finished catalog run in 6.20 seconds
Jul 25 14:22:16 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 14:22:16 node-4 nailgun-agent: I, [2016-07-25T14:22:16.679440 #13161]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 25 14:22:55 node-4 puppet-user[13657]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 25 14:22:55 node-4 puppet-user[13657]: Compiled catalog for node-4.domain.tld in environment production in 0.11 seconds
Jul 25 14:22:55 node-4 puppet-user[13657]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 25 14:22:55 node-4 puppet-user[13657]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Jul 25 14:22:55 node-4 puppet-user[13657]: Finished catalog run in 0.09 seconds
Jul 25 14:22:57 node-4 puppet-user[14105]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 25 14:22:58 node-4 puppet-user[14105]: Compiled catalog for node-4.domain.tld in environment production in 1.27 seconds
Jul 25 14:22:58 node-4 puppet-user[14105]: (/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 25 14:22:58 node-4 puppet-user[14105]: (/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 25 14:22:58 node-4 puppet-user[14105]: (/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 25 14:22:58 node-4 puppet-user[14105]: (/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 25 14:22:58 node-4 puppet-user[14105]: (/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 25 14:22:58 node-4 puppet-user[14105]: (/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 25 14:22:58 node-4 puppet-user[14105]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 25 14:22:58 node-4 puppet-user[14105]: (/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 25 14:22:58 node-4 puppet-user[14105]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 25 14:22:58 node-4 puppet-user[14105]: (/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 25 14:22:58 node-4 puppet-user[14105]: (/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 25 14:22:58 node-4 puppet-user[14105]: (/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 25 14:22:58 node-4 puppet-user[14105]: (/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 25 14:22:58 node-4 puppet-user[14105]: (/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 25 14:22:59 node-4 puppet-user[14105]: (/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 25 14:22:59 node-4 puppet-user[14105]: (/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 25 14:23:01 node-4 CRON[14645]: (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 25 14:23:11 node-4 puppet-user[14105]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 25 14:23:12 node-4 puppet-user[14105]: Finished catalog run in 13.44 seconds
Jul 25 14:23:14 node-4 puppet-user[14929]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 25 14:23:14 node-4 puppet-user[14929]: Compiled catalog for node-4.domain.tld in environment production in 0.15 seconds
Jul 25 14:23:15 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 14:23:15 node-4 nailgun-agent: I, [2016-07-25T14:23:15.858295 #14648]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 25 14:23:19 node-4 puppet-user[14929]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 25 14:23:29 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 14:23:29 node-4 nailgun-agent: I, [2016-07-25T14:23:29.255509 #14648]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 25 14:23:50 node-4 puppet-user[14929]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 25 14:23:50 node-4 puppet-user[14929]: Finished catalog run in 35.70 seconds
Jul 25 14:23:51 node-4 puppet-user[17682]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 25 14:23:52 node-4 puppet-user[17682]: Compiled catalog for node-4.domain.tld in environment production in 0.59 seconds
Jul 25 14:23:52 node-4 puppet-user[17682]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 25 14:23:52 node-4 puppet-user[17682]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 25 14:23:52 node-4 puppet-user[17682]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 25 14:23:52 node-4 puppet-user[17682]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 25 14:23:52 node-4 puppet-user[17682]: Finished catalog run in 0.09 seconds
Jul 25 14:23:54 node-4 puppet-user[18136]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 25 14:23:55 node-4 puppet-user[18136]: Compiled catalog for node-4.domain.tld in environment production in 0.85 seconds
Jul 25 14:23:55 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 25 14:23:55 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 25 14:23:55 node-4 crontab[18572]: (root) LIST (root)
Jul 25 14:23:55 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 25 14:23:55 node-4 crontab[18573]: (root) REPLACE (root)
Jul 25 14:23:57 node-4 puppet-user[18136]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/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 25 14:23:59 node-4 puppet-user[18136]: (/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 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/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 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/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 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/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 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/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 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 25 14:23:59 node-4 puppet-user[18136]: (/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 25 14:23:59 node-4 puppet-user[18136]: (/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 25 14:23:59 node-4 puppet-user[18136]: (/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 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 25 14:23:59 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 25 14:24:00 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 25 14:24:00 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 25 14:24:00 node-4 puppet-user[18136]: (/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 25 14:24:00 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 25 14:24:00 node-4 puppet-user[18136]: (/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 25 14:24:00 node-4 puppet-user[18136]: (/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 25 14:24:00 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 25 14:24:00 node-4 puppet-user[18136]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 25 14:24:00 node-4 puppet-user[18136]: (/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 25 14:24:00 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8374" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 14:24:00 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 25 14:24:02 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:02 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:02 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:02 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:02 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:23 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:23 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:23 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:23 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:23 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:26 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:26 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:26 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:26 node-4 multipathd: uevent trigger error
<27>Jul 25 14:24:26 node-4 multipathd: uevent trigger error
<27>Jul 25 14:25:26 node-4 ntpdate[29857]: no servers can be used, exiting
<27>Jul 25 14:25:26 node-4 ntpdate[30157]: no servers can be used, exiting
<27>Jul 25 14:25:57 node-4 multipathd: uevent trigger error
<27>Jul 25 14:25:57 node-4 multipathd: uevent trigger error
<27>Jul 25 14:25:57 node-4 multipathd: uevent trigger error
<27>Jul 25 14:25:57 node-4 multipathd: uevent trigger error
<27>Jul 25 14:25:57 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:00 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:00 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:00 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:00 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:00 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:12 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:12 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:12 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:12 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:12 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:15 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:15 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:15 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:15 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:15 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:58 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:58 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:58 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:58 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:58 node-4 multipathd: uevent trigger error
<27>Jul 25 14:26:58 node-4 multipathd: uevent trigger error
<27>Jul 25 14:27:05 node-4 multipathd: uevent trigger error
<27>Jul 25 14:27:05 node-4 multipathd: uevent trigger error
<27>Jul 25 14:27:05 node-4 multipathd: uevent trigger error
<27>Jul 25 14:27:05 node-4 multipathd: uevent trigger error
<27>Jul 25 14:27:05 node-4 multipathd: uevent trigger error
<43>Jul 25 14:27:20 node-4 apache2_error [Mon Jul 25 14:27:17.814241 2016] [mpm_event:notice] [pid 13452:tid 140442907297664] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 25 14:27:20 node-4 apache2_error [Mon Jul 25 14:27:17.814299 2016] [core:notice] [pid 13452:tid 140442907297664] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 25 14:27:20 node-4 apache2_error [Mon Jul 25 14:27:19.732952 2016] [mpm_event:notice] [pid 13452:tid 140442907297664] AH00491: caught SIGTERM, shutting down
<27>Jul 25 14:27:24 node-4 multipathd: uevent trigger error
<27>Jul 25 14:27:24 node-4 multipathd: uevent trigger error
<27>Jul 25 14:27:24 node-4 multipathd: uevent trigger error
<27>Jul 25 14:27:24 node-4 multipathd: uevent trigger error
<27>Jul 25 14:27:24 node-4 multipathd: uevent trigger error
<43>Jul 25 14:27:30 node-4 apache2_error [Mon Jul 25 14:27:20.796297 2016] [mpm_worker:notice] [pid 13851:tid 140133620840320] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 25 14:27:30 node-4 apache2_error [Mon Jul 25 14:27:20.796333 2016] [core:notice] [pid 13851:tid 140133620840320] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 25 14:28:00 node-4 apache2_error [Mon Jul 25 14:27:58.097345 2016] [mpm_worker:notice] [pid 13851:tid 140133620840320] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 14:28:00 node-4 apache2_error [Mon Jul 25 14:27:58.104186 2016] [mpm_worker:warn] [pid 13851:tid 140133620840320] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 14:28:00 node-4 apache2_error [Mon Jul 25 14:27:58.104966 2016] [mpm_worker:notice] [pid 13851:tid 140133620840320] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 25 14:28:00 node-4 apache2_error [Mon Jul 25 14:27:58.104978 2016] [core:notice] [pid 13851:tid 140133620840320] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 14:28:01 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:01 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:01 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:01 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:01 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:01 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:36 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 25 14:28:39 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:39 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:39 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:39 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:39 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:43 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:43 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:43 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:43 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:43 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:49 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:49 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:49 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:49 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:49 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:49 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:57 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:57 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:57 node-4 multipathd: uevent trigger error
<27>Jul 25 14:28:57 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:03 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:03 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:03 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:03 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:03 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:03 node-4 multipathd: uevent trigger error
<129>Jul 25 14:29:06 node-4 haproxy[28240]: 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 25 14:29:08 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:08 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:08 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:08 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:11 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:11 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:11 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:11 node-4 multipathd: uevent trigger error
<129>Jul 25 14:29:14 node-4 haproxy[30470]: 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 25 14:29:15 node-4 haproxy[30470]: 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 25 14:29:16 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:16 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:16 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:16 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:16 node-4 multipathd: uevent trigger error
<129>Jul 25 14:29:19 node-4 haproxy[31826]: 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 25 14:29:19 node-4 haproxy[31826]: 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 25 14:29:20 node-4 haproxy[31830]: 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 25 14:29:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:21 node-4 multipathd: uevent trigger error
<129>Jul 25 14:29:24 node-4 haproxy[582]: 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 25 14:29:25 node-4 haproxy[586]: 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 25 14:29:25 node-4 haproxy[586]: 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 25 14:29:25 node-4 haproxy[586]: 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 25 14:29:26 node-4 haproxy[586]: 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 25 14:29:27 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:27 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:27 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:27 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:27 node-4 multipathd: uevent trigger error
<129>Jul 25 14:29:29 node-4 haproxy[1803]: 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 25 14:29:30 node-4 haproxy[1807]: 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 25 14:29:30 node-4 haproxy[1807]: 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 25 14:29:30 node-4 haproxy[1807]: 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 25 14:29:31 node-4 haproxy[1807]: 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 25 14:29:31 node-4 haproxy[1807]: 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 25 14:29:32 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:32 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:32 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:32 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:32 node-4 multipathd: uevent trigger error
<129>Jul 25 14:29:33 node-4 haproxy[1807]: 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 25 14:29:33 node-4 haproxy[1807]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:33 node-4 haproxy[1807]: proxy aodh has no server available!
<129>Jul 25 14:29:35 node-4 haproxy[2985]: 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 25 14:29:35 node-4 haproxy[2985]: 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 25 14:29:35 node-4 haproxy[2985]: 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 25 14:29:36 node-4 haproxy[2991]: 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 25 14:29:36 node-4 haproxy[2991]: 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 25 14:29:36 node-4 haproxy[2991]: 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 25 14:29:36 node-4 haproxy[2991]: 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 25 14:29:38 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:38 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:38 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:38 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:38 node-4 multipathd: uevent trigger error
<129>Jul 25 14:29:38 node-4 haproxy[2991]: 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 25 14:29:38 node-4 haproxy[2991]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:38 node-4 haproxy[2991]: proxy aodh has no server available!
<129>Jul 25 14:29:38 node-4 haproxy[2991]: 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 25 14:29:38 node-4 haproxy[2991]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:38 node-4 haproxy[2991]: proxy ceilometer has no server available!
<129>Jul 25 14:29:40 node-4 haproxy[4152]: 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 25 14:29:40 node-4 haproxy[4152]: 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 25 14:29:41 node-4 haproxy[4156]: 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 25 14:29:41 node-4 haproxy[4156]: 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 25 14:29:41 node-4 haproxy[4156]: 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 25 14:29:41 node-4 haproxy[4156]: 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 25 14:29:42 node-4 haproxy[4156]: 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 25 14:29:43 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:43 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:43 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:43 node-4 multipathd: uevent trigger error
<129>Jul 25 14:29:43 node-4 haproxy[4156]: 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 25 14:29:43 node-4 haproxy[4156]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:43 node-4 haproxy[4156]: proxy aodh has no server available!
<129>Jul 25 14:29:43 node-4 haproxy[4156]: 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 25 14:29:43 node-4 haproxy[4156]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:43 node-4 haproxy[4156]: proxy ceilometer has no server available!
<129>Jul 25 14:29:45 node-4 haproxy[5368]: 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 25 14:29:46 node-4 haproxy[5372]: 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 25 14:29:46 node-4 haproxy[5372]: 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 25 14:29:46 node-4 haproxy[5372]: 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 25 14:29:46 node-4 haproxy[5372]: 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 25 14:29:47 node-4 haproxy[5372]: 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 25 14:29:47 node-4 haproxy[5372]: 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 25 14:29:47 node-4 haproxy[5372]: 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 25 14:29:47 node-4 haproxy[5372]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 25 14:29:48 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:48 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:48 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:48 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:48 node-4 multipathd: uevent trigger error
<129>Jul 25 14:29:48 node-4 haproxy[5372]: 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 25 14:29:49 node-4 haproxy[5372]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:49 node-4 haproxy[5372]: proxy aodh has no server available!
<129>Jul 25 14:29:49 node-4 haproxy[5372]: 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 25 14:29:49 node-4 haproxy[5372]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:49 node-4 haproxy[5372]: proxy ceilometer has no server available!
<129>Jul 25 14:29:51 node-4 haproxy[6629]: 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 25 14:29:51 node-4 haproxy[6629]: 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 25 14:29:51 node-4 haproxy[6629]: 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 25 14:29:52 node-4 haproxy[6636]: 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 25 14:29:52 node-4 haproxy[6636]: 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 25 14:29:52 node-4 haproxy[6636]: 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 25 14:29:52 node-4 haproxy[6636]: 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 25 14:29:52 node-4 haproxy[6636]: 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 25 14:29:52 node-4 haproxy[6636]: 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 25 14:29:53 node-4 haproxy[6636]: 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 25 14:29:53 node-4 haproxy[6636]: 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 25 14:29:53 node-4 haproxy[6636]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 25 14:29:54 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:54 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:54 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:54 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:54 node-4 multipathd: uevent trigger error
<129>Jul 25 14:29:54 node-4 haproxy[6636]: 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 25 14:29:54 node-4 haproxy[6636]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:54 node-4 haproxy[6636]: proxy glance-registry has no server available!
<27>Jul 25 14:29:54 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Jul 25 14:29:54 node-4 haproxy[6636]: 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 25 14:29:54 node-4 haproxy[6636]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:54 node-4 haproxy[6636]: proxy aodh has no server available!
<129>Jul 25 14:29:55 node-4 haproxy[6636]: 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 25 14:29:55 node-4 haproxy[6636]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:29:55 node-4 haproxy[6636]: proxy ceilometer has no server available!
<129>Jul 25 14:29:57 node-4 haproxy[7932]: 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 25 14:29:57 node-4 haproxy[7932]: 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 25 14:29:57 node-4 haproxy[7932]: 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 25 14:29:57 node-4 haproxy[7932]: 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 25 14:29:57 node-4 haproxy[7932]: 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 25 14:29:58 node-4 haproxy[7936]: 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 25 14:29:58 node-4 haproxy[7936]: 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 25 14:29:58 node-4 haproxy[7936]: 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 25 14:29:58 node-4 haproxy[7936]: 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 25 14:29:58 node-4 haproxy[7936]: 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 25 14:29:58 node-4 haproxy[7936]: 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 25 14:29:58 node-4 haproxy[7936]: 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 25 14:29:58 node-4 haproxy[7936]: 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 25 14:29:59 node-4 haproxy[7936]: 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 25 14:29:59 node-4 haproxy[7936]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 25 14:29:59 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:59 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:59 node-4 multipathd: uevent trigger error
<27>Jul 25 14:29:59 node-4 multipathd: uevent trigger error
<129>Jul 25 14:30:00 node-4 haproxy[7936]: 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 25 14:30:00 node-4 haproxy[7936]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:00 node-4 haproxy[7936]: proxy glance-registry has no server available!
<129>Jul 25 14:30:00 node-4 haproxy[7936]: 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 25 14:30:00 node-4 haproxy[7936]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:00 node-4 haproxy[7936]: proxy aodh has no server available!
<129>Jul 25 14:30:00 node-4 haproxy[7936]: 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 25 14:30:00 node-4 haproxy[7936]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:00 node-4 haproxy[7936]: proxy ceilometer has no server available!
<129>Jul 25 14:30:00 node-4 haproxy[7936]: 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 25 14:30:00 node-4 haproxy[7936]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:00 node-4 haproxy[7936]: proxy nova-novncproxy has no server available!
<129>Jul 25 14:30:02 node-4 haproxy[9178]: 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 25 14:30:02 node-4 haproxy[9178]: 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 25 14:30:02 node-4 haproxy[9178]: 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 25 14:30:02 node-4 haproxy[9178]: 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 25 14:30:03 node-4 haproxy[9185]: 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 25 14:30:03 node-4 haproxy[9185]: 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 25 14:30:03 node-4 haproxy[9185]: 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 25 14:30:03 node-4 haproxy[9185]: 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 25 14:30:03 node-4 haproxy[9185]: 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 25 14:30:03 node-4 haproxy[9185]: 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 25 14:30:03 node-4 haproxy[9185]: 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 25 14:30:03 node-4 haproxy[9185]: 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 25 14:30:04 node-4 haproxy[9185]: 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 25 14:30:04 node-4 haproxy[9185]: 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 25 14:30:04 node-4 haproxy[9185]: 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 25 14:30:04 node-4 haproxy[9185]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 25 14:30:04 node-4 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 14:30:05 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:05 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:05 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:05 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:05 node-4 multipathd: uevent trigger error
<129>Jul 25 14:30:05 node-4 haproxy[9185]: 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 25 14:30:05 node-4 haproxy[9185]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:05 node-4 haproxy[9185]: proxy glance-registry has no server available!
<129>Jul 25 14:30:05 node-4 haproxy[9185]: 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 25 14:30:05 node-4 haproxy[9185]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:05 node-4 haproxy[9185]: proxy aodh has no server available!
<129>Jul 25 14:30:06 node-4 haproxy[9185]: 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 25 14:30:06 node-4 haproxy[9185]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:06 node-4 haproxy[9185]: proxy ceilometer has no server available!
<129>Jul 25 14:30:06 node-4 haproxy[9185]: 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 25 14:30:06 node-4 haproxy[9185]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:06 node-4 haproxy[9185]: proxy nova-novncproxy has no server available!
<129>Jul 25 14:30:08 node-4 haproxy[10534]: 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 25 14:30:08 node-4 haproxy[10534]: 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 25 14:30:08 node-4 haproxy[10534]: 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 25 14:30:08 node-4 haproxy[10534]: 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 25 14:30:08 node-4 haproxy[10534]: 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 25 14:30:08 node-4 haproxy[10534]: 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 25 14:30:08 node-4 haproxy[10534]: 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 25 14:30:09 node-4 haproxy[10538]: 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 25 14:30:09 node-4 haproxy[10538]: 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 25 14:30:09 node-4 haproxy[10538]: 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 25 14:30:09 node-4 haproxy[10538]: 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 25 14:30:09 node-4 haproxy[10538]: 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 25 14:30:09 node-4 haproxy[10538]: 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 25 14:30:09 node-4 haproxy[10538]: 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 25 14:30:09 node-4 haproxy[10538]: 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 25 14:30:09 node-4 haproxy[10538]: 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 25 14:30:10 node-4 haproxy[10538]: 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 25 14:30:10 node-4 haproxy[10538]: 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 25 14:30:10 node-4 haproxy[10538]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 25 14:30:11 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:11 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:11 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:11 node-4 multipathd: uevent trigger error
<129>Jul 25 14:30:11 node-4 haproxy[10538]: 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 25 14:30:11 node-4 haproxy[10538]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:11 node-4 haproxy[10538]: proxy glance-registry has no server available!
<129>Jul 25 14:30:11 node-4 haproxy[10538]: 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 25 14:30:11 node-4 haproxy[10538]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:11 node-4 haproxy[10538]: proxy aodh has no server available!
<129>Jul 25 14:30:11 node-4 haproxy[10538]: 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 25 14:30:11 node-4 haproxy[10538]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:11 node-4 haproxy[10538]: proxy ceilometer has no server available!
<129>Jul 25 14:30:11 node-4 haproxy[10538]: 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 25 14:30:11 node-4 haproxy[10538]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:11 node-4 haproxy[10538]: proxy nova-novncproxy has no server available!
<27>Jul 25 14:30:14 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:14 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:14 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:14 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:14 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:17 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:17 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:17 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:17 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:17 node-4 multipathd: uevent trigger error
<129>Jul 25 14:30:18 node-4 haproxy[10538]: 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 25 14:30:18 node-4 haproxy[10538]: Server keystone-1/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:18 node-4 haproxy[10538]: proxy keystone-1 has no server available!
<129>Jul 25 14:30:18 node-4 haproxy[10538]: 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 25 14:30:18 node-4 haproxy[10538]: Server keystone-2/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:18 node-4 haproxy[10538]: proxy keystone-2 has no server available!
<129>Jul 25 14:30:18 node-4 haproxy[10538]: 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 25 14:30:18 node-4 haproxy[10538]: Server nova-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:18 node-4 haproxy[10538]: proxy nova-api has no server available!
<129>Jul 25 14:30:18 node-4 haproxy[10538]: Server nova-metadata-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 25 14:30:18 node-4 haproxy[10538]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:18 node-4 haproxy[10538]: proxy nova-metadata-api has no server available!
<129>Jul 25 14:30:18 node-4 haproxy[10538]: 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 25 14:30:18 node-4 haproxy[10538]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:18 node-4 haproxy[10538]: proxy cinder-api has no server available!
<129>Jul 25 14:30:18 node-4 haproxy[10538]: Server glance-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 25 14:30:18 node-4 haproxy[10538]: Server glance-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:18 node-4 haproxy[10538]: proxy glance-api has no server available!
<129>Jul 25 14:30:18 node-4 haproxy[10538]: 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 25 14:30:18 node-4 haproxy[10538]: Server glance-glare/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:18 node-4 haproxy[10538]: proxy glance-glare has no server available!
<129>Jul 25 14:30:18 node-4 haproxy[10538]: Server neutron/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 25 14:30:19 node-4 haproxy[10538]: Server neutron/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:19 node-4 haproxy[10538]: proxy neutron has no server available!
<129>Jul 25 14:30:19 node-4 haproxy[10538]: Server mysqld/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 14:30:19 node-4 haproxy[10538]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:19 node-4 haproxy[10538]: proxy mysqld has no server available!
<129>Jul 25 14:30:19 node-4 haproxy[10538]: 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 25 14:30:19 node-4 haproxy[10538]: Server object-storage/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:19 node-4 haproxy[10538]: proxy object-storage has no server available!
<129>Jul 25 14:30:19 node-4 haproxy[10538]: 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 25 14:30:19 node-4 haproxy[10538]: Server heat-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:19 node-4 haproxy[10538]: proxy heat-api has no server available!
<129>Jul 25 14:30:19 node-4 haproxy[10538]: Server heat-api-cfn/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 25 14:30:19 node-4 haproxy[10538]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:19 node-4 haproxy[10538]: proxy heat-api-cfn has no server available!
<129>Jul 25 14:30:19 node-4 haproxy[10538]: Server heat-api-cloudwatch/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 25 14:30:19 node-4 haproxy[10538]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 14:30:19 node-4 haproxy[10538]: proxy heat-api-cloudwatch has no server available!
<27>Jul 25 14:30:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:39 node-4 multipathd: uevent trigger error
<27>Jul 25 14:30:55 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 25 14:30:55 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 25 14:31:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:31:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:31:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:31:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:31:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:31:27 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 25 14:32:01 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 25 14:32:04 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 25 14:33:41 node-4 multipathd: uevent trigger error
<27>Jul 25 14:33:41 node-4 multipathd: uevent trigger error
<27>Jul 25 14:33:41 node-4 multipathd: uevent trigger error
<27>Jul 25 14:33:41 node-4 multipathd: uevent trigger error
<27>Jul 25 14:33:41 node-4 multipathd: uevent trigger error
<27>Jul 25 14:37:11 node-4 multipathd: uevent trigger error
<27>Jul 25 14:37:11 node-4 multipathd: uevent trigger error
<27>Jul 25 14:37:11 node-4 multipathd: uevent trigger error
<27>Jul 25 14:37:11 node-4 multipathd: uevent trigger error
<27>Jul 25 14:37:11 node-4 multipathd: uevent trigger error
<43>Jul 25 14:38:21 node-4 apache2_error [Mon Jul 25 14:38:20.279064 2016] [mpm_worker:notice] [pid 13851:tid 140133620840320] AH00295: caught SIGTERM, shutting down
<43>Jul 25 14:38:21 node-4 apache2_error [Mon Jul 25 14:38:21.030692 2016] [mpm_worker:notice] [pid 15286:tid 139781136459648] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 14:38:21 node-4 apache2_error [Mon Jul 25 14:38:21.030733 2016] [core:notice] [pid 15286:tid 139781136459648] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 14:38:58 node-4 multipathd: uevent trigger error
<27>Jul 25 14:38:58 node-4 multipathd: uevent trigger error
<27>Jul 25 14:38:58 node-4 multipathd: uevent trigger error
<27>Jul 25 14:38:58 node-4 multipathd: uevent trigger error
<27>Jul 25 14:38:58 node-4 multipathd: uevent trigger error
<43>Jul 25 14:39:01 node-4 apache2_error [Mon Jul 25 14:38:53.058495 2016] [mpm_worker:notice] [pid 15286:tid 139781136459648] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 14:39:01 node-4 apache2_error [Mon Jul 25 14:38:53.073169 2016] [mpm_worker:warn] [pid 15286:tid 139781136459648] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 14:39:01 node-4 apache2_error [Mon Jul 25 14:38:53.078540 2016] [mpm_worker:notice] [pid 15286:tid 139781136459648] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 14:39:01 node-4 apache2_error [Mon Jul 25 14:38:53.078563 2016] [core:notice] [pid 15286:tid 139781136459648] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 14:39:56 node-4 multipathd: uevent trigger error
<27>Jul 25 14:39:56 node-4 multipathd: uevent trigger error
<27>Jul 25 14:39:56 node-4 multipathd: uevent trigger error
<27>Jul 25 14:40:02 node-4 multipathd: uevent trigger error
<27>Jul 25 14:40:02 node-4 multipathd: uevent trigger error
<27>Jul 25 14:40:02 node-4 multipathd: uevent trigger error
<27>Jul 25 14:40:02 node-4 multipathd: uevent trigger error
<27>Jul 25 14:40:02 node-4 multipathd: uevent trigger error
<27>Jul 25 14:41:14 node-4 multipathd: uevent trigger error
<27>Jul 25 14:41:14 node-4 multipathd: uevent trigger error
<27>Jul 25 14:41:14 node-4 multipathd: uevent trigger error
<27>Jul 25 14:41:14 node-4 multipathd: uevent trigger error
<27>Jul 25 14:41:14 node-4 multipathd: uevent trigger error
<27>Jul 25 14:41:14 node-4 multipathd: uevent trigger error
<27>Jul 25 14:45:56 node-4 multipathd: uevent trigger error
<27>Jul 25 14:45:56 node-4 multipathd: uevent trigger error
<27>Jul 25 14:45:56 node-4 multipathd: uevent trigger error
<27>Jul 25 14:45:56 node-4 multipathd: uevent trigger error
<27>Jul 25 14:48:03 node-4 multipathd: uevent trigger error
<27>Jul 25 14:48:03 node-4 multipathd: uevent trigger error
<27>Jul 25 14:48:03 node-4 multipathd: uevent trigger error
<27>Jul 25 14:48:03 node-4 multipathd: uevent trigger error
<27>Jul 25 14:48:03 node-4 multipathd: uevent trigger error
<27>Jul 25 14:48:03 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:09 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:09 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:09 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:09 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:09 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:09 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:09 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:44 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:44 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:44 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:44 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:44 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:44 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:53 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:53 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:53 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:53 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:53 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:53 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:58 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:58 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:58 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:58 node-4 multipathd: uevent trigger error
<27>Jul 25 14:49:58 node-4 multipathd: uevent trigger error
<43>Jul 25 14:50:52 node-4 apache2_error [Mon Jul 25 14:50:49.379636 2016] [mpm_worker:notice] [pid 15286:tid 139781136459648] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 14:50:52 node-4 apache2_error [Mon Jul 25 14:50:49.765297 2016] [mpm_worker:warn] [pid 15286:tid 139781136459648] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 14:50:52 node-4 apache2_error [Mon Jul 25 14:50:49.770147 2016] [mpm_worker:notice] [pid 15286:tid 139781136459648] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 14:50:52 node-4 apache2_error [Mon Jul 25 14:50:49.770168 2016] [core:notice] [pid 15286:tid 139781136459648] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 14:51:30 node-4 multipathd: uevent trigger error
<27>Jul 25 14:51:30 node-4 multipathd: uevent trigger error
<27>Jul 25 14:51:30 node-4 multipathd: uevent trigger error
<27>Jul 25 14:51:30 node-4 multipathd: uevent trigger error
<27>Jul 25 14:51:30 node-4 multipathd: uevent trigger error
<43>Jul 25 14:51:32 node-4 apache2_error [Mon Jul 25 14:51:26.987869 2016] [mpm_worker:notice] [pid 15286:tid 139781136459648] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 14:51:32 node-4 apache2_error [Mon Jul 25 14:51:27.374867 2016] [mpm_worker:warn] [pid 15286:tid 139781136459648] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 14:51:32 node-4 apache2_error [Mon Jul 25 14:51:27.390976 2016] [mpm_worker:notice] [pid 15286:tid 139781136459648] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 14:51:32 node-4 apache2_error [Mon Jul 25 14:51:27.391020 2016] [core:notice] [pid 15286:tid 139781136459648] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 14:51:48 node-4 multipathd: uevent trigger error
<27>Jul 25 14:51:48 node-4 multipathd: uevent trigger error
<27>Jul 25 14:51:48 node-4 multipathd: uevent trigger error
<27>Jul 25 14:51:48 node-4 multipathd: uevent trigger error
<27>Jul 25 14:51:48 node-4 multipathd: uevent trigger error
<27>Jul 25 14:52:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:52:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:52:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:52:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:52:26 node-4 multipathd: uevent trigger error
<27>Jul 25 14:52:26 node-4 multipathd: uevent trigger error
<27>Jul 25 14:52:26 node-4 multipathd: uevent trigger error
<27>Jul 25 14:52:26 node-4 multipathd: uevent trigger error
<27>Jul 25 14:52:27 node-4 multipathd: uevent trigger error
<27>Jul 25 14:52:30 node-4 multipathd: uevent trigger error
<27>Jul 25 14:52:30 node-4 multipathd: uevent trigger error
<27>Jul 25 14:52:30 node-4 multipathd: uevent trigger error
<27>Jul 25 14:52:30 node-4 multipathd: uevent trigger error
<27>Jul 25 14:53:47 node-4 multipathd: uevent trigger error
<27>Jul 25 14:53:47 node-4 multipathd: uevent trigger error
<27>Jul 25 14:53:47 node-4 multipathd: uevent trigger error
<27>Jul 25 14:53:47 node-4 multipathd: uevent trigger error
<27>Jul 25 14:53:47 node-4 multipathd: uevent trigger error
<27>Jul 25 14:54:36 node-4 multipathd: uevent trigger error
<27>Jul 25 14:54:36 node-4 multipathd: uevent trigger error
<27>Jul 25 14:54:36 node-4 multipathd: uevent trigger error
<27>Jul 25 14:54:36 node-4 multipathd: uevent trigger error
<27>Jul 25 14:54:36 node-4 multipathd: uevent trigger error
<27>Jul 25 14:54:49 node-4 multipathd: uevent trigger error
<27>Jul 25 14:54:49 node-4 multipathd: uevent trigger error
<27>Jul 25 14:54:49 node-4 multipathd: uevent trigger error
<27>Jul 25 14:54:49 node-4 multipathd: uevent trigger error
<11>Jul 25 14:54:58 node-4 liberasurecode[10670]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:58 node-4 liberasurecode[10670]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:58 node-4 liberasurecode[10670]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:58 node-4 liberasurecode[10670]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:59 node-4 liberasurecode[10695]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:59 node-4 liberasurecode[10695]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:59 node-4 liberasurecode[10695]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:54:59 node-4 liberasurecode[10695]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:01 node-4 liberasurecode[11137]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:01 node-4 liberasurecode[11137]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:01 node-4 liberasurecode[11137]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:01 node-4 liberasurecode[11137]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:01 node-4 liberasurecode[11145]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:01 node-4 liberasurecode[11145]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:01 node-4 liberasurecode[11145]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:01 node-4 liberasurecode[11145]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<131>Jul 25 14:55:01 node-4 recon-cron: Exception during recon-cron while accessing devices: #012Traceback (most recent call last):#012  File "/usr/bin/swift-recon-cron", line 74, in main#012    asyncs = get_async_count(device_dir, logger)#012  File "/usr/bin/swift-recon-cron", line 31, in get_async_count#012    for i in os.listdir(device_dir):#012OSError: [Errno 2] No such file or directory: '/srv/node'
<11>Jul 25 14:55:07 node-4 liberasurecode[11769]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[11769]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[11769]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[11769]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[11805]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[11805]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[11805]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[11805]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[11848]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[11848]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[11848]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[11848]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[11963]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[11963]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[11963]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[11963]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[12022]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[12022]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[12022]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[12022]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[12047]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[12047]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[12047]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[12047]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[12078]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[12078]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[12078]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 14:55:07 node-4 liberasurecode[12078]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 25 14:55:13 node-4 multipathd: uevent trigger error
<27>Jul 25 14:55:13 node-4 multipathd: uevent trigger error
<27>Jul 25 14:55:13 node-4 multipathd: uevent trigger error
<27>Jul 25 14:55:13 node-4 multipathd: uevent trigger error
<27>Jul 25 14:55:13 node-4 multipathd: uevent trigger error
<27>Jul 25 14:55:18 node-4 multipathd: uevent trigger error
<27>Jul 25 14:55:18 node-4 multipathd: uevent trigger error
<27>Jul 25 14:55:18 node-4 multipathd: uevent trigger error
<27>Jul 25 14:55:18 node-4 multipathd: uevent trigger error
<27>Jul 25 14:55:18 node-4 multipathd: uevent trigger error
<27>Jul 25 14:56:19 node-4 multipathd: uevent trigger error
<27>Jul 25 14:56:19 node-4 multipathd: uevent trigger error
<27>Jul 25 14:56:20 node-4 multipathd: uevent trigger error
<27>Jul 25 14:56:20 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:26 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:26 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:26 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:26 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:26 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:39 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:39 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:39 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:39 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:52 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:52 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:52 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:52 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:56 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:56 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:56 node-4 multipathd: uevent trigger error
<27>Jul 25 14:58:56 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:09 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:09 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:09 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:09 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:09 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:13 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:13 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:13 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:13 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:13 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:17 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:17 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:17 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:17 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:17 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:21 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:22 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:22 node-4 multipathd: uevent trigger error
<27>Jul 25 14:59:22 node-4 multipathd: uevent trigger error
<11>Jul 25 15:00:01 node-4 liberasurecode[32619]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 15:00:01 node-4 liberasurecode[32619]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 15:00:01 node-4 liberasurecode[32619]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 15:00:01 node-4 liberasurecode[32619]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 25 15:00:03 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 15:00:03 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
