Jul 29 23:42:17 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8369" x-info="http://www.rsyslog.com"] start
Jul 29 23:42:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 29 23:42:17 node-4 rsyslogd: rsyslogd's groupid changed to 104
Jul 29 23:42:17 node-4 rsyslogd: rsyslogd's userid changed to 101
Jul 29 23:42:17 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 29 23:42:17 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 29 23:42:17 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 29 23:42:17 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 29 23:42:17 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=13289587-75fe-49ce-a1f6-f91e261f5227 nomdmonddf nomdmonisw
Jul 29 23:42:17 node-4 kernel: [    0.000000] KERNEL supported cpus:
Jul 29 23:42:17 node-4 kernel: [    0.000000]   Intel GenuineIntel
Jul 29 23:42:17 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Jul 29 23:42:17 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Jul 29 23:42:17 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 29 23:42:17 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 29 23:42:17 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 29 23:42:17 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 29 23:42:17 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 29 23:42:17 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 29 23:42:17 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 29 23:42:17 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 29 23:42:17 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 29 23:42:17 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 29 23:42:17 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 29 23:42:17 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 29 23:42:17 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 29 23:42:17 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 29 23:42:17 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 29 23:42:17 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 29 23:42:17 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 29 23:42:17 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 29 23:42:17 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 29 23:42:17 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 29 23:42:17 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 29 23:42:17 node-4 kernel: [    0.000000] No AGP bridge found
Jul 29 23:42:17 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 29 23:42:17 node-4 kernel: [    0.000000] MTRR default type: write-back
Jul 29 23:42:17 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 29 23:42:17 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Jul 29 23:42:17 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 29 23:42:17 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 29 23:42:17 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 29 23:42:17 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 29 23:42:17 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 29 23:42:17 node-4 kernel: [    0.000000]   2 disabled
Jul 29 23:42:17 node-4 kernel: [    0.000000]   3 disabled
Jul 29 23:42:17 node-4 kernel: [    0.000000]   4 disabled
Jul 29 23:42:17 node-4 kernel: [    0.000000]   5 disabled
Jul 29 23:42:17 node-4 kernel: [    0.000000]   6 disabled
Jul 29 23:42:17 node-4 kernel: [    0.000000]   7 disabled
Jul 29 23:42:17 node-4 kernel: [    0.000000]   8 disabled
Jul 29 23:42:17 node-4 kernel: [    0.000000]   9 disabled
Jul 29 23:42:17 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 29 23:42:17 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 29 23:42:17 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 29 23:42:17 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 29 23:42:17 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 29 23:42:17 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Jul 29 23:42:17 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 29 23:42:17 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 29 23:42:17 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 29 23:42:17 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 29 23:42:17 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 29 23:42:17 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 29 23:42:17 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 29 23:42:17 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 29 23:42:17 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 29 23:42:17 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 29 23:42:17 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 29 23:42:17 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 29 23:42:17 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 29 23:42:17 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 29 23:42:17 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 29 23:42:17 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 29 23:42:17 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 29 23:42:17 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 29 23:42:17 node-4 kernel: [    0.000000] Zone ranges:
Jul 29 23:42:17 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] Movable zone start for each node
Jul 29 23:42:17 node-4 kernel: [    0.000000] Early memory node ranges
Jul 29 23:42:17 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 29 23:42:17 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 29 23:42:17 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 29 23:42:17 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 29 23:42:17 node-4 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 29 23:42:17 node-4 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 29 23:42:17 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 29 23:42:17 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 29 23:42:17 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 29 23:42:17 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 29 23:42:17 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 29 23:42:17 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 29 23:42:17 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 29 23:42:17 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 29 23:42:17 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 29 23:42:17 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 29 23:42:17 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 29 23:42:17 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 29 23:42:17 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 29 23:42:17 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 29 23:42:17 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 29 23:42:17 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 29 23:42:17 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 29 23:42:17 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 29 23:42:17 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 29 23:42:17 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 29 23:42:17 node-4 kernel: [    0.000000] Policy zone: Normal
Jul 29 23:42:17 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=13289587-75fe-49ce-a1f6-f91e261f5227 nomdmonddf nomdmonisw
Jul 29 23:42:17 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 29 23:42:17 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 29 23:42:17 node-4 kernel: [    0.000000] Checking aperture...
Jul 29 23:42:17 node-4 kernel: [    0.000000] No AGP bridge found
Jul 29 23:42:17 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 29 23:42:17 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 29 23:42:17 node-4 kernel: [    0.000000] Memory: 32653312K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Jul 29 23:42:17 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 29 23:42:17 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 29 23:42:17 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 29 23:42:17 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 29 23:42:17 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 29 23:42:17 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 29 23:42:17 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 29 23:42:17 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 29 23:42:17 node-4 kernel: [    0.000000] console [tty0] enabled
Jul 29 23:42:17 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 29 23:42:17 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 29 23:42:17 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 29 23:42:17 node-4 kernel: [    0.000000] hpet clockevent registered
Jul 29 23:42:17 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 29 23:42:17 node-4 kernel: [    0.004000] tsc: Detected 3491.834 MHz processor
Jul 29 23:42:17 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.66 BogoMIPS (lpj=13967336)
Jul 29 23:42:17 node-4 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 29 23:42:17 node-4 kernel: [    0.000044] Security Framework initialized
Jul 29 23:42:17 node-4 kernel: [    0.000062] AppArmor: AppArmor initialized
Jul 29 23:42:17 node-4 kernel: [    0.000063] Yama: becoming mindful.
Jul 29 23:42:17 node-4 kernel: [    0.001456] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 29 23:42:17 node-4 kernel: [    0.006384] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 29 23:42:17 node-4 kernel: [    0.008315] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 29 23:42:17 node-4 kernel: [    0.008343] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 29 23:42:17 node-4 kernel: [    0.008634] Initializing cgroup subsys memory
Jul 29 23:42:17 node-4 kernel: [    0.008643] Initializing cgroup subsys devices
Jul 29 23:42:17 node-4 kernel: [    0.008644] Initializing cgroup subsys freezer
Jul 29 23:42:17 node-4 kernel: [    0.008646] Initializing cgroup subsys blkio
Jul 29 23:42:17 node-4 kernel: [    0.008648] Initializing cgroup subsys perf_event
Jul 29 23:42:17 node-4 kernel: [    0.008650] Initializing cgroup subsys hugetlb
Jul 29 23:42:17 node-4 kernel: [    0.008669] CPU: Physical Processor ID: 0
Jul 29 23:42:17 node-4 kernel: [    0.008671] CPU: Processor Core ID: 0
Jul 29 23:42:17 node-4 kernel: [    0.008674] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 29 23:42:17 node-4 kernel: [    0.008674] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 29 23:42:17 node-4 kernel: [    0.009369] mce: CPU supports 22 MCE banks
Jul 29 23:42:17 node-4 kernel: [    0.009396] CPU0: Thermal monitoring enabled (TM1)
Jul 29 23:42:17 node-4 kernel: [    0.009417] process: using mwait in idle threads
Jul 29 23:42:17 node-4 kernel: [    0.009420] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 29 23:42:17 node-4 kernel: [    0.009420] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 29 23:42:17 node-4 kernel: [    0.009420] tlb_flushall_shift: 6
Jul 29 23:42:17 node-4 kernel: [    0.009508] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 29 23:42:17 node-4 kernel: [    0.010229] ACPI: Core revision 20131115
Jul 29 23:42:17 node-4 kernel: [    0.022881] ACPI: All ACPI Tables successfully acquired
Jul 29 23:42:17 node-4 kernel: [    0.023053] ftrace: allocating 28617 entries in 112 pages
Jul 29 23:42:17 node-4 kernel: [    0.031852] dmar: Host address width 46
Jul 29 23:42:17 node-4 kernel: [    0.031854] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 29 23:42:17 node-4 kernel: [    0.031860] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 29 23:42:17 node-4 kernel: [    0.031862] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 29 23:42:17 node-4 kernel: [    0.031866] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 29 23:42:17 node-4 kernel: [    0.031868] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 29 23:42:17 node-4 kernel: [    0.031869] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 29 23:42:17 node-4 kernel: [    0.031870] dmar: ATSR flags: 0x0
Jul 29 23:42:17 node-4 kernel: [    0.031871] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 29 23:42:17 node-4 kernel: [    0.031872] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 29 23:42:17 node-4 kernel: [    0.031988] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 29 23:42:17 node-4 kernel: [    0.031989] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 29 23:42:17 node-4 kernel: [    0.031990] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 29 23:42:17 node-4 kernel: [    0.031991] HPET id 0 under DRHD base 0xc7ffc000
Jul 29 23:42:17 node-4 kernel: [    0.031992] Your BIOS is broken and requested that x2apic be disabled.
Jul 29 23:42:17 node-4 kernel: [    0.031992] This will slightly decrease performance.
Jul 29 23:42:17 node-4 kernel: [    0.031992] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 29 23:42:17 node-4 kernel: [    0.032425] Enabled IRQ remapping in xapic mode
Jul 29 23:42:17 node-4 kernel: [    0.032427] x2apic not enabled, IRQ remapping is in xapic mode
Jul 29 23:42:17 node-4 kernel: [    0.032430] Switched APIC routing to physical flat.
Jul 29 23:42:17 node-4 kernel: [    0.033055] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 29 23:42:17 node-4 kernel: [    0.072704] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 29 23:42:17 node-4 kernel: [    0.072709] TSC deadline timer enabled
Jul 29 23:42:17 node-4 kernel: [    0.072717] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 29 23:42:17 node-4 kernel: [    0.072723] ... version:                3
Jul 29 23:42:17 node-4 kernel: [    0.072724] ... bit width:              48
Jul 29 23:42:17 node-4 kernel: [    0.072724] ... generic registers:      4
Jul 29 23:42:17 node-4 kernel: [    0.072725] ... value mask:             0000ffffffffffff
Jul 29 23:42:17 node-4 kernel: [    0.072727] ... max period:             0000ffffffffffff
Jul 29 23:42:17 node-4 kernel: [    0.072727] ... fixed-purpose events:   3
Jul 29 23:42:17 node-4 kernel: [    0.072728] ... event mask:             000000070000000f
Jul 29 23:42:17 node-4 kernel: [    0.074152] x86: Booting SMP configuration:
Jul 29 23:42:17 node-4 kernel: [    0.088257] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 29 23:42:17 node-4 kernel: [    0.074154] .... node  #0, CPUs:        #1  #2  #3
Jul 29 23:42:17 node-4 kernel: [    0.116164] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 29 23:42:17 node-4 kernel: [    0.270311] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 29 23:42:17 node-4 kernel: [    0.325924] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 29 23:42:17 node-4 kernel: [    0.382972] x86: Booted up 2 nodes, 16 CPUs
Jul 29 23:42:17 node-4 kernel: [    0.382975] smpboot: Total of 16 processors activated (111751.16 BogoMIPS)
Jul 29 23:42:17 node-4 kernel: [    0.407151] devtmpfs: initialized
Jul 29 23:42:17 node-4 kernel: [    0.410494] EVM: security.selinux
Jul 29 23:42:17 node-4 kernel: [    0.410496] EVM: security.SMACK64
Jul 29 23:42:17 node-4 kernel: [    0.410497] EVM: security.ima
Jul 29 23:42:17 node-4 kernel: [    0.410498] EVM: security.capability
Jul 29 23:42:17 node-4 kernel: [    0.410548] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 29 23:42:17 node-4 kernel: [    0.411224] pinctrl core: initialized pinctrl subsystem
Jul 29 23:42:17 node-4 kernel: [    0.411286] regulator-dummy: no parameters
Jul 29 23:42:17 node-4 kernel: [    0.411318] RTC time: 23:41:42, date: 07/29/16
Jul 29 23:42:17 node-4 kernel: [    0.411353] NET: Registered protocol family 16
Jul 29 23:42:17 node-4 kernel: [    0.411437] cpuidle: using governor ladder
Jul 29 23:42:17 node-4 kernel: [    0.411438] cpuidle: using governor menu
Jul 29 23:42:17 node-4 kernel: [    0.411473] ACPI: bus type PCI registered
Jul 29 23:42:17 node-4 kernel: [    0.411475] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 29 23:42:17 node-4 kernel: [    0.411521] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 29 23:42:17 node-4 kernel: [    0.411523] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 29 23:42:17 node-4 kernel: [    0.425256] PCI: Using configuration type 1 for base access
Jul 29 23:42:17 node-4 kernel: [    0.426256] bio: create slab <bio-0> at 0
Jul 29 23:42:17 node-4 kernel: [    0.426524] ACPI: Added _OSI(Module Device)
Jul 29 23:42:17 node-4 kernel: [    0.426526] ACPI: Added _OSI(Processor Device)
Jul 29 23:42:17 node-4 kernel: [    0.426527] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 29 23:42:17 node-4 kernel: [    0.426528] ACPI: Added _OSI(Processor Aggregator Device)
Jul 29 23:42:17 node-4 kernel: [    0.439202] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 29 23:42:17 node-4 kernel: [    0.449793] ACPI: Interpreter enabled
Jul 29 23:42:17 node-4 kernel: [    0.449798] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 29 23:42:17 node-4 kernel: [    0.449802] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 29 23:42:17 node-4 kernel: [    0.449805] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 29 23:42:17 node-4 kernel: [    0.449811] ACPI: (supports S0 S4 S5)
Jul 29 23:42:17 node-4 kernel: [    0.449813] ACPI: Using IOAPIC for interrupt routing
Jul 29 23:42:17 node-4 kernel: [    0.449858] HEST: Table parsing has been initialized.
Jul 29 23:42:17 node-4 kernel: [    0.449861] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 29 23:42:17 node-4 kernel: [    0.450413] ACPI: No dock devices found.
Jul 29 23:42:17 node-4 kernel: [    0.461999] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 29 23:42:17 node-4 kernel: [    0.462004] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 23:42:17 node-4 kernel: [    0.462007] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 29 23:42:17 node-4 kernel: [    0.462033] PCI host bridge to bus 0000:ff
Jul 29 23:42:17 node-4 kernel: [    0.462035] pci_bus 0000:ff: root bus resource [bus ff]
Jul 29 23:42:17 node-4 kernel: [    0.462044] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 29 23:42:17 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 29 23:42:17 node-4 kernel: [    0.462082] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 29 23:42:17 node-4 kernel: [    0.462112] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462147] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462176] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 29 23:42:17 node-4 kernel: [    0.462206] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 29 23:42:17 node-4 kernel: [    0.462236] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462265] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462294] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462322] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462349] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462375] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462403] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462429] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462456] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462482] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462511] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462539] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462565] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 29 23:42:17 node-4 kernel: [    0.462593] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462619] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 29 23:42:17 node-4 kernel: [    0.462645] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462671] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462703] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 29 23:42:17 node-4 kernel: [    0.462738] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462769] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462799] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462830] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462861] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462892] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462924] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462956] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.462986] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463019] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463051] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463084] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463117] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463147] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463175] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463207] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463239] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463276] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463311] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463343] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463372] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463401] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463431] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463460] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463493] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463524] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463555] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463584] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463613] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463642] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463671] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463702] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463733] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463792] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 29 23:42:17 node-4 kernel: [    0.463795] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 23:42:17 node-4 kernel: [    0.463798] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 29 23:42:17 node-4 kernel: [    0.463815] PCI host bridge to bus 0000:7f
Jul 29 23:42:17 node-4 kernel: [    0.463817] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 29 23:42:17 node-4 kernel: [    0.463822] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463849] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 29 23:42:17 node-4 kernel: [    0.463877] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463906] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.463928] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 29 23:42:17 node-4 kernel: [    0.463952] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 29 23:42:17 node-4 kernel: [    0.463978] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464007] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464031] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464054] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464079] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464103] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464128] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464151] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464176] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464202] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464224] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464247] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464270] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 29 23:42:17 node-4 kernel: [    0.464294] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464316] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 29 23:42:17 node-4 kernel: [    0.464338] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464360] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464386] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 29 23:42:17 node-4 kernel: [    0.464421] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464447] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464475] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464502] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464527] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464553] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464578] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464606] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464630] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464658] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464685] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464713] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464741] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464766] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464791] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464819] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464844] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464872] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464901] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464929] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464955] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.464981] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.465006] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.465034] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.465060] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.465086] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.465115] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.465141] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.465164] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.465190] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.465214] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.465244] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.465271] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.466522] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 29 23:42:17 node-4 kernel: [    0.466525] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 23:42:17 node-4 kernel: [    0.467649] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 29 23:42:17 node-4 kernel: [    0.468158] PCI host bridge to bus 0000:00
Jul 29 23:42:17 node-4 kernel: [    0.468160] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 29 23:42:17 node-4 kernel: [    0.468162] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 29 23:42:17 node-4 kernel: [    0.468163] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 29 23:42:17 node-4 kernel: [    0.468165] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 29 23:42:17 node-4 kernel: [    0.468166] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 29 23:42:17 node-4 kernel: [    0.468167] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 29 23:42:17 node-4 kernel: [    0.468169] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 29 23:42:17 node-4 kernel: [    0.468175] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 29 23:42:17 node-4 kernel: [    0.468257] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 29 23:42:17 node-4 kernel: [    0.468287] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-4 kernel: [    0.468329] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 29 23:42:17 node-4 kernel: [    0.468348] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 29 23:42:17 node-4 kernel: [    0.468377] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-4 kernel: [    0.468417] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 29 23:42:17 node-4 kernel: [    0.468436] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 29 23:42:17 node-4 kernel: [    0.468465] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-4 kernel: [    0.468505] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 29 23:42:17 node-4 kernel: [    0.468522] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.468591] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.468667] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.468742] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 29 23:42:17 node-4 kernel: [    0.468747] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 29 23:42:17 node-4 kernel: [    0.468831] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 29 23:42:17 node-4 kernel: [    0.468978] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 29 23:42:17 node-4 kernel: [    0.468995] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 29 23:42:17 node-4 kernel: [    0.469073] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-4 kernel: [    0.469128] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 29 23:42:17 node-4 kernel: [    0.469149] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 29 23:42:17 node-4 kernel: [    0.469204] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-4 kernel: [    0.469247] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 29 23:42:17 node-4 kernel: [    0.469274] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 29 23:42:17 node-4 kernel: [    0.469329] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-4 kernel: [    0.469372] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 29 23:42:17 node-4 kernel: [    0.469395] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 29 23:42:17 node-4 kernel: [    0.469412] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 29 23:42:17 node-4 kernel: [    0.469491] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-4 kernel: [    0.469540] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 29 23:42:17 node-4 kernel: [    0.469565] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 29 23:42:17 node-4 kernel: [    0.469811] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 29 23:42:17 node-4 kernel: [    0.469817] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 29 23:42:17 node-4 kernel: [    0.469823] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 29 23:42:17 node-4 kernel: [    0.469829] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 29 23:42:17 node-4 kernel: [    0.469836] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 29 23:42:17 node-4 kernel: [    0.469867] pci 0000:01:00.0: supports D1 D2
Jul 29 23:42:17 node-4 kernel: [    0.480004] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 29 23:42:17 node-4 kernel: [    0.480007] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 29 23:42:17 node-4 kernel: [    0.480008] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 29 23:42:17 node-4 kernel: [    0.480115] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 29 23:42:17 node-4 kernel: [    0.480149] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 29 23:42:17 node-4 kernel: [    0.488010] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 29 23:42:17 node-4 kernel: [    0.488016] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-4 kernel: [    0.488020] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 23:42:17 node-4 kernel: [    0.488105] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 29 23:42:17 node-4 kernel: [    0.488172] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 29 23:42:17 node-4 kernel: [    0.488249] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-4 kernel: [    0.488293] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 29 23:42:17 node-4 kernel: [    0.488296] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-4 kernel: [    0.488298] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 23:42:17 node-4 kernel: [    0.488362] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 29 23:42:17 node-4 kernel: [    0.488486] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-4 kernel: [    0.488543] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 29 23:42:17 node-4 kernel: [    0.488545] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-4 kernel: [    0.488547] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 23:42:17 node-4 kernel: [    0.488596] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 29 23:42:17 node-4 kernel: [    0.488715] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-4 kernel: [    0.488756] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 29 23:42:17 node-4 kernel: [    0.488875] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-4 kernel: [    0.488913] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 29 23:42:17 node-4 kernel: [    0.489034] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-4 kernel: [    0.489072] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 29 23:42:17 node-4 kernel: [    0.489191] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 29 23:42:17 node-4 kernel: [    0.489234] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 29 23:42:17 node-4 kernel: [    0.489236] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-4 kernel: [    0.489238] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 23:42:17 node-4 kernel: [    0.489298] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 29 23:42:17 node-4 kernel: [    0.489380] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 29 23:42:17 node-4 kernel: [    0.489433] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 29 23:42:17 node-4 kernel: [    0.489474] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 29 23:42:17 node-4 kernel: [    0.489556] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 29 23:42:17 node-4 kernel: [    0.489663] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 29 23:42:17 node-4 kernel: [    0.489665] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-4 kernel: [    0.489667] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 29 23:42:17 node-4 kernel: [    0.489723] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 29 23:42:17 node-4 kernel: [    0.489777] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 29 23:42:17 node-4 kernel: [    0.489826] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 29 23:42:17 node-4 kernel: [    0.490036] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 29 23:42:17 node-4 kernel: [    0.490040] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 29 23:42:17 node-4 kernel: [    0.490103] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 29 23:42:17 node-4 kernel: [    0.490156] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 29 23:42:17 node-4 kernel: [    0.490204] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 29 23:42:17 node-4 kernel: [    0.490435] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 29 23:42:17 node-4 kernel: [    0.490439] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 29 23:42:17 node-4 kernel: [    0.490497] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 29 23:42:17 node-4 kernel: [    0.490561] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 29 23:42:17 node-4 kernel: [    0.490616] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 29 23:42:17 node-4 kernel: [    0.490838] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 29 23:42:17 node-4 kernel: [    0.490842] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 29 23:42:17 node-4 kernel: [    0.491015] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 29 23:42:17 node-4 kernel: [    0.491053] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 29 23:42:17 node-4 kernel: [    0.491132] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 29 23:42:17 node-4 kernel: [    0.491150] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 29 23:42:17 node-4 kernel: [    0.491163] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 29 23:42:17 node-4 kernel: [    0.491177] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 29 23:42:17 node-4 kernel: [    0.491227] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 29 23:42:17 node-4 kernel: [    0.496016] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 29 23:42:17 node-4 kernel: [    0.496025] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 29 23:42:17 node-4 kernel: [    0.496077] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 29 23:42:17 node-4 kernel: [    0.496584] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 29 23:42:17 node-4 kernel: [    0.496587] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 23:42:17 node-4 kernel: [    0.496706] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 29 23:42:17 node-4 kernel: [    0.496816] PCI host bridge to bus 0000:80
Jul 29 23:42:17 node-4 kernel: [    0.496818] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 29 23:42:17 node-4 kernel: [    0.496820] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 29 23:42:17 node-4 kernel: [    0.496821] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 29 23:42:17 node-4 kernel: [    0.496829] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.496892] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.496960] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 29 23:42:17 node-4 kernel: [    0.497022] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 29 23:42:17 node-4 kernel: [    0.497028] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 29 23:42:17 node-4 kernel: [    0.497099] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 29 23:42:17 node-4 kernel: [    0.497396] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 29 23:42:17 node-4 kernel: [    0.497427] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 29 23:42:17 node-4 kernel: [    0.497456] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 29 23:42:17 node-4 kernel: [    0.497485] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 29 23:42:17 node-4 kernel: [    0.497514] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 23:42:17 node-4 kernel: [    0.497544] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 23:42:17 node-4 kernel: [    0.497574] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 23:42:17 node-4 kernel: [    0.497603] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 23:42:17 node-4 kernel: [    0.497687] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 29 23:42:17 node-4 kernel: [    0.497692] ACPI: \_SB_.UNC1: notify handler is installed
Jul 29 23:42:17 node-4 kernel: [    0.497693] ACPI: \_SB_.UNC0: notify handler is installed
Jul 29 23:42:17 node-4 kernel: [    0.497708] ACPI: \_SB_.PCI0: notify handler is installed
Jul 29 23:42:17 node-4 kernel: [    0.497761] ACPI: \_SB_.PCI1: notify handler is installed
Jul 29 23:42:17 node-4 kernel: [    0.497840] Found 4 acpi root devices
Jul 29 23:42:17 node-4 kernel: [    0.497949] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 29 23:42:17 node-4 kernel: [    0.497951] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 29 23:42:17 node-4 kernel: [    0.497953] vgaarb: loaded
Jul 29 23:42:17 node-4 kernel: [    0.497954] vgaarb: bridge control possible 0000:0c:00.0
Jul 29 23:42:17 node-4 kernel: [    0.498074] SCSI subsystem initialized
Jul 29 23:42:17 node-4 kernel: [    0.498137] libata version 3.00 loaded.
Jul 29 23:42:17 node-4 kernel: [    0.498153] ACPI: bus type USB registered
Jul 29 23:42:17 node-4 kernel: [    0.498163] usbcore: registered new interface driver usbfs
Jul 29 23:42:17 node-4 kernel: [    0.498167] usbcore: registered new interface driver hub
Jul 29 23:42:17 node-4 kernel: [    0.498192] usbcore: registered new device driver usb
Jul 29 23:42:17 node-4 kernel: [    0.498353] PCI: Using ACPI for IRQ routing
Jul 29 23:42:17 node-4 kernel: [    0.501934] PCI: pci_cache_line_size set to 64 bytes
Jul 29 23:42:17 node-4 kernel: [    0.502145] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 29 23:42:17 node-4 kernel: [    0.502146] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 29 23:42:17 node-4 kernel: [    0.502147] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 29 23:42:17 node-4 kernel: [    0.502212] NetLabel: Initializing
Jul 29 23:42:17 node-4 kernel: [    0.502213] NetLabel:  domain hash size = 128
Jul 29 23:42:17 node-4 kernel: [    0.502214] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 29 23:42:17 node-4 kernel: [    0.502224] NetLabel:  unlabeled traffic allowed by default
Jul 29 23:42:17 node-4 kernel: [    0.502280] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 29 23:42:17 node-4 kernel: [    0.502284] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 29 23:42:17 node-4 kernel: [    0.504339] Switched to clocksource hpet
Jul 29 23:42:17 node-4 kernel: [    0.508178] AppArmor: AppArmor Filesystem Enabled
Jul 29 23:42:17 node-4 kernel: [    0.508191] pnp: PnP ACPI init
Jul 29 23:42:17 node-4 kernel: [    0.508198] ACPI: bus type PNP registered
Jul 29 23:42:17 node-4 kernel: [    0.508315] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 29 23:42:17 node-4 kernel: [    0.508323] pnp 00:01: [dma 4]
Jul 29 23:42:17 node-4 kernel: [    0.508340] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 29 23:42:17 node-4 kernel: [    0.508366] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 29 23:42:17 node-4 kernel: [    0.508385] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 29 23:42:17 node-4 kernel: [    0.508402] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 29 23:42:17 node-4 kernel: [    0.508435] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 29 23:42:17 node-4 kernel: [    0.508487] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 29 23:42:17 node-4 kernel: [    0.508489] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 29 23:42:17 node-4 kernel: [    0.508491] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 29 23:42:17 node-4 kernel: [    0.508492] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 29 23:42:17 node-4 kernel: [    0.508494] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 29 23:42:17 node-4 kernel: [    0.508498] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 29 23:42:17 node-4 kernel: [    0.508500] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 29 23:42:17 node-4 kernel: [    0.508502] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 29 23:42:17 node-4 kernel: [    0.508503] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 29 23:42:17 node-4 kernel: [    0.508505] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 29 23:42:17 node-4 kernel: [    0.508506] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 29 23:42:17 node-4 kernel: [    0.508508] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 29 23:42:17 node-4 kernel: [    0.508509] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 29 23:42:17 node-4 kernel: [    0.508512] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 29 23:42:17 node-4 kernel: [    0.508594] pnp 00:07: [dma 0 disabled]
Jul 29 23:42:17 node-4 kernel: [    0.508622] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 29 23:42:17 node-4 kernel: [    0.508696] pnp 00:08: [dma 0 disabled]
Jul 29 23:42:17 node-4 kernel: [    0.508727] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 29 23:42:17 node-4 kernel: [    0.508778] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 29 23:42:17 node-4 kernel: [    0.509123] pnp: PnP ACPI: found 10 devices
Jul 29 23:42:17 node-4 kernel: [    0.509125] ACPI: bus type PNP unregistered
Jul 29 23:42:17 node-4 kernel: [    0.515422] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 29 23:42:17 node-4 kernel: [    0.515425] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 29 23:42:17 node-4 kernel: [    0.515428] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 29 23:42:17 node-4 kernel: [    0.515432] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 29 23:42:17 node-4 kernel: [    0.515434] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-4 kernel: [    0.515449] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 29 23:42:17 node-4 kernel: [    0.515478] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 29 23:42:17 node-4 kernel: [    0.515493] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 29 23:42:17 node-4 kernel: [    0.515522] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 29 23:42:17 node-4 kernel: [    0.515536] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 29 23:42:17 node-4 kernel: [    0.515568] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 29 23:42:17 node-4 kernel: [    0.515582] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 29 23:42:17 node-4 kernel: [    0.515611] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 29 23:42:17 node-4 kernel: [    0.515613] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-4 kernel: [    0.515628] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 23:42:17 node-4 kernel: [    0.515657] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 29 23:42:17 node-4 kernel: [    0.515659] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-4 kernel: [    0.515673] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 23:42:17 node-4 kernel: [    0.515702] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 29 23:42:17 node-4 kernel: [    0.515704] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-4 kernel: [    0.515706] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 23:42:17 node-4 kernel: [    0.515711] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 29 23:42:17 node-4 kernel: [    0.515712] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 29 23:42:17 node-4 kernel: [    0.515715] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 23:42:17 node-4 kernel: [    0.515718] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 29 23:42:17 node-4 kernel: [    0.515723] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 29 23:42:17 node-4 kernel: [    0.515731] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 29 23:42:17 node-4 kernel: [    0.515734] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 29 23:42:17 node-4 kernel: [    0.515741] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 29 23:42:17 node-4 kernel: [    0.515742] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 29 23:42:17 node-4 kernel: [    0.515743] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 29 23:42:17 node-4 kernel: [    0.515743] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 29 23:42:17 node-4 kernel: [    0.515744] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 29 23:42:17 node-4 kernel: [    0.515745] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 29 23:42:17 node-4 kernel: [    0.515746] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 29 23:42:17 node-4 kernel: [    0.515747] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 29 23:42:17 node-4 kernel: [    0.515748] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 29 23:42:17 node-4 kernel: [    0.515749] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 29 23:42:17 node-4 kernel: [    0.515750] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 29 23:42:17 node-4 kernel: [    0.515751] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 29 23:42:17 node-4 kernel: [    0.515751] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 29 23:42:17 node-4 kernel: [    0.515752] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 29 23:42:17 node-4 kernel: [    0.515753] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 29 23:42:17 node-4 kernel: [    0.515754] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 29 23:42:17 node-4 kernel: [    0.515755] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 29 23:42:17 node-4 kernel: [    0.515756] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 29 23:42:17 node-4 kernel: [    0.515757] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 29 23:42:17 node-4 kernel: [    0.515758] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 29 23:42:17 node-4 kernel: [    0.515759] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 29 23:42:17 node-4 kernel: [    0.515760] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 29 23:42:17 node-4 kernel: [    0.515762] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 29 23:42:17 node-4 kernel: [    0.515763] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 29 23:42:17 node-4 kernel: [    0.515805] NET: Registered protocol family 2
Jul 29 23:42:17 node-4 kernel: [    0.516060] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 29 23:42:17 node-4 kernel: [    0.516398] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 29 23:42:17 node-4 kernel: [    0.516542] TCP: Hash tables configured (established 262144 bind 65536)
Jul 29 23:42:17 node-4 kernel: [    0.516584] TCP: reno registered
Jul 29 23:42:17 node-4 kernel: [    0.516611] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 29 23:42:17 node-4 kernel: [    0.516706] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 29 23:42:17 node-4 kernel: [    0.516852] NET: Registered protocol family 1
Jul 29 23:42:17 node-4 kernel: [    0.552422] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 29 23:42:17 node-4 kernel: [    0.552429] PCI: CLS 64 bytes, default 64
Jul 29 23:42:17 node-4 kernel: [    0.552470] Trying to unpack rootfs image as initramfs...
Jul 29 23:42:17 node-4 kernel: [    0.771439] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Jul 29 23:42:17 node-4 kernel: [    0.771488] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 29 23:42:17 node-4 kernel: [    0.771490] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 29 23:42:17 node-4 kernel: [    0.771917] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-4 kernel: [    0.771923] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-4 kernel: [    0.771928] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-4 kernel: [    0.771933] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-4 kernel: [    0.771959] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-4 kernel: [    0.771970] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-4 kernel: [    0.771979] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-4 kernel: [    0.771988] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-4 kernel: [    0.771995] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-4 kernel: [    0.772005] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-4 kernel: [    0.772011] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-4 kernel: [    0.772017] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-4 kernel: [    0.772024] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-4 kernel: [    0.772032] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-4 kernel: [    0.772039] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-4 kernel: [    0.772047] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 23:42:17 node-4 kernel: [    0.772146] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 29 23:42:17 node-4 kernel: [    0.772149] Scanning for low memory corruption every 60 seconds
Jul 29 23:42:17 node-4 kernel: [    0.772527] Initialise system trusted keyring
Jul 29 23:42:17 node-4 kernel: [    0.772579] audit: initializing netlink socket (disabled)
Jul 29 23:42:17 node-4 kernel: [    0.772596] type=2000 audit(1469835701.728:1): initialized
Jul 29 23:42:17 node-4 kernel: [    0.790537] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 29 23:42:17 node-4 kernel: [    0.792086] zbud: loaded
Jul 29 23:42:17 node-4 kernel: [    0.792221] VFS: Disk quotas dquot_6.5.2
Jul 29 23:42:17 node-4 kernel: [    0.792255] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 29 23:42:17 node-4 kernel: [    0.792634] fuse init (API version 7.22)
Jul 29 23:42:17 node-4 kernel: [    0.792695] msgmni has been set to 32768
Jul 29 23:42:17 node-4 kernel: [    0.792749] Key type big_key registered
Jul 29 23:42:17 node-4 kernel: [    0.793250] Key type asymmetric registered
Jul 29 23:42:17 node-4 kernel: [    0.793252] Asymmetric key parser 'x509' registered
Jul 29 23:42:17 node-4 kernel: [    0.793275] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 29 23:42:17 node-4 kernel: [    0.793344] io scheduler noop registered
Jul 29 23:42:17 node-4 kernel: [    0.793346] io scheduler deadline registered (default)
Jul 29 23:42:17 node-4 kernel: [    0.793364] io scheduler cfq registered
Jul 29 23:42:17 node-4 kernel: [    0.793919] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    0.794065] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    0.794181] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    0.794291] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    0.794405] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    0.794501] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    0.794882] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 29 23:42:17 node-4 kernel: [    0.794907] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 29 23:42:17 node-4 kernel: [    0.794923] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 29 23:42:17 node-4 kernel: [    0.794932] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.794935] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.794937] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 29 23:42:17 node-4 kernel: [    0.794942] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.794944] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.794945] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.794947] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.794949] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.794950] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.794952] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.794954] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.794955] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.794956] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.794958] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.794959] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.794962] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 29 23:42:17 node-4 kernel: [    0.794973] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.794975] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 29 23:42:17 node-4 kernel: [    0.794988] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.794991] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 29 23:42:17 node-4 kernel: [    0.795001] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.795003] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 29 23:42:17 node-4 kernel: [    0.795006] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 29 23:42:17 node-4 kernel: [    0.795043] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 29 23:42:17 node-4 kernel: [    0.795049] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 29 23:42:17 node-4 kernel: [    0.795054] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 29 23:42:17 node-4 kernel: [    0.795063] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 29 23:42:17 node-4 kernel: [    0.795103] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 29 23:42:17 node-4 kernel: [    0.795105] vesafb: scrolling: redraw
Jul 29 23:42:17 node-4 kernel: [    0.795106] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 29 23:42:17 node-4 kernel: [    0.815742] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 29 23:42:17 node-4 kernel: [    0.824251] Console: switching to colour frame buffer device 80x30
Jul 29 23:42:17 node-4 kernel: [    0.832929] fb0: VESA VGA frame buffer device
Jul 29 23:42:17 node-4 kernel: [    0.833125] intel_idle: MWAIT substates: 0x2120
Jul 29 23:42:17 node-4 kernel: [    0.833126] intel_idle: v0.4 model 0x3F
Jul 29 23:42:17 node-4 kernel: [    0.833127] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 29 23:42:17 node-4 kernel: [    0.833364] ipmi message handler version 39.2
Jul 29 23:42:17 node-4 kernel: [    0.833639] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 29 23:42:17 node-4 kernel: [    0.834071] ACPI: AC Adapter [P111] (on-line)
Jul 29 23:42:17 node-4 kernel: [    0.839314] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 29 23:42:17 node-4 kernel: [    0.850321] ACPI: Power Button [PWRB]
Jul 29 23:42:17 node-4 kernel: [    0.856078] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 29 23:42:17 node-4 kernel: [    0.867694] ACPI: Power Button [PWRF]
Jul 29 23:42:17 node-4 kernel: [    0.893899] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 29 23:42:17 node-4 kernel: [    0.905542] pstore: Registered erst as persistent store backend
Jul 29 23:42:17 node-4 kernel: [    0.911726] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 29 23:42:17 node-4 kernel: [    0.923660] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 29 23:42:17 node-4 kernel: [    0.950404] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 29 23:42:17 node-4 kernel: [    0.983677] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 29 23:42:17 node-4 kernel: [    0.997735] Linux agpgart interface v0.103
Jul 29 23:42:17 node-4 kernel: [    1.005380] brd: module loaded
Jul 29 23:42:17 node-4 kernel: [    1.012415] loop: module loaded
Jul 29 23:42:17 node-4 kernel: [    1.019136] libphy: Fixed MDIO Bus: probed
Jul 29 23:42:17 node-4 kernel: [    1.025616] tun: Universal TUN/TAP device driver, 1.6
Jul 29 23:42:17 node-4 kernel: [    1.032086] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 29 23:42:17 node-4 kernel: [    1.038613] PPP generic driver version 2.4.2
Jul 29 23:42:17 node-4 kernel: [    1.044987] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 29 23:42:17 node-4 kernel: [    1.051421] ehci-pci: EHCI PCI platform driver
Jul 29 23:42:17 node-4 kernel: [    1.057947] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 29 23:42:17 node-4 kernel: [    1.064359] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 29 23:42:17 node-4 kernel: [    1.076884] ehci-pci 0000:00:1a.0: debug port 2
Jul 29 23:42:17 node-4 kernel: [    1.087077] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 29 23:42:17 node-4 kernel: [    1.087095] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 29 23:42:17 node-4 kernel: [    1.103835] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 29 23:42:17 node-4 kernel: [    1.109903] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 29 23:42:17 node-4 kernel: [    1.116075] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 29 23:42:17 node-4 kernel: [    1.128100] usb usb1: Product: EHCI Host Controller
Jul 29 23:42:17 node-4 kernel: [    1.134220] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 29 23:42:17 node-4 kernel: [    1.140338] usb usb1: SerialNumber: 0000:00:1a.0
Jul 29 23:42:17 node-4 kernel: [    1.146295] hub 1-0:1.0: USB hub found
Jul 29 23:42:17 node-4 kernel: [    1.152059] hub 1-0:1.0: 2 ports detected
Jul 29 23:42:17 node-4 kernel: [    1.157871] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 29 23:42:17 node-4 kernel: [    1.163455] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 29 23:42:17 node-4 kernel: [    1.174362] ehci-pci 0000:00:1d.0: debug port 2
Jul 29 23:42:17 node-4 kernel: [    1.183668] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 29 23:42:17 node-4 kernel: [    1.183671] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 29 23:42:17 node-4 kernel: [    1.199753] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 29 23:42:17 node-4 kernel: [    1.204964] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 29 23:42:17 node-4 kernel: [    1.210273] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 29 23:42:17 node-4 kernel: [    1.220858] usb usb2: Product: EHCI Host Controller
Jul 29 23:42:17 node-4 kernel: [    1.226335] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 29 23:42:17 node-4 kernel: [    1.231885] usb usb2: SerialNumber: 0000:00:1d.0
Jul 29 23:42:17 node-4 kernel: [    1.237416] hub 2-0:1.0: USB hub found
Jul 29 23:42:17 node-4 kernel: [    1.242792] hub 2-0:1.0: 2 ports detected
Jul 29 23:42:17 node-4 kernel: [    1.248098] ehci-platform: EHCI generic platform driver
Jul 29 23:42:17 node-4 kernel: [    1.253329] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 29 23:42:17 node-4 kernel: [    1.258653] ohci-pci: OHCI PCI platform driver
Jul 29 23:42:17 node-4 kernel: [    1.263951] ohci-platform: OHCI generic platform driver
Jul 29 23:42:17 node-4 kernel: [    1.269244] uhci_hcd: USB Universal Host Controller Interface driver
Jul 29 23:42:17 node-4 kernel: [    1.274591] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 29 23:42:17 node-4 kernel: [    1.475517] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 29 23:42:17 node-4 kernel: [    1.767283] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 29 23:42:17 node-4 kernel: [    1.783621] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 29 23:42:17 node-4 kernel: [    1.789243] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 29 23:42:17 node-4 kernel: [    1.795015] hub 1-1:1.0: USB hub found
Jul 29 23:42:17 node-4 kernel: [    1.800606] hub 1-1:1.0: 6 ports detected
Jul 29 23:42:17 node-4 kernel: [    1.915145] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 29 23:42:17 node-4 kernel: [    2.313268] i8042: No controller found
Jul 29 23:42:17 node-4 kernel: [    2.318817] mousedev: PS/2 mouse device common for all mice
Jul 29 23:42:17 node-4 kernel: [    2.324547] rtc_cmos 00:02: RTC can wake from S4
Jul 29 23:42:17 node-4 kernel: [    2.327600] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 29 23:42:17 node-4 kernel: [    2.327600] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 29 23:42:17 node-4 kernel: [    2.328633] hub 2-1:1.0: USB hub found
Jul 29 23:42:17 node-4 kernel: [    2.328847] hub 2-1:1.0: 8 ports detected
Jul 29 23:42:17 node-4 kernel: [    2.352831] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 29 23:42:17 node-4 kernel: [    2.358584] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 29 23:42:17 node-4 kernel: [    2.369883] device-mapper: uevent: version 1.0.3
Jul 29 23:42:17 node-4 kernel: [    2.375587] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 29 23:42:17 node-4 kernel: [    2.386945] ledtrig-cpu: registered to indicate activity on CPUs
Jul 29 23:42:17 node-4 kernel: [    2.392903] TCP: cubic registered
Jul 29 23:42:17 node-4 kernel: [    2.398770] NET: Registered protocol family 10
Jul 29 23:42:17 node-4 kernel: [    2.404830] NET: Registered protocol family 17
Jul 29 23:42:17 node-4 kernel: [    2.410595] Key type dns_resolver registered
Jul 29 23:42:17 node-4 kernel: [    2.416625] Loading compiled-in X.509 certificates
Jul 29 23:42:17 node-4 kernel: [    2.422826] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 29 23:42:17 node-4 kernel: [    2.434432] registered taskstats version 1
Jul 29 23:42:17 node-4 kernel: [    2.442478] Key type trusted registered
Jul 29 23:42:17 node-4 kernel: [    2.450086] Key type encrypted registered
Jul 29 23:42:17 node-4 kernel: [    2.455572] AppArmor: AppArmor sha1 policy hashing enabled
Jul 29 23:42:17 node-4 kernel: [    2.461070] IMA: No TPM chip found, activating TPM-bypass!
Jul 29 23:42:17 node-4 kernel: [    2.467179] regulator-dummy: disabling
Jul 29 23:42:17 node-4 kernel: [    2.472644]   Magic number: 8:759:707
Jul 29 23:42:17 node-4 kernel: [    2.478253] acpi LNXCPU:44: hash matches
Jul 29 23:42:17 node-4 kernel: [    2.483738] rtc_cmos 00:02: setting system clock to 2016-07-29 23:41:44 UTC (1469835704)
Jul 29 23:42:17 node-4 kernel: [    2.495985] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 29 23:42:17 node-4 kernel: [    2.501582] EDD information not available.
Jul 29 23:42:17 node-4 kernel: [    2.507083] PM: Hibernation image not present or could not be loaded.
Jul 29 23:42:17 node-4 kernel: [    2.507943] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 29 23:42:17 node-4 kernel: [    2.519148] Write protecting the kernel read-only data: 12288k
Jul 29 23:42:17 node-4 kernel: [    2.525464] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 29 23:42:17 node-4 kernel: [    2.538271] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 29 23:42:17 node-4 kernel: [    2.570577] device-mapper: multipath: version 1.6.0 loaded
Jul 29 23:42:17 node-4 kernel: [    2.578334] systemd-udevd[215]: starting version 204
Jul 29 23:42:17 node-4 kernel: [    2.601654] md: linear personality registered for level -1
Jul 29 23:42:17 node-4 kernel: [    2.606754] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 29 23:42:17 node-4 kernel: [    2.622121] md: multipath personality registered for level -4
Jul 29 23:42:17 node-4 kernel: [    2.630384] md: raid0 personality registered for level 0
Jul 29 23:42:17 node-4 kernel: [    2.638663] md: raid1 personality registered for level 1
Jul 29 23:42:17 node-4 kernel: [    2.647016] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 29 23:42:17 node-4 kernel: [    2.653299] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 29 23:42:17 node-4 kernel: [    2.659718] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 29 23:42:17 node-4 kernel: [    2.659934] megasas: FW now in Ready state
Jul 29 23:42:17 node-4 kernel: [    2.660173] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.660271] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.660401] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.660491] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.660550] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.660664] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.660769] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.660909] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.661013] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.661052] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.661185] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.661255] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.661331] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.661478] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.661562] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.661627] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.662198] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 29 23:42:17 node-4 kernel: [    2.693548] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 29 23:42:17 node-4 kernel: [    2.706734] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 29 23:42:17 node-4 kernel: [    2.714551] raid6: sse2x1   10989 MB/s
Jul 29 23:42:17 node-4 kernel: [    2.727339] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 23:42:17 node-4 kernel: [    2.734267] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.734272] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.734276] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.734280] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.734317] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 23:42:17 node-4 kernel: [    2.743782] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 29 23:42:17 node-4 kernel: [    2.743783] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 29 23:42:17 node-4 kernel: [    2.743784] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 29 23:42:17 node-4 kernel: [    2.743785] usb 2-1.4: Manufacturer: Avocent
Jul 29 23:42:17 node-4 kernel: [    2.743785] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 29 23:42:17 node-4 kernel: [    2.782707] raid6: sse2x2   13340 MB/s
Jul 29 23:42:17 node-4 kernel: [    2.850364] raid6: sse2x4   10067 MB/s
Jul 29 23:42:17 node-4 kernel: [    2.922307] raid6: avx2x1   14954 MB/s
Jul 29 23:42:17 node-4 kernel: [    2.994244] raid6: avx2x2   18865 MB/s
Jul 29 23:42:17 node-4 kernel: [    3.066184] raid6: avx2x4   21371 MB/s
Jul 29 23:42:17 node-4 kernel: [    3.071781] raid6: using algorithm avx2x4 (21371 MB/s)
Jul 29 23:42:17 node-4 kernel: [    3.077289] raid6: using avx2x2 recovery algorithm
Jul 29 23:42:17 node-4 kernel: [    3.082680] megasas:IOC Init cmd success
Jul 29 23:42:17 node-4 kernel: [    3.082681] Switched to clocksource tsc
Jul 29 23:42:17 node-4 kernel: [    3.094058] xor: automatically using best checksumming function:
Jul 29 23:42:17 node-4 kernel: [    3.094156] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 29 23:42:17 node-4 kernel: [    3.094158] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 29 23:42:17 node-4 kernel: [    3.094159] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 23:42:17 node-4 kernel: [    3.094246] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    3.094287] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    3.094312] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    3.094345] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    3.094422] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 23:42:17 node-4 kernel: [    3.107853] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 29 23:42:17 node-4 kernel: [    3.107854] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 29 23:42:17 node-4 kernel: [    3.107855] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 23:42:17 node-4 kernel: [    3.107922] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    3.107961] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    3.107996] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    3.108029] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    3.108100] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 23:42:17 node-4 kernel: [    3.110185] megasas: INIT adapter done
Jul 29 23:42:17 node-4 kernel: [    3.119171] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 29 23:42:17 node-4 kernel: [    3.119172] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 29 23:42:17 node-4 kernel: [    3.119173] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 23:42:17 node-4 kernel: [    3.119233] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    3.119270] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    3.119305] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    3.119344] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 29 23:42:17 node-4 kernel: [    3.119421] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 23:42:17 node-4 kernel: [    3.202071] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 29 23:42:17 node-4 kernel: [    3.202448] scsi0 : LSI SAS based MegaRAID driver
Jul 29 23:42:17 node-4 kernel: [    3.209816] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 29 23:42:17 node-4 kernel: [    3.220674] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 29 23:42:17 node-4 kernel: [    3.224710] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 29 23:42:17 node-4 kernel: [    3.224801] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 29 23:42:17 node-4 kernel: [    3.225111] sd 0:2:0:0: [sda] Write Protect is off
Jul 29 23:42:17 node-4 kernel: [    3.225112] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 29 23:42:17 node-4 kernel: [    3.225177] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 29 23:42:17 node-4 kernel: [    3.256961]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 29 23:42:17 node-4 kernel: [    3.257516] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 29 23:42:17 node-4 kernel: [    3.314429] hidraw: raw HID events driver (C) Jiri Kosina
Jul 29 23:42:17 node-4 kernel: [    3.323994] usbcore: registered new interface driver usbhid
Jul 29 23:42:17 node-4 kernel: [    3.330462] usbhid: USB HID core driver
Jul 29 23:42:17 node-4 kernel: [    3.337676] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Jul 29 23:42:17 node-4 kernel: [    3.350530] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Jul 29 23:42:17 node-4 kernel: [    3.354008]    avx       : 35737.000 MB/sec
Jul 29 23:42:17 node-4 kernel: [    3.370645] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Jul 29 23:42:17 node-4 kernel: [    3.384281] async_tx: api initialized (async)
Jul 29 23:42:17 node-4 kernel: [    3.384924] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Jul 29 23:42:17 node-4 kernel: [    3.386058] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Jul 29 23:42:17 node-4 kernel: [    3.386250] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Jul 29 23:42:17 node-4 kernel: [    3.436425] md: raid6 personality registered for level 6
Jul 29 23:42:17 node-4 kernel: [    3.443587] md: raid5 personality registered for level 5
Jul 29 23:42:17 node-4 kernel: [    3.450566] md: raid4 personality registered for level 4
Jul 29 23:42:17 node-4 kernel: [    3.460226] random: lvm urandom read with 31 bits of entropy available
Jul 29 23:42:17 node-4 kernel: [    3.467116] md: raid10 personality registered for level 10
Jul 29 23:42:17 node-4 kernel: [    3.523243] multipathd (370): /proc/370/oom_adj is deprecated, please use /proc/370/oom_score_adj instead.
Jul 29 23:42:17 node-4 kernel: [    3.595769] bio: create slab <bio-1> at 1
Jul 29 23:42:17 node-4 kernel: [    4.360435] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 23:42:17 node-4 kernel: [    4.997938] random: nonblocking pool is initialized
Jul 29 23:42:17 node-4 kernel: [    5.068114] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 29 23:42:17 node-4 kernel: [    5.112585] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 29 23:42:17 node-4 kernel: [    5.202068] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 29 23:42:17 node-4 kernel: [    5.243989] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 29 23:42:17 node-4 kernel: [    5.307669] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 23:42:17 node-4 kernel: [    5.520061] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 29 23:42:17 node-4 kernel: [    5.556977] XFS (dm-0): Mounting Filesystem
Jul 29 23:42:17 node-4 kernel: [    5.818546] XFS (dm-0): Ending clean mount
Jul 29 23:42:17 node-4 kernel: [    5.864718] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 23:42:17 node-4 kernel: [    5.903371] XFS (dm-1): Mounting Filesystem
Jul 29 23:42:17 node-4 kernel: [    6.047125] XFS (dm-1): Ending clean mount
Jul 29 23:42:17 node-4 kernel: [    7.755296] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 29 23:42:17 node-4 kernel: [    7.780266] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 29 23:42:17 node-4 kernel: [    7.927764] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 29 23:42:17 node-4 kernel: [    7.927769] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 29 23:42:17 node-4 kernel: [    7.927774] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 29 23:42:17 node-4 kernel: [    7.927779] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 29 23:42:17 node-4 kernel: [    7.955856] systemd-udevd[777]: starting version 204
Jul 29 23:42:17 node-4 kernel: [    8.161269] power_meter ACPI000D:00: Found ACPI power meter.
Jul 29 23:42:17 node-4 kernel: [    8.161281] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 29 23:42:17 node-4 kernel: [    8.191705] wmi: Mapper loaded
Jul 29 23:42:17 node-4 kernel: [    8.198343] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 29 23:42:17 node-4 kernel: [    8.198348] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 29 23:42:17 node-4 kernel: [    8.198350] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 29 23:42:17 node-4 kernel: [    8.198352] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 29 23:42:17 node-4 kernel: [    8.198401] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 29 23:42:17 node-4 kernel: [    8.212325] IPMI System Interface driver.
Jul 29 23:42:17 node-4 kernel: [    8.212350] ipmi_si: probing via ACPI
Jul 29 23:42:17 node-4 kernel: [    8.212366] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 29 23:42:17 node-4 kernel: [    8.212367] ipmi_si: Adding ACPI-specified kcs state machine
Jul 29 23:42:17 node-4 kernel: [    8.212374] ipmi_si: probing via SMBIOS
Jul 29 23:42:17 node-4 kernel: [    8.212375] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 29 23:42:17 node-4 kernel: [    8.212375] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 29 23:42:17 node-4 kernel: [    8.212377] ipmi_si: probing via SPMI
Jul 29 23:42:17 node-4 kernel: [    8.212377] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 29 23:42:17 node-4 kernel: [    8.212378] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 29 23:42:17 node-4 kernel: [    8.212379] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 29 23:42:17 node-4 kernel: [    8.218223] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 29 23:42:17 node-4 kernel: [    8.322214] systemd-udevd[796]: renamed network interface eth0 to enp6s0
Jul 29 23:42:17 node-4 kernel: [    8.354075] systemd-udevd[794]: renamed network interface eth1 to enp7s0
Jul 29 23:42:17 node-4 kernel: [    8.374276] systemd-udevd[795]: renamed network interface eth2 to enp8s0
Jul 29 23:42:17 node-4 kernel: [    8.398021] systemd-udevd[797]: renamed network interface eth3 to enp9s0
Jul 29 23:42:17 node-4 kernel: [    8.433544] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 29 23:42:17 node-4 kernel: [    8.433549] ipmi_si 00:09: IPMI kcs interface initialized
Jul 29 23:42:17 node-4 kernel: [    8.703733] type=1400 audit(1469835710.720:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1063 comm="apparmor_parser"
Jul 29 23:42:17 node-4 kernel: [    8.703888] type=1400 audit(1469835710.720:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1063 comm="apparmor_parser"
Jul 29 23:42:17 node-4 kernel: [    8.704014] type=1400 audit(1469835710.720:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1063 comm="apparmor_parser"
Jul 29 23:42:17 node-4 kernel: [    8.705349] type=1400 audit(1469835710.720:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1059 comm="apparmor_parser"
Jul 29 23:42:17 node-4 kernel: [    8.705497] type=1400 audit(1469835710.724:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1059 comm="apparmor_parser"
Jul 29 23:42:17 node-4 kernel: [    8.705618] type=1400 audit(1469835710.724:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1059 comm="apparmor_parser"
Jul 29 23:42:17 node-4 kernel: [    8.708490] type=1400 audit(1469835710.724:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1062 comm="apparmor_parser"
Jul 29 23:42:17 node-4 kernel: [    8.708630] type=1400 audit(1469835710.724:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1062 comm="apparmor_parser"
Jul 29 23:42:17 node-4 kernel: [    8.708751] type=1400 audit(1469835710.724:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1062 comm="apparmor_parser"
Jul 29 23:42:17 node-4 kernel: [    8.719532] type=1400 audit(1469835710.736:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1060 comm="apparmor_parser"
Jul 29 23:42:17 node-4 kernel: [    9.280915] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 29 23:42:17 node-4 kernel: [    9.281613] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 29 23:42:17 node-4 kernel: [    9.421212] enic 0000:06:00.0 enp6s0: Link UP
Jul 29 23:42:17 node-4 kernel: [    9.422335] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 29 23:42:17 node-4 kernel: [    9.422340] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 29 23:42:17 node-4 kernel: [   18.426630] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 29 23:42:18 node-4 failsafe: Failsafe of 120 seconds reached.
Jul 29 23:42:18 node-4 kernel: [   37.132459] init: failsafe main process (8396) killed by TERM signal
Jul 29 23:42:19 node-4 dbus[8425]: [system] AppArmor D-Bus mediation is enabled
Jul 29 23:42:19 node-4 kernel: [   37.305673] audit_printk_skb: 30 callbacks suppressed
Jul 29 23:42:19 node-4 kernel: [   37.305675] type=1400 audit(1469835739.155:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8521 comm="apparmor_parser"
Jul 29 23:42:19 node-4 kernel: [   37.305679] type=1400 audit(1469835739.155:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8521 comm="apparmor_parser"
Jul 29 23:42:19 node-4 kernel: [   37.305682] type=1400 audit(1469835739.155:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8521 comm="apparmor_parser"
Jul 29 23:42:19 node-4 kernel: [   37.305898] type=1400 audit(1469835739.155:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8521 comm="apparmor_parser"
Jul 29 23:42:19 node-4 kernel: [   37.305900] type=1400 audit(1469835739.155:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8521 comm="apparmor_parser"
Jul 29 23:42:19 node-4 kernel: [   37.306011] type=1400 audit(1469835739.155:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8521 comm="apparmor_parser"
Jul 29 23:42:19 node-4 kernel: [   37.310843] type=1400 audit(1469835739.159:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8522 comm="apparmor_parser"
Jul 29 23:42:19 node-4 kernel: [   37.381596] type=1400 audit(1469835739.231:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8524 comm="apparmor_parser"
Jul 29 23:42:19 node-4 cron[8554]: (CRON) INFO (pidfile fd = 3)
Jul 29 23:42:19 node-4 anacron[8569]: Anacron 2.3 started on 2016-07-29
Jul 29 23:42:19 node-4 cron[8578]: (CRON) STARTUP (fork ok)
Jul 29 23:42:19 node-4 anacron[8569]: Will run job `cron.daily' in 5 min.
Jul 29 23:42:19 node-4 anacron[8569]: Will run job `cron.weekly' in 10 min.
Jul 29 23:42:19 node-4 anacron[8569]: Will run job `cron.monthly' in 15 min.
Jul 29 23:42:19 node-4 anacron[8569]: Jobs will be executed sequentially
Jul 29 23:42:19 node-4 cron[8578]: (CRON) INFO (Running @reboot jobs)
Jul 29 23:42:19 node-4 multipathd: path checkers start up
Jul 29 23:42:19 node-4 postfix/master[8733]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 29 23:42:23 node-4 puppet-agent[8917]: Reopening log files
Jul 29 23:42:23 node-4 puppet-agent[8917]: Could not request certificate: Connection refused - connect(2)
Jul 29 23:42:38 node-4 puppet-user[9125]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 29 23:42:38 node-4 puppet-user[9125]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Jul 29 23:42:39 node-4 puppet-user[9125]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 29 23:42:39 node-4 puppet-user[9125]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 29 23:42:39 node-4 puppet-user[9125]: Finished catalog run in 0.78 seconds
Jul 29 23:42:41 node-4 multipathd: uevent trigger error
Jul 29 23:42:41 node-4 puppet-user[9570]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 29 23:42:41 node-4 puppet-user[9570]: Compiled catalog for node-4.domain.tld in environment production in 0.08 seconds
Jul 29 23:42:41 node-4 puppet-user[9570]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 29 23:42:41 node-4 puppet-user[9570]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 29 23:42:41 node-4 puppet-user[9570]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Jul 29 23:42:41 node-4 puppet-user[9570]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 29 23:42:41 node-4 puppet-user[9570]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 29 23:42:41 node-4 puppet-user[9570]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 29 23:42:41 node-4 puppet-user[9570]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 29 23:42:41 node-4 puppet-user[9570]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 29 23:42:41 node-4 puppet-user[9570]: Finished catalog run in 0.06 seconds
Jul 29 23:42:42 node-4 puppet-user[10207]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 29 23:42:42 node-4 puppet-user[10207]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Jul 29 23:42:42 node-4 puppet-user[10207]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 29 23:42:42 node-4 puppet-user[10207]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 29 23:42:42 node-4 puppet-user[10207]: Finished catalog run in 0.03 seconds
Jul 29 23:42:44 node-4 puppet-user[10686]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 29 23:42:44 node-4 puppet-user[10686]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 29 23:42:44 node-4 puppet-user[10686]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 29 23:42:44 node-4 puppet-user[10686]: Finished catalog run in 0.03 seconds
Jul 29 23:42:45 node-4 puppet-user[11152]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 29 23:42:46 node-4 puppet-user[11152]: Compiled catalog for node-4.domain.tld in environment production in 0.18 seconds
Jul 29 23:42:46 node-4 puppet-user[11152]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 29 23:42:46 node-4 puppet-user[11152]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-kvm-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-kvm-0.9/]/returns) executed successfully
Jul 29 23:42:46 node-4 puppet-user[11152]: Finished catalog run in 0.43 seconds
Jul 29 23:42:47 node-4 puppet-user[11644]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 29 23:42:48 node-4 puppet-user[11644]: Compiled catalog for node-4.domain.tld in environment production in 0.19 seconds
Jul 29 23:42:48 node-4 puppet-user[11644]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 29 23:42:48 node-4 puppet-user[11644]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 29 23:42:48 node-4 puppet-user[11644]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-kvm-0.9.0]/Apt::Setting[list-fuel-plugin-kvm-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-kvm-0.9.0.list]/ensure) created
Jul 29 23:42:48 node-4 puppet-user[11644]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 29 23:42:48 node-4 puppet-user[11644]: Finished catalog run in 0.22 seconds
Jul 29 23:42:49 node-4 puppet-user[12126]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 29 23:42:50 node-4 puppet-user[12126]: Compiled catalog for node-4.domain.tld in environment production in 0.15 seconds
Jul 29 23:42:50 node-4 puppet-user[12126]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 29 23:42:50 node-4 kernel: [   68.271847] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 29 23:42:50 node-4 kernel: [   68.271893] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Jul 29 23:42:50 node-4 puppet-user[12126]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Jul 29 23:42:50 node-4 puppet-user[12126]: Finished catalog run in 0.05 seconds
Jul 29 23:42:51 node-4 puppet-user[12587]: (Scope(Class[main])) MODULAR: sync_time
Jul 29 23:42:51 node-4 puppet-user[12587]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 29 23:42:52 node-4 ntpdate[13016]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 29 23:42:53 node-4 kernel: [   71.995078] init: plymouth-upstart-bridge main process ended, respawning
Jul 29 23:42:54 node-4 puppet-agent[8917]: Could not run: SIGTERM
Jul 29 23:42:54 node-4 kernel: [   72.251408] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 29 23:42:54 node-4 ec2: 
Jul 29 23:42:54 node-4 ec2: #############################################################
Jul 29 23:42:54 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 29 23:42:54 node-4 ec2: 1024 bb:1e:f2:24:40:b9:83:8f:08:5c:28:ca:2a:ea:82:28  root@node-4.domain.tld (DSA)
Jul 29 23:42:54 node-4 ec2: 256 95:44:f7:27:c9:4b:d4:a3:19:1c:2a:51:58:28:fa:f8  root@node-4.domain.tld (ECDSA)
Jul 29 23:42:54 node-4 ec2: 256 ab:f0:7d:1d:fb:68:55:ab:4f:b5:c6:d3:c4:22:74:44  root@node-4.domain.tld (ED25519)
Jul 29 23:42:54 node-4 ec2: 2048 c6:26:03:25:9c:27:11:9f:e3:1d:d1:97:69:d8:a6:ae  root@node-4.domain.tld (RSA)
Jul 29 23:42:54 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 29 23:42:54 node-4 ec2: #############################################################
Jul 29 23:42:58 node-4 ntpdate[13016]: adjust time server 10.20.0.2 offset 0.002016 sec
Jul 29 23:42:58 node-4 puppet-user[12587]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 29 23:42:58 node-4 puppet-user[12587]: Finished catalog run in 6.16 seconds
Jul 29 23:43:01 node-4 CRON[13347]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 29 23:43:28 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:43:28 node-4 nailgun-agent: I, [2016-07-29T23:43:28.655461 #13350]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 23:43:41 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:43:41 node-4 nailgun-agent: I, [2016-07-29T23:43:41.707243 #13350]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 29 23:44:01 node-4 CRON[13688]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 29 23:44:14 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:44:14 node-4 nailgun-agent: I, [2016-07-29T23:44:14.881764 #13691]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 23:44:27 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:44:27 node-4 nailgun-agent: I, [2016-07-29T23:44:27.861233 #13691]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 29 23:45:01 node-4 CRON[14001]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 29 23:45:17 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:45:17 node-4 nailgun-agent: I, [2016-07-29T23:45:17.033623 #14004]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 23:45:29 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:45:30 node-4 nailgun-agent: I, [2016-07-29T23:45:30.102274 #14004]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 29 23:46:01 node-4 CRON[14314]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 29 23:46:06 node-4 puppet-user[14344]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 29 23:46:06 node-4 puppet-user[14344]: Compiled catalog for node-4.domain.tld in environment production in 0.11 seconds
Jul 29 23:46:06 node-4 puppet-user[14344]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 29 23:46:06 node-4 puppet-user[14344]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-kvm"]'
Jul 29 23:46:06 node-4 puppet-user[14344]: Finished catalog run in 0.08 seconds
Jul 29 23:46:08 node-4 puppet-user[14806]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 29 23:46:09 node-4 puppet-user[14806]: Compiled catalog for node-4.domain.tld in environment production in 1.05 seconds
Jul 29 23:46:10 node-4 puppet-user[14806]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Jul 29 23:46:10 node-4 puppet-user[14806]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Jul 29 23:46:10 node-4 puppet-user[14806]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Jul 29 23:46:10 node-4 puppet-user[14806]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 29 23:46:10 node-4 puppet-user[14806]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Jul 29 23:46:10 node-4 puppet-user[14806]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 29 23:46:10 node-4 puppet-user[14806]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 29 23:46:10 node-4 puppet-user[14806]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 29 23:46:10 node-4 puppet-user[14806]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 29 23:46:10 node-4 puppet-user[14806]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 29 23:46:10 node-4 puppet-user[14806]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 29 23:46:10 node-4 puppet-user[14806]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 29 23:46:10 node-4 puppet-user[14806]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 29 23:46:10 node-4 puppet-user[14806]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Jul 29 23:46:10 node-4 puppet-user[14806]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 29 23:46:10 node-4 puppet-user[14806]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 29 23:46:15 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:46:15 node-4 nailgun-agent: I, [2016-07-29T23:46:15.285807 #14317]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 23:46:28 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 23:46:28 node-4 nailgun-agent: I, [2016-07-29T23:46:28.244627 #14317]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 29 23:46:28 node-4 puppet-user[14806]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 29 23:46:28 node-4 puppet-user[14806]: Finished catalog run in 18.29 seconds
Jul 29 23:46:30 node-4 puppet-user[16084]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 29 23:46:30 node-4 puppet-user[16084]: Compiled catalog for node-4.domain.tld in environment production in 0.14 seconds
Jul 29 23:46:35 node-4 puppet-user[16084]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 29 23:47:01 node-4 CRON[18305]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 29 23:47:07 node-4 puppet-user[16084]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 29 23:47:07 node-4 puppet-user[16084]: Finished catalog run in 36.32 seconds
Jul 29 23:47:09 node-4 puppet-user[18663]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 29 23:47:09 node-4 puppet-user[18663]: Compiled catalog for node-4.domain.tld in environment production in 0.63 seconds
Jul 29 23:47:09 node-4 puppet-user[18663]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 29 23:47:09 node-4 puppet-user[18663]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 29 23:47:09 node-4 puppet-user[18663]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 29 23:47:09 node-4 puppet-user[18663]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 29 23:47:09 node-4 puppet-user[18663]: Finished catalog run in 0.08 seconds
Jul 29 23:47:11 node-4 puppet-user[19148]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 29 23:47:12 node-4 puppet-user[19148]: Compiled catalog for node-4.domain.tld in environment production in 0.92 seconds
Jul 29 23:47:12 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 29 23:47:12 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 29 23:47:12 node-4 crontab[19602]: (root) LIST (root)
Jul 29 23:47:12 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 29 23:47:12 node-4 crontab[19603]: (root) REPLACE (root)
Jul 29 23:47:15 node-4 puppet-user[19148]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 29 23:47:16 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 29 23:47:17 node-4 puppet-user[19148]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 29 23:47:17 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8369" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 23:47:17 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 29 23:47:19 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:19 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:19 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:19 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:19 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:19 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:19 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:38 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:38 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:38 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:38 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:38 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:38 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:40 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:40 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:40 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:40 node-4 multipathd: uevent trigger error
<27>Jul 29 23:47:40 node-4 multipathd: uevent trigger error
<27>Jul 29 23:48:41 node-4 ntpdate[31466]: no servers can be used, exiting
<27>Jul 29 23:48:41 node-4 ntpdate[31726]: no servers can be used, exiting
<27>Jul 29 23:49:12 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:12 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:12 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:12 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:12 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:12 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:13 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:16 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:16 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:16 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:16 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:16 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:16 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:28 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:28 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:28 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:28 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:28 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:31 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:31 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:31 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:31 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:31 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:37 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:37 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:37 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:37 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:37 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:37 node-4 multipathd: uevent trigger error
<43>Jul 29 23:49:57 node-4 apache2_error [Fri Jul 29 23:49:50.086509 2016] [mpm_event:notice] [pid 9445:tid 139716753463168] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 23:49:57 node-4 apache2_error [Fri Jul 29 23:49:50.086672 2016] [core:notice] [pid 9445:tid 139716753463168] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 29 23:49:57 node-4 apache2_error [Fri Jul 29 23:49:53.172704 2016] [mpm_event:notice] [pid 9445:tid 139716753463168] AH00491: caught SIGTERM, shutting down
<43>Jul 29 23:49:57 node-4 apache2_error [Fri Jul 29 23:49:54.266054 2016] [mpm_worker:notice] [pid 9821:tid 140634042972032] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 23:49:57 node-4 apache2_error [Fri Jul 29 23:49:54.266092 2016] [core:notice] [pid 9821:tid 140634042972032] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 23:49:58 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:58 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:58 node-4 multipathd: uevent trigger error
<27>Jul 29 23:49:58 node-4 multipathd: uevent trigger error
<27>Jul 29 23:50:34 node-4 multipathd: uevent trigger error
<27>Jul 29 23:50:34 node-4 multipathd: uevent trigger error
<27>Jul 29 23:50:34 node-4 multipathd: uevent trigger error
<27>Jul 29 23:50:34 node-4 multipathd: uevent trigger error
<27>Jul 29 23:50:34 node-4 multipathd: uevent trigger error
<43>Jul 29 23:50:37 node-4 apache2_error [Fri Jul 29 23:50:31.722450 2016] [mpm_worker:notice] [pid 9821:tid 140634042972032] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 23:50:37 node-4 apache2_error [Fri Jul 29 23:50:31.726786 2016] [mpm_worker:warn] [pid 9821:tid 140634042972032] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 23:50:37 node-4 apache2_error [Fri Jul 29 23:50:31.727206 2016] [mpm_worker:notice] [pid 9821:tid 140634042972032] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 23:50:37 node-4 apache2_error [Fri Jul 29 23:50:31.727213 2016] [core:notice] [pid 9821:tid 140634042972032] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 23:51:13 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 29 23:51:15 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:15 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:15 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:15 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:15 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:19 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:19 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:19 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:19 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:19 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:25 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:25 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:25 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:25 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:25 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:32 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:32 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:32 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:32 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:32 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:32 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:32 node-4 multipathd: uevent trigger error
<129>Jul 29 23:51:36 node-4 haproxy[22735]: 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 29 23:51:37 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:37 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:37 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:37 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:37 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:37 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:41 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:41 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:41 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:41 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:41 node-4 multipathd: uevent trigger error
<129>Jul 29 23:51:44 node-4 haproxy[24942]: 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 29 23:51:45 node-4 haproxy[24942]: 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 29 23:51:46 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:46 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:46 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:46 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:46 node-4 multipathd: uevent trigger error
<129>Jul 29 23:51:49 node-4 haproxy[26121]: 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 29 23:51:50 node-4 haproxy[26121]: 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 29 23:51:50 node-4 haproxy[26121]: 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 29 23:51:51 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:51 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:51 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:51 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:51 node-4 multipathd: uevent trigger error
<129>Jul 29 23:51:54 node-4 haproxy[27283]: 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 29 23:51:55 node-4 haproxy[27287]: 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 29 23:51:55 node-4 haproxy[27287]: 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 29 23:51:55 node-4 haproxy[27287]: 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 29 23:51:56 node-4 haproxy[27287]: 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 29 23:51:57 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:57 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:57 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:57 node-4 multipathd: uevent trigger error
<27>Jul 29 23:51:57 node-4 multipathd: uevent trigger error
<129>Jul 29 23:51:59 node-4 haproxy[28426]: 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 29 23:52:00 node-4 haproxy[28430]: 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 29 23:52:00 node-4 haproxy[28430]: 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 29 23:52:00 node-4 haproxy[28430]: 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 29 23:52:01 node-4 haproxy[28430]: 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 29 23:52:01 node-4 haproxy[28430]: 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 29 23:52:02 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:02 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:02 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:02 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:02 node-4 multipathd: uevent trigger error
<129>Jul 29 23:52:03 node-4 haproxy[28430]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:03 node-4 haproxy[28430]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:03 node-4 haproxy[28430]: proxy aodh has no server available!
<129>Jul 29 23:52:05 node-4 haproxy[29607]: 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 29 23:52:05 node-4 haproxy[29607]: 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 29 23:52:05 node-4 haproxy[29607]: 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 29 23:52:05 node-4 haproxy[29607]: 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 29 23:52:06 node-4 haproxy[29607]: 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 29 23:52:06 node-4 haproxy[29607]: 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 29 23:52:06 node-4 haproxy[29607]: 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 29 23:52:07 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:07 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:07 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:07 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:07 node-4 multipathd: uevent trigger error
<129>Jul 29 23:52:08 node-4 haproxy[29607]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:08 node-4 haproxy[29607]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:08 node-4 haproxy[29607]: proxy aodh has no server available!
<129>Jul 29 23:52:08 node-4 haproxy[29607]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:08 node-4 haproxy[29607]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:08 node-4 haproxy[29607]: proxy ceilometer has no server available!
<129>Jul 29 23:52:10 node-4 haproxy[30868]: 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 29 23:52:10 node-4 haproxy[30868]: 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 29 23:52:10 node-4 haproxy[30868]: 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 29 23:52:11 node-4 haproxy[30874]: 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 29 23:52:11 node-4 haproxy[30874]: 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 29 23:52:11 node-4 haproxy[30874]: 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 29 23:52:11 node-4 haproxy[30874]: 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 29 23:52:12 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:12 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:12 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:12 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:12 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:12 node-4 multipathd: uevent trigger error
<129>Jul 29 23:52:13 node-4 haproxy[30874]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:13 node-4 haproxy[30874]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:13 node-4 haproxy[30874]: proxy aodh has no server available!
<129>Jul 29 23:52:13 node-4 haproxy[30874]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:13 node-4 haproxy[30874]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:13 node-4 haproxy[30874]: proxy ceilometer has no server available!
<129>Jul 29 23:52:15 node-4 haproxy[32011]: 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 29 23:52:15 node-4 haproxy[32011]: 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 29 23:52:15 node-4 haproxy[32011]: 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 29 23:52:16 node-4 haproxy[32011]: 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 29 23:52:16 node-4 haproxy[32011]: 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 29 23:52:16 node-4 haproxy[32011]: 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 29 23:52:16 node-4 haproxy[32011]: 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 29 23:52:16 node-4 haproxy[32011]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:17 node-4 haproxy[32011]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 23:52:17 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:17 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:17 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:17 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:17 node-4 multipathd: uevent trigger error
<129>Jul 29 23:52:18 node-4 haproxy[32011]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:18 node-4 haproxy[32011]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:18 node-4 haproxy[32011]: proxy aodh has no server available!
<129>Jul 29 23:52:18 node-4 haproxy[32011]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:18 node-4 haproxy[32011]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:18 node-4 haproxy[32011]: proxy ceilometer has no server available!
<129>Jul 29 23:52:20 node-4 haproxy[963]: 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 29 23:52:20 node-4 haproxy[963]: 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 29 23:52:20 node-4 haproxy[963]: 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 29 23:52:21 node-4 haproxy[967]: 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 29 23:52:21 node-4 haproxy[967]: 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 29 23:52:21 node-4 haproxy[967]: 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 29 23:52:21 node-4 haproxy[967]: 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 29 23:52:21 node-4 haproxy[967]: 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 29 23:52:22 node-4 haproxy[967]: 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 29 23:52:22 node-4 haproxy[967]: 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 29 23:52:22 node-4 haproxy[967]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:22 node-4 haproxy[967]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:23 node-4 haproxy[967]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:23 node-4 haproxy[967]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:23 node-4 haproxy[967]: proxy glance-registry has no server available!
<129>Jul 29 23:52:23 node-4 haproxy[967]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:23 node-4 haproxy[967]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:23 node-4 haproxy[967]: proxy aodh has no server available!
<129>Jul 29 23:52:24 node-4 haproxy[967]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:24 node-4 haproxy[967]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:24 node-4 haproxy[967]: proxy ceilometer has no server available!
<27>Jul 29 23:52:24 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:24 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:24 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:24 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:24 node-4 multipathd: uevent trigger error
<129>Jul 29 23:52:27 node-4 haproxy[2119]: 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 29 23:52:27 node-4 haproxy[2119]: 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 29 23:52:27 node-4 haproxy[2119]: 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 29 23:52:27 node-4 haproxy[2119]: 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 29 23:52:28 node-4 haproxy[2128]: 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 29 23:52:28 node-4 haproxy[2128]: 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 29 23:52:28 node-4 haproxy[2128]: 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 29 23:52:28 node-4 haproxy[2128]: 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 29 23:52:28 node-4 haproxy[2128]: 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 29 23:52:28 node-4 haproxy[2128]: 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 29 23:52:28 node-4 haproxy[2128]: 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 29 23:52:29 node-4 haproxy[2128]: 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 29 23:52:29 node-4 haproxy[2128]: 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 29 23:52:29 node-4 haproxy[2128]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:29 node-4 haproxy[2128]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 23:52:30 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:30 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:30 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:30 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:30 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:30 node-4 multipathd: uevent trigger error
<129>Jul 29 23:52:30 node-4 haproxy[2128]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:30 node-4 haproxy[2128]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:30 node-4 haproxy[2128]: proxy glance-registry has no server available!
<129>Jul 29 23:52:30 node-4 haproxy[2128]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:30 node-4 haproxy[2128]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:30 node-4 haproxy[2128]: proxy aodh has no server available!
<129>Jul 29 23:52:30 node-4 haproxy[2128]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:30 node-4 haproxy[2128]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:30 node-4 haproxy[2128]: proxy ceilometer has no server available!
<129>Jul 29 23:52:31 node-4 haproxy[2128]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:31 node-4 haproxy[2128]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:31 node-4 haproxy[2128]: proxy nova-novncproxy has no server available!
<129>Jul 29 23:52:32 node-4 haproxy[3270]: 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 29 23:52:32 node-4 haproxy[3270]: 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 29 23:52:32 node-4 haproxy[3270]: 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 29 23:52:32 node-4 haproxy[3270]: 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 29 23:52:33 node-4 haproxy[3274]: 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 29 23:52:33 node-4 haproxy[3274]: 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 29 23:52:33 node-4 haproxy[3274]: 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 29 23:52:33 node-4 haproxy[3274]: 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 29 23:52:33 node-4 haproxy[3274]: 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 29 23:52:33 node-4 haproxy[3274]: 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 29 23:52:33 node-4 haproxy[3274]: 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 29 23:52:34 node-4 haproxy[3274]: 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 29 23:52:34 node-4 haproxy[3274]: 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 29 23:52:34 node-4 haproxy[3274]: 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 29 23:52:34 node-4 haproxy[3274]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:34 node-4 haproxy[3274]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 23:52:35 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:35 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:35 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:35 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:35 node-4 multipathd: uevent trigger error
<129>Jul 29 23:52:35 node-4 haproxy[3274]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:35 node-4 haproxy[3274]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:35 node-4 haproxy[3274]: proxy glance-registry has no server available!
<129>Jul 29 23:52:35 node-4 haproxy[3274]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:36 node-4 haproxy[3274]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:36 node-4 haproxy[3274]: proxy aodh has no server available!
<129>Jul 29 23:52:36 node-4 haproxy[3274]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:36 node-4 haproxy[3274]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:36 node-4 haproxy[3274]: proxy ceilometer has no server available!
<129>Jul 29 23:52:36 node-4 haproxy[3274]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:36 node-4 haproxy[3274]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:36 node-4 haproxy[3274]: proxy nova-novncproxy has no server available!
<129>Jul 29 23:52:38 node-4 haproxy[4464]: 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 29 23:52:38 node-4 haproxy[4464]: 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 29 23:52:38 node-4 haproxy[4464]: 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 29 23:52:38 node-4 haproxy[4464]: 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 29 23:52:38 node-4 haproxy[4464]: 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 29 23:52:38 node-4 haproxy[4464]: 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 29 23:52:38 node-4 haproxy[4464]: 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 29 23:52:39 node-4 haproxy[4468]: 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 29 23:52:39 node-4 haproxy[4468]: 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 29 23:52:39 node-4 haproxy[4468]: 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 29 23:52:39 node-4 haproxy[4468]: 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 29 23:52:39 node-4 haproxy[4468]: 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 29 23:52:39 node-4 haproxy[4468]: 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 29 23:52:39 node-4 haproxy[4468]: 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 29 23:52:39 node-4 haproxy[4468]: 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 29 23:52:40 node-4 haproxy[4468]: 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 29 23:52:40 node-4 haproxy[4468]: 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 29 23:52:40 node-4 haproxy[4468]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:40 node-4 haproxy[4468]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 23:52:41 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:41 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:41 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:41 node-4 multipathd: uevent trigger error
<129>Jul 29 23:52:41 node-4 haproxy[4468]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:41 node-4 haproxy[4468]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:41 node-4 haproxy[4468]: proxy glance-registry has no server available!
<129>Jul 29 23:52:41 node-4 haproxy[4468]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:41 node-4 haproxy[4468]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:41 node-4 haproxy[4468]: proxy aodh has no server available!
<129>Jul 29 23:52:41 node-4 haproxy[4468]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:41 node-4 haproxy[4468]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:41 node-4 haproxy[4468]: proxy ceilometer has no server available!
<129>Jul 29 23:52:42 node-4 haproxy[4468]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:42 node-4 haproxy[4468]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:42 node-4 haproxy[4468]: proxy nova-novncproxy has no server available!
<27>Jul 29 23:52:44 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:44 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:44 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:44 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:44 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:44 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:45 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 29 23:52:47 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:47 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:47 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:47 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:47 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:47 node-4 multipathd: uevent trigger error
<129>Jul 29 23:52:48 node-4 haproxy[4468]: Server keystone-1/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:48 node-4 haproxy[4468]: 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 29 23:52:48 node-4 haproxy[4468]: proxy keystone-1 has no server available!
<129>Jul 29 23:52:48 node-4 haproxy[4468]: Server keystone-2/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:48 node-4 haproxy[4468]: Server keystone-2/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:48 node-4 haproxy[4468]: proxy keystone-2 has no server available!
<129>Jul 29 23:52:48 node-4 haproxy[4468]: Server nova-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:48 node-4 haproxy[4468]: 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 29 23:52:48 node-4 haproxy[4468]: proxy nova-api has no server available!
<129>Jul 29 23:52:48 node-4 haproxy[4468]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:48 node-4 haproxy[4468]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:48 node-4 haproxy[4468]: proxy nova-metadata-api has no server available!
<129>Jul 29 23:52:48 node-4 haproxy[4468]: Server cinder-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10002ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:48 node-4 haproxy[4468]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:48 node-4 haproxy[4468]: proxy cinder-api has no server available!
<129>Jul 29 23:52:48 node-4 haproxy[4468]: Server glance-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:48 node-4 haproxy[4468]: Server glance-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:48 node-4 haproxy[4468]: proxy glance-api has no server available!
<129>Jul 29 23:52:48 node-4 haproxy[4468]: Server glance-glare/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:48 node-4 haproxy[4468]: Server glance-glare/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:48 node-4 haproxy[4468]: proxy glance-glare has no server available!
<129>Jul 29 23:52:49 node-4 haproxy[4468]: Server neutron/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:49 node-4 haproxy[4468]: Server neutron/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:49 node-4 haproxy[4468]: proxy neutron has no server available!
<129>Jul 29 23:52:49 node-4 haproxy[4468]: Server mysqld/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:49 node-4 haproxy[4468]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:49 node-4 haproxy[4468]: proxy mysqld has no server available!
<129>Jul 29 23:52:49 node-4 haproxy[4468]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:49 node-4 haproxy[4468]: Server object-storage/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:49 node-4 haproxy[4468]: proxy object-storage has no server available!
<129>Jul 29 23:52:49 node-4 haproxy[4468]: Server heat-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:49 node-4 haproxy[4468]: 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 29 23:52:49 node-4 haproxy[4468]: proxy heat-api has no server available!
<129>Jul 29 23:52:49 node-4 haproxy[4468]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:49 node-4 haproxy[4468]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 23:52:49 node-4 haproxy[4468]: proxy heat-api-cfn has no server available!
<129>Jul 29 23:52:49 node-4 haproxy[4468]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 23:52:49 node-4 haproxy[4468]: 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 29 23:52:49 node-4 haproxy[4468]: proxy heat-api-cloudwatch has no server available!
<27>Jul 29 23:52:51 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:51 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:51 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:51 node-4 multipathd: uevent trigger error
<27>Jul 29 23:52:51 node-4 multipathd: uevent trigger error
<27>Jul 29 23:53:10 node-4 multipathd: uevent trigger error
<27>Jul 29 23:53:42 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 29 23:53:42 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 29 23:54:11 node-4 multipathd: uevent trigger error
<27>Jul 29 23:54:11 node-4 multipathd: uevent trigger error
<27>Jul 29 23:54:11 node-4 multipathd: uevent trigger error
<27>Jul 29 23:54:11 node-4 multipathd: uevent trigger error
<27>Jul 29 23:54:11 node-4 multipathd: uevent trigger error
<27>Jul 29 23:54:17 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 29 23:55:17 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 29 23:55:19 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 29 23:56:34 node-4 multipathd: uevent trigger error
<27>Jul 29 23:56:34 node-4 multipathd: uevent trigger error
<27>Jul 29 23:56:34 node-4 multipathd: uevent trigger error
<27>Jul 29 23:56:34 node-4 multipathd: uevent trigger error
<27>Jul 29 23:56:34 node-4 multipathd: uevent trigger error
<27>Jul 29 23:56:34 node-4 multipathd: uevent trigger error
<27>Jul 29 23:59:50 node-4 multipathd: uevent trigger error
<27>Jul 29 23:59:50 node-4 multipathd: uevent trigger error
<27>Jul 29 23:59:50 node-4 multipathd: uevent trigger error
<27>Jul 29 23:59:50 node-4 multipathd: uevent trigger error
<27>Jul 29 23:59:50 node-4 multipathd: uevent trigger error
<43>Jul 30 00:01:08 node-4 apache2_error [Sat Jul 30 00:01:03.538259 2016] [mpm_worker:notice] [pid 9821:tid 140634042972032] AH00295: caught SIGTERM, shutting down
<43>Jul 30 00:01:08 node-4 apache2_error [Sat Jul 30 00:01:04.282674 2016] [mpm_worker:notice] [pid 8853:tid 140402278774656] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 00:01:08 node-4 apache2_error [Sat Jul 30 00:01:04.282700 2016] [core:notice] [pid 8853:tid 140402278774656] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 30 00:01:38 node-4 apache2_error [Sat Jul 30 00:01:36.193752 2016] [mpm_worker:notice] [pid 8853:tid 140402278774656] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 00:01:38 node-4 apache2_error [Sat Jul 30 00:01:36.202642 2016] [mpm_worker:warn] [pid 8853:tid 140402278774656] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 00:01:38 node-4 apache2_error [Sat Jul 30 00:01:36.206898 2016] [mpm_worker:notice] [pid 8853:tid 140402278774656] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 00:01:38 node-4 apache2_error [Sat Jul 30 00:01:36.206925 2016] [core:notice] [pid 8853:tid 140402278774656] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 00:01:41 node-4 multipathd: uevent trigger error
<27>Jul 30 00:01:41 node-4 multipathd: uevent trigger error
<27>Jul 30 00:01:41 node-4 multipathd: uevent trigger error
<27>Jul 30 00:01:41 node-4 multipathd: uevent trigger error
<27>Jul 30 00:01:42 node-4 multipathd: uevent trigger error
<27>Jul 30 00:01:42 node-4 multipathd: uevent trigger error
<27>Jul 30 00:02:31 node-4 multipathd: uevent trigger error
<27>Jul 30 00:02:31 node-4 multipathd: uevent trigger error
<27>Jul 30 00:02:31 node-4 multipathd: uevent trigger error
<27>Jul 30 00:02:31 node-4 multipathd: uevent trigger error
<27>Jul 30 00:02:31 node-4 multipathd: uevent trigger error
<27>Jul 30 00:03:45 node-4 multipathd: uevent trigger error
<27>Jul 30 00:03:45 node-4 multipathd: uevent trigger error
<27>Jul 30 00:03:45 node-4 multipathd: uevent trigger error
<27>Jul 30 00:03:45 node-4 multipathd: uevent trigger error
<27>Jul 30 00:03:45 node-4 multipathd: uevent trigger error
<27>Jul 30 00:09:18 node-4 multipathd: uevent trigger error
<27>Jul 30 00:09:18 node-4 multipathd: uevent trigger error
<27>Jul 30 00:09:18 node-4 multipathd: uevent trigger error
<27>Jul 30 00:09:18 node-4 multipathd: uevent trigger error
<27>Jul 30 00:09:18 node-4 multipathd: uevent trigger error
<27>Jul 30 00:09:18 node-4 multipathd: uevent trigger error
<27>Jul 30 00:11:30 node-4 multipathd: uevent trigger error
<27>Jul 30 00:11:30 node-4 multipathd: uevent trigger error
<27>Jul 30 00:11:30 node-4 multipathd: uevent trigger error
<27>Jul 30 00:11:30 node-4 multipathd: uevent trigger error
<27>Jul 30 00:11:30 node-4 multipathd: uevent trigger error
<27>Jul 30 00:12:39 node-4 multipathd: uevent trigger error
<27>Jul 30 00:12:39 node-4 multipathd: uevent trigger error
<27>Jul 30 00:12:39 node-4 multipathd: uevent trigger error
<27>Jul 30 00:12:39 node-4 multipathd: uevent trigger error
<27>Jul 30 00:12:39 node-4 multipathd: uevent trigger error
<27>Jul 30 00:12:39 node-4 multipathd: uevent trigger error
<27>Jul 30 00:12:39 node-4 multipathd: uevent trigger error
<27>Jul 30 00:12:39 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:14 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:14 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:14 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:14 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:14 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:14 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:24 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:24 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:24 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:24 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:24 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:24 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:36 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Jul 30 00:13:36 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Jul 30 00:13:37 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Jul 30 00:13:38 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Jul 30 00:13:38 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Jul 30 00:13:38 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:38 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:38 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:38 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:38 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:38 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:38 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:56 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:56 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:56 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:56 node-4 multipathd: uevent trigger error
<27>Jul 30 00:13:56 node-4 multipathd: uevent trigger error
<27>Jul 30 00:14:02 node-4 multipathd: uevent trigger error
<27>Jul 30 00:14:02 node-4 multipathd: uevent trigger error
<27>Jul 30 00:14:02 node-4 multipathd: uevent trigger error
<27>Jul 30 00:14:02 node-4 multipathd: uevent trigger error
<27>Jul 30 00:14:02 node-4 multipathd: uevent trigger error
<43>Jul 30 00:14:49 node-4 apache2_error [Sat Jul 30 00:14:48.270950 2016] [mpm_worker:notice] [pid 8853:tid 140402278774656] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 00:14:49 node-4 apache2_error [Sat Jul 30 00:14:48.654911 2016] [mpm_worker:warn] [pid 8853:tid 140402278774656] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 00:14:49 node-4 apache2_error [Sat Jul 30 00:14:48.659606 2016] [mpm_worker:notice] [pid 8853:tid 140402278774656] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 00:14:49 node-4 apache2_error [Sat Jul 30 00:14:48.659628 2016] [core:notice] [pid 8853:tid 140402278774656] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 00:15:29 node-4 multipathd: uevent trigger error
<27>Jul 30 00:15:29 node-4 multipathd: uevent trigger error
<27>Jul 30 00:15:29 node-4 multipathd: uevent trigger error
<27>Jul 30 00:15:29 node-4 multipathd: uevent trigger error
<27>Jul 30 00:15:29 node-4 multipathd: uevent trigger error
<27>Jul 30 00:15:29 node-4 multipathd: uevent trigger error
<43>Jul 30 00:15:29 node-4 apache2_error [Sat Jul 30 00:15:25.394116 2016] [mpm_worker:notice] [pid 8853:tid 140402278774656] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 00:15:29 node-4 apache2_error [Sat Jul 30 00:15:25.778060 2016] [mpm_worker:warn] [pid 8853:tid 140402278774656] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 00:15:29 node-4 apache2_error [Sat Jul 30 00:15:25.788767 2016] [mpm_worker:notice] [pid 8853:tid 140402278774656] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 00:15:29 node-4 apache2_error [Sat Jul 30 00:15:25.788805 2016] [core:notice] [pid 8853:tid 140402278774656] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 00:15:45 node-4 multipathd: uevent trigger error
<27>Jul 30 00:15:45 node-4 multipathd: uevent trigger error
<27>Jul 30 00:15:45 node-4 multipathd: uevent trigger error
<27>Jul 30 00:15:59 node-4 multipathd: uevent trigger error
<27>Jul 30 00:15:59 node-4 multipathd: uevent trigger error
<27>Jul 30 00:15:59 node-4 multipathd: uevent trigger error
<27>Jul 30 00:15:59 node-4 multipathd: uevent trigger error
<27>Jul 30 00:15:59 node-4 multipathd: uevent trigger error
<27>Jul 30 00:15:59 node-4 multipathd: uevent trigger error
<27>Jul 30 00:15:59 node-4 multipathd: uevent trigger error
<27>Jul 30 00:15:59 node-4 multipathd: sda: spurious uevent, path already in pathvec
<27>Jul 30 00:16:47 node-4 multipathd: uevent trigger error
<27>Jul 30 00:16:47 node-4 multipathd: uevent trigger error
<27>Jul 30 00:16:47 node-4 multipathd: uevent trigger error
<27>Jul 30 00:16:47 node-4 multipathd: uevent trigger error
<27>Jul 30 00:16:47 node-4 multipathd: uevent trigger error
<27>Jul 30 00:16:59 node-4 multipathd: uevent trigger error
<27>Jul 30 00:16:59 node-4 multipathd: uevent trigger error
<27>Jul 30 00:16:59 node-4 multipathd: uevent trigger error
<27>Jul 30 00:16:59 node-4 multipathd: uevent trigger error
<27>Jul 30 00:16:59 node-4 multipathd: uevent trigger error
<27>Jul 30 00:16:59 node-4 multipathd: uevent trigger error
<27>Jul 30 00:17:03 node-4 multipathd: uevent trigger error
<27>Jul 30 00:17:03 node-4 multipathd: uevent trigger error
<27>Jul 30 00:17:04 node-4 multipathd: uevent trigger error
<27>Jul 30 00:17:04 node-4 multipathd: uevent trigger error
<27>Jul 30 00:17:04 node-4 multipathd: uevent trigger error
<27>Jul 30 00:17:12 node-4 multipathd: uevent trigger error
<27>Jul 30 00:17:12 node-4 multipathd: uevent trigger error
<27>Jul 30 00:17:12 node-4 multipathd: uevent trigger error
<27>Jul 30 00:17:12 node-4 multipathd: uevent trigger error
<27>Jul 30 00:17:12 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:01 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:01 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:01 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:01 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:01 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:14 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:14 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:14 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:14 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:14 node-4 multipathd: uevent trigger error
<11>Jul 30 00:18:23 node-4 liberasurecode[73033]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:23 node-4 liberasurecode[73033]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:23 node-4 liberasurecode[73033]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:23 node-4 liberasurecode[73033]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:23 node-4 liberasurecode[73152]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:23 node-4 liberasurecode[73152]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:23 node-4 liberasurecode[73152]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:23 node-4 liberasurecode[73152]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:25 node-4 liberasurecode[74134]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:25 node-4 liberasurecode[74134]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:25 node-4 liberasurecode[74134]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:25 node-4 liberasurecode[74134]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[74886]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[74886]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[74886]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[74886]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[74927]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[74927]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[74927]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[74927]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[74965]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[74965]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[74965]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[74965]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[75051]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[75051]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[75051]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[75051]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[75067]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[75067]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[75067]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[75067]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[75079]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[75079]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[75079]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[75079]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[75091]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[75091]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[75091]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:18:31 node-4 liberasurecode[75091]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 30 00:18:37 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:37 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:37 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:37 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:37 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:43 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:43 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:43 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:43 node-4 multipathd: uevent trigger error
<27>Jul 30 00:18:43 node-4 multipathd: uevent trigger error
<27>Jul 30 00:19:50 node-4 multipathd: uevent trigger error
<27>Jul 30 00:19:50 node-4 multipathd: uevent trigger error
<27>Jul 30 00:19:50 node-4 multipathd: uevent trigger error
<27>Jul 30 00:19:50 node-4 multipathd: uevent trigger error
<27>Jul 30 00:19:50 node-4 multipathd: uevent trigger error
<11>Jul 30 00:20:01 node-4 liberasurecode[90132]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:20:01 node-4 liberasurecode[90132]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:20:01 node-4 liberasurecode[90132]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:20:01 node-4 liberasurecode[90132]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 30 00:21:50 node-4 multipathd: uevent trigger error
<27>Jul 30 00:21:50 node-4 multipathd: uevent trigger error
<27>Jul 30 00:21:50 node-4 multipathd: uevent trigger error
<27>Jul 30 00:21:50 node-4 multipathd: uevent trigger error
<27>Jul 30 00:21:50 node-4 multipathd: uevent trigger error
<27>Jul 30 00:21:56 node-4 multipathd: uevent trigger error
<27>Jul 30 00:21:56 node-4 multipathd: uevent trigger error
<27>Jul 30 00:21:56 node-4 multipathd: uevent trigger error
<27>Jul 30 00:21:56 node-4 multipathd: uevent trigger error
<27>Jul 30 00:21:56 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:09 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:09 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:09 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:09 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:09 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:09 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:14 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:14 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:14 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:14 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:14 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:29 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:29 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:29 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:29 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:29 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:37 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:37 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:37 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:37 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:37 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:41 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:41 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:41 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:41 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:41 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:45 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:45 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:46 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:46 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:46 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:46 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:50 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:50 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:50 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:50 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:50 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:55 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:55 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:55 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:55 node-4 multipathd: uevent trigger error
<27>Jul 30 00:22:55 node-4 multipathd: uevent trigger error
<27>Jul 30 00:23:24 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 30 00:23:24 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<11>Jul 30 00:25:01 node-4 liberasurecode[136902]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:25:01 node-4 liberasurecode[136902]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:25:01 node-4 liberasurecode[136902]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 00:25:01 node-4 liberasurecode[136902]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
