Sep 18 11:19:00 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8391" x-info="http://www.rsyslog.com"] start
Sep 18 11:19:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 18 11:19:00 node-4 rsyslogd: rsyslogd's groupid changed to 104
Sep 18 11:19:00 node-4 rsyslogd: rsyslogd's userid changed to 101
Sep 18 11:19:00 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 18 11:19:00 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 18 11:19:00 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 18 11:19:00 node-4 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep 18 11:19:00 node-4 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=8464d10e-19b0-4bd4-aa70-a1e3fc658b0b nomdmonddf nomdmonisw
Sep 18 11:19:00 node-4 kernel: [    0.000000] KERNEL supported cpus:
Sep 18 11:19:00 node-4 kernel: [    0.000000]   Intel GenuineIntel
Sep 18 11:19:00 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Sep 18 11:19:00 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Sep 18 11:19:00 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 18 11:19:00 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 18 11:19:00 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 18 11:19:00 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 18 11:19:00 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Sep 18 11:19:00 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Sep 18 11:19:00 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Sep 18 11:19:00 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Sep 18 11:19:00 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Sep 18 11:19:00 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 18 11:19:00 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 18 11:19:00 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 18 11:19:00 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 18 11:19:00 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 18 11:19:00 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 18 11:19:00 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 18 11:19:00 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 18 11:19:00 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 18 11:19:00 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
Sep 18 11:19:00 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 18 11:19:00 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 18 11:19:00 node-4 kernel: [    0.000000] No AGP bridge found
Sep 18 11:19:00 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 18 11:19:00 node-4 kernel: [    0.000000] MTRR default type: write-back
Sep 18 11:19:00 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 18 11:19:00 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Sep 18 11:19:00 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 18 11:19:00 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 18 11:19:00 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 18 11:19:00 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 18 11:19:00 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 18 11:19:00 node-4 kernel: [    0.000000]   2 disabled
Sep 18 11:19:00 node-4 kernel: [    0.000000]   3 disabled
Sep 18 11:19:00 node-4 kernel: [    0.000000]   4 disabled
Sep 18 11:19:00 node-4 kernel: [    0.000000]   5 disabled
Sep 18 11:19:00 node-4 kernel: [    0.000000]   6 disabled
Sep 18 11:19:00 node-4 kernel: [    0.000000]   7 disabled
Sep 18 11:19:00 node-4 kernel: [    0.000000]   8 disabled
Sep 18 11:19:00 node-4 kernel: [    0.000000]   9 disabled
Sep 18 11:19:00 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 18 11:19:00 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 18 11:19:00 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 18 11:19:00 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 18 11:19:00 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 18 11:19:00 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Sep 18 11:19:00 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 18 11:19:00 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 18 11:19:00 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 18 11:19:00 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 18 11:19:00 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 18 11:19:00 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 18 11:19:00 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 18 11:19:00 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 18 11:19:00 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 18 11:19:00 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Sep 18 11:19:00 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 18 11:19:00 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 18 11:19:00 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 18 11:19:00 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 18 11:19:00 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 18 11:19:00 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 18 11:19:00 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 18 11:19:00 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 18 11:19:00 node-4 kernel: [    0.000000] Zone ranges:
Sep 18 11:19:00 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] Movable zone start for each node
Sep 18 11:19:00 node-4 kernel: [    0.000000] Early memory node ranges
Sep 18 11:19:00 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] On node 0 totalpages: 4125855
Sep 18 11:19:00 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 18 11:19:00 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 18 11:19:00 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 18 11:19:00 node-4 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Sep 18 11:19:00 node-4 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Sep 18 11:19:00 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 18 11:19:00 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 18 11:19:00 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 18 11:19:00 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 18 11:19:00 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 18 11:19:00 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 18 11:19:00 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 18 11:19:00 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 18 11:19:00 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 18 11:19:00 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 18 11:19:00 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 18 11:19:00 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 18 11:19:00 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 18 11:19:00 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 18 11:19:00 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 18 11:19:00 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 18 11:19:00 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 18 11:19:00 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 18 11:19:00 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 
Sep 18 11:19:00 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Sep 18 11:19:00 node-4 kernel: [    0.000000] Policy zone: Normal
Sep 18 11:19:00 node-4 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=8464d10e-19b0-4bd4-aa70-a1e3fc658b0b nomdmonddf nomdmonisw
Sep 18 11:19:00 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 18 11:19:00 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 18 11:19:00 node-4 kernel: [    0.000000] Checking aperture...
Sep 18 11:19:00 node-4 kernel: [    0.000000] No AGP bridge found
Sep 18 11:19:00 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 18 11:19:00 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 18 11:19:00 node-4 kernel: [    0.000000] Memory: 32653460K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Sep 18 11:19:00 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 18 11:19:00 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 18 11:19:00 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 18 11:19:00 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 18 11:19:00 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 18 11:19:00 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 18 11:19:00 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 18 11:19:00 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 18 11:19:00 node-4 kernel: [    0.000000] console [tty0] enabled
Sep 18 11:19:00 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 18 11:19:00 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 18 11:19:00 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 18 11:19:00 node-4 kernel: [    0.000000] hpet clockevent registered
Sep 18 11:19:00 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 18 11:19:00 node-4 kernel: [    0.004000] tsc: Detected 3491.833 MHz processor
Sep 18 11:19:00 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.66 BogoMIPS (lpj=13967332)
Sep 18 11:19:00 node-4 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 18 11:19:00 node-4 kernel: [    0.000043] Security Framework initialized
Sep 18 11:19:00 node-4 kernel: [    0.000061] AppArmor: AppArmor initialized
Sep 18 11:19:00 node-4 kernel: [    0.000062] Yama: becoming mindful.
Sep 18 11:19:00 node-4 kernel: [    0.001455] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 18 11:19:00 node-4 kernel: [    0.006399] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 18 11:19:00 node-4 kernel: [    0.008324] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 18 11:19:00 node-4 kernel: [    0.008352] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 18 11:19:00 node-4 kernel: [    0.008645] Initializing cgroup subsys memory
Sep 18 11:19:00 node-4 kernel: [    0.008653] Initializing cgroup subsys devices
Sep 18 11:19:00 node-4 kernel: [    0.008655] Initializing cgroup subsys freezer
Sep 18 11:19:00 node-4 kernel: [    0.008656] Initializing cgroup subsys blkio
Sep 18 11:19:00 node-4 kernel: [    0.008658] Initializing cgroup subsys perf_event
Sep 18 11:19:00 node-4 kernel: [    0.008660] Initializing cgroup subsys hugetlb
Sep 18 11:19:00 node-4 kernel: [    0.008679] CPU: Physical Processor ID: 0
Sep 18 11:19:00 node-4 kernel: [    0.008681] CPU: Processor Core ID: 0
Sep 18 11:19:00 node-4 kernel: [    0.008684] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 18 11:19:00 node-4 kernel: [    0.008684] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 18 11:19:00 node-4 kernel: [    0.009379] mce: CPU supports 22 MCE banks
Sep 18 11:19:00 node-4 kernel: [    0.009406] CPU0: Thermal monitoring enabled (TM1)
Sep 18 11:19:00 node-4 kernel: [    0.009427] process: using mwait in idle threads
Sep 18 11:19:00 node-4 kernel: [    0.009430] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 18 11:19:00 node-4 kernel: [    0.009430] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 18 11:19:00 node-4 kernel: [    0.009430] tlb_flushall_shift: 6
Sep 18 11:19:00 node-4 kernel: [    0.009518] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 18 11:19:00 node-4 kernel: [    0.010241] ACPI: Core revision 20131115
Sep 18 11:19:00 node-4 kernel: [    0.022895] ACPI: All ACPI Tables successfully acquired
Sep 18 11:19:00 node-4 kernel: [    0.023064] ftrace: allocating 28617 entries in 112 pages
Sep 18 11:19:00 node-4 kernel: [    0.032029] dmar: Host address width 46
Sep 18 11:19:00 node-4 kernel: [    0.032031] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 18 11:19:00 node-4 kernel: [    0.032037] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 18 11:19:00 node-4 kernel: [    0.032039] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 18 11:19:00 node-4 kernel: [    0.032043] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 18 11:19:00 node-4 kernel: [    0.032044] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 18 11:19:00 node-4 kernel: [    0.032045] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 18 11:19:00 node-4 kernel: [    0.032046] dmar: ATSR flags: 0x0
Sep 18 11:19:00 node-4 kernel: [    0.032047] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 18 11:19:00 node-4 kernel: [    0.032048] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 18 11:19:00 node-4 kernel: [    0.032164] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 18 11:19:00 node-4 kernel: [    0.032165] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 18 11:19:00 node-4 kernel: [    0.032166] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 18 11:19:00 node-4 kernel: [    0.032167] HPET id 0 under DRHD base 0xc7ffc000
Sep 18 11:19:00 node-4 kernel: [    0.032168] Your BIOS is broken and requested that x2apic be disabled.
Sep 18 11:19:00 node-4 kernel: [    0.032168] This will slightly decrease performance.
Sep 18 11:19:00 node-4 kernel: [    0.032168] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 18 11:19:00 node-4 kernel: [    0.032599] Enabled IRQ remapping in xapic mode
Sep 18 11:19:00 node-4 kernel: [    0.032601] x2apic not enabled, IRQ remapping is in xapic mode
Sep 18 11:19:00 node-4 kernel: [    0.032604] Switched APIC routing to physical flat.
Sep 18 11:19:00 node-4 kernel: [    0.033179] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 18 11:19:00 node-4 kernel: [    0.072828] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 18 11:19:00 node-4 kernel: [    0.072834] TSC deadline timer enabled
Sep 18 11:19:00 node-4 kernel: [    0.072841] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 18 11:19:00 node-4 kernel: [    0.072847] ... version:                3
Sep 18 11:19:00 node-4 kernel: [    0.072848] ... bit width:              48
Sep 18 11:19:00 node-4 kernel: [    0.072849] ... generic registers:      4
Sep 18 11:19:00 node-4 kernel: [    0.072850] ... value mask:             0000ffffffffffff
Sep 18 11:19:00 node-4 kernel: [    0.072851] ... max period:             0000ffffffffffff
Sep 18 11:19:00 node-4 kernel: [    0.072852] ... fixed-purpose events:   3
Sep 18 11:19:00 node-4 kernel: [    0.072853] ... event mask:             000000070000000f
Sep 18 11:19:00 node-4 kernel: [    0.074224] x86: Booting SMP configuration:
Sep 18 11:19:00 node-4 kernel: [    0.088331] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 18 11:19:00 node-4 kernel: [    0.074226] .... node  #0, CPUs:        #1  #2  #3
Sep 18 11:19:00 node-4 kernel: [    0.116235] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 18 11:19:00 node-4 kernel: [    0.270373] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 18 11:19:00 node-4 kernel: [    0.325988] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 18 11:19:00 node-4 kernel: [    0.383037] x86: Booted up 2 nodes, 16 CPUs
Sep 18 11:19:00 node-4 kernel: [    0.383041] smpboot: Total of 16 processors activated (111750.50 BogoMIPS)
Sep 18 11:19:00 node-4 kernel: [    0.406454] devtmpfs: initialized
Sep 18 11:19:00 node-4 kernel: [    0.409590] EVM: security.selinux
Sep 18 11:19:00 node-4 kernel: [    0.409592] EVM: security.SMACK64
Sep 18 11:19:00 node-4 kernel: [    0.409593] EVM: security.ima
Sep 18 11:19:00 node-4 kernel: [    0.409594] EVM: security.capability
Sep 18 11:19:00 node-4 kernel: [    0.409646] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Sep 18 11:19:00 node-4 kernel: [    0.410321] pinctrl core: initialized pinctrl subsystem
Sep 18 11:19:00 node-4 kernel: [    0.410384] regulator-dummy: no parameters
Sep 18 11:19:00 node-4 kernel: [    0.410416] RTC time: 11:18:23, date: 09/18/16
Sep 18 11:19:00 node-4 kernel: [    0.410450] NET: Registered protocol family 16
Sep 18 11:19:00 node-4 kernel: [    0.410534] cpuidle: using governor ladder
Sep 18 11:19:00 node-4 kernel: [    0.410536] cpuidle: using governor menu
Sep 18 11:19:00 node-4 kernel: [    0.410572] ACPI: bus type PCI registered
Sep 18 11:19:00 node-4 kernel: [    0.410573] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 18 11:19:00 node-4 kernel: [    0.410618] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 18 11:19:00 node-4 kernel: [    0.410620] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 18 11:19:00 node-4 kernel: [    0.424352] PCI: Using configuration type 1 for base access
Sep 18 11:19:00 node-4 kernel: [    0.425355] bio: create slab <bio-0> at 0
Sep 18 11:19:00 node-4 kernel: [    0.425631] ACPI: Added _OSI(Module Device)
Sep 18 11:19:00 node-4 kernel: [    0.425632] ACPI: Added _OSI(Processor Device)
Sep 18 11:19:00 node-4 kernel: [    0.425633] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 18 11:19:00 node-4 kernel: [    0.425635] ACPI: Added _OSI(Processor Aggregator Device)
Sep 18 11:19:00 node-4 kernel: [    0.438320] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 18 11:19:00 node-4 kernel: [    0.449867] ACPI: Interpreter enabled
Sep 18 11:19:00 node-4 kernel: [    0.449872] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 18 11:19:00 node-4 kernel: [    0.449876] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 18 11:19:00 node-4 kernel: [    0.449879] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 18 11:19:00 node-4 kernel: [    0.449886] ACPI: (supports S0 S4 S5)
Sep 18 11:19:00 node-4 kernel: [    0.449887] ACPI: Using IOAPIC for interrupt routing
Sep 18 11:19:00 node-4 kernel: [    0.449929] HEST: Table parsing has been initialized.
Sep 18 11:19:00 node-4 kernel: [    0.449932] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 18 11:19:00 node-4 kernel: [    0.450485] ACPI: No dock devices found.
Sep 18 11:19:00 node-4 kernel: [    0.462192] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 18 11:19:00 node-4 kernel: [    0.462197] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 18 11:19:00 node-4 kernel: [    0.462201] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 18 11:19:00 node-4 kernel: [    0.462229] PCI host bridge to bus 0000:ff
Sep 18 11:19:00 node-4 kernel: [    0.462231] pci_bus 0000:ff: root bus resource [bus ff]
Sep 18 11:19:00 node-4 kernel: [    0.462239] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462278] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 18 11:19:00 node-4 kernel: [    0.462309] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462345] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462375] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 18 11:19:00 node-4 kernel: [    0.462405] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 18 11:19:00 node-4 kernel: [    0.462437] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462466] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462498] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462527] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462554] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462581] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462610] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462636] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462663] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462691] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462720] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462748] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462775] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 18 11:19:00 node-4 kernel: [    0.462803] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462830] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 18 11:19:00 node-4 kernel: [    0.462857] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462883] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462914] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 18 11:19:00 node-4 kernel: [    0.462949] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.462981] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463011] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463043] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463074] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463106] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463137] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463168] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463199] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463231] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463265] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463298] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463333] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463362] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463390] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463422] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463455] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463494] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463529] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463563] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463594] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463625] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463657] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463689] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463725] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463758] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463791] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463822] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463852] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463883] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463913] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463946] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.463979] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464037] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 18 11:19:00 node-4 kernel: [    0.464040] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 18 11:19:00 node-4 kernel: [    0.464043] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 18 11:19:00 node-4 kernel: [    0.464062] PCI host bridge to bus 0000:7f
Sep 18 11:19:00 node-4 kernel: [    0.464063] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 18 11:19:00 node-4 kernel: [    0.464068] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464096] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 18 11:19:00 node-4 kernel: [    0.464123] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464159] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464182] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 18 11:19:00 node-4 kernel: [    0.464206] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 18 11:19:00 node-4 kernel: [    0.464231] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464255] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464277] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464300] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464322] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464344] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464368] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464390] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464413] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464438] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464460] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464483] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464505] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 18 11:19:00 node-4 kernel: [    0.464529] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464551] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 18 11:19:00 node-4 kernel: [    0.464573] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464595] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464621] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 18 11:19:00 node-4 kernel: [    0.464654] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464680] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464708] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464735] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464760] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464789] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464815] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464842] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464869] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464897] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464924] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464952] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.464980] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465004] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465029] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465056] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465082] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465109] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465139] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465168] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465192] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465217] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465244] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465272] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465299] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465326] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465356] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465382] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465405] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465430] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465456] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465485] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.465511] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.466754] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 18 11:19:00 node-4 kernel: [    0.466757] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 18 11:19:00 node-4 kernel: [    0.467887] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 18 11:19:00 node-4 kernel: [    0.468399] PCI host bridge to bus 0000:00
Sep 18 11:19:00 node-4 kernel: [    0.468401] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 18 11:19:00 node-4 kernel: [    0.468403] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 18 11:19:00 node-4 kernel: [    0.468404] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 18 11:19:00 node-4 kernel: [    0.468405] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 18 11:19:00 node-4 kernel: [    0.468407] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 18 11:19:00 node-4 kernel: [    0.468408] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 18 11:19:00 node-4 kernel: [    0.468410] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 18 11:19:00 node-4 kernel: [    0.468415] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 18 11:19:00 node-4 kernel: [    0.468498] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 18 11:19:00 node-4 kernel: [    0.468529] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:00 node-4 kernel: [    0.468570] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 18 11:19:00 node-4 kernel: [    0.468590] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 18 11:19:00 node-4 kernel: [    0.468619] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:00 node-4 kernel: [    0.468659] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 18 11:19:00 node-4 kernel: [    0.468677] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 18 11:19:00 node-4 kernel: [    0.468707] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:00 node-4 kernel: [    0.468747] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 18 11:19:00 node-4 kernel: [    0.468762] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.468832] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.468909] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.468985] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 18 11:19:00 node-4 kernel: [    0.468989] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 18 11:19:00 node-4 kernel: [    0.469074] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 18 11:19:00 node-4 kernel: [    0.469222] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 18 11:19:00 node-4 kernel: [    0.469239] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 18 11:19:00 node-4 kernel: [    0.469318] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:00 node-4 kernel: [    0.469371] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 18 11:19:00 node-4 kernel: [    0.469392] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 18 11:19:00 node-4 kernel: [    0.469448] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:00 node-4 kernel: [    0.469492] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 18 11:19:00 node-4 kernel: [    0.469519] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 18 11:19:00 node-4 kernel: [    0.469575] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 18 11:19:00 node-4 kernel: [    0.469618] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 18 11:19:00 node-4 kernel: [    0.469642] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 18 11:19:00 node-4 kernel: [    0.469659] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 18 11:19:00 node-4 kernel: [    0.469738] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:00 node-4 kernel: [    0.469787] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 18 11:19:00 node-4 kernel: [    0.469813] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 18 11:19:00 node-4 kernel: [    0.470061] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 18 11:19:00 node-4 kernel: [    0.470067] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 18 11:19:00 node-4 kernel: [    0.470073] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 18 11:19:00 node-4 kernel: [    0.470078] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 18 11:19:00 node-4 kernel: [    0.470086] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 18 11:19:00 node-4 kernel: [    0.470116] pci 0000:01:00.0: supports D1 D2
Sep 18 11:19:00 node-4 kernel: [    0.476153] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 18 11:19:00 node-4 kernel: [    0.476159] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 18 11:19:00 node-4 kernel: [    0.476163] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 18 11:19:00 node-4 kernel: [    0.476315] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 18 11:19:00 node-4 kernel: [    0.476348] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 18 11:19:00 node-4 kernel: [    0.484149] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 18 11:19:00 node-4 kernel: [    0.484156] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:00 node-4 kernel: [    0.484160] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 18 11:19:00 node-4 kernel: [    0.484244] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 18 11:19:00 node-4 kernel: [    0.484316] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 18 11:19:00 node-4 kernel: [    0.484422] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:00 node-4 kernel: [    0.484467] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 18 11:19:00 node-4 kernel: [    0.484471] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:00 node-4 kernel: [    0.484472] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 18 11:19:00 node-4 kernel: [    0.484525] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 18 11:19:00 node-4 kernel: [    0.484651] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:00 node-4 kernel: [    0.484704] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 18 11:19:00 node-4 kernel: [    0.484707] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:00 node-4 kernel: [    0.484709] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 18 11:19:00 node-4 kernel: [    0.484758] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 18 11:19:00 node-4 kernel: [    0.484877] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:00 node-4 kernel: [    0.484926] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 18 11:19:00 node-4 kernel: [    0.485047] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:00 node-4 kernel: [    0.485084] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 18 11:19:00 node-4 kernel: [    0.485204] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:00 node-4 kernel: [    0.485241] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 18 11:19:00 node-4 kernel: [    0.485360] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 18 11:19:00 node-4 kernel: [    0.485402] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 18 11:19:00 node-4 kernel: [    0.485405] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:00 node-4 kernel: [    0.485407] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 18 11:19:00 node-4 kernel: [    0.485466] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 18 11:19:00 node-4 kernel: [    0.485531] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 18 11:19:00 node-4 kernel: [    0.485583] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 18 11:19:00 node-4 kernel: [    0.485625] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 18 11:19:00 node-4 kernel: [    0.485707] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 18 11:19:00 node-4 kernel: [    0.485812] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 18 11:19:00 node-4 kernel: [    0.485815] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:00 node-4 kernel: [    0.485817] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 18 11:19:00 node-4 kernel: [    0.485872] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 18 11:19:00 node-4 kernel: [    0.485950] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 18 11:19:00 node-4 kernel: [    0.485998] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 18 11:19:00 node-4 kernel: [    0.486210] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 18 11:19:00 node-4 kernel: [    0.486214] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 18 11:19:00 node-4 kernel: [    0.486276] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 18 11:19:00 node-4 kernel: [    0.486330] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 18 11:19:00 node-4 kernel: [    0.486378] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 18 11:19:00 node-4 kernel: [    0.486589] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 18 11:19:00 node-4 kernel: [    0.486593] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 18 11:19:00 node-4 kernel: [    0.486651] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 18 11:19:00 node-4 kernel: [    0.486711] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 18 11:19:00 node-4 kernel: [    0.486763] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 18 11:19:00 node-4 kernel: [    0.487007] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 18 11:19:00 node-4 kernel: [    0.487011] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 18 11:19:00 node-4 kernel: [    0.487188] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 18 11:19:00 node-4 kernel: [    0.487227] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 18 11:19:00 node-4 kernel: [    0.487304] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 18 11:19:00 node-4 kernel: [    0.487322] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 18 11:19:00 node-4 kernel: [    0.487336] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 18 11:19:00 node-4 kernel: [    0.487349] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 18 11:19:00 node-4 kernel: [    0.487399] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 18 11:19:00 node-4 kernel: [    0.492153] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 18 11:19:00 node-4 kernel: [    0.492157] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 18 11:19:00 node-4 kernel: [    0.492189] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 18 11:19:00 node-4 kernel: [    0.492681] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 18 11:19:00 node-4 kernel: [    0.492684] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 18 11:19:00 node-4 kernel: [    0.492804] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 18 11:19:00 node-4 kernel: [    0.492910] PCI host bridge to bus 0000:80
Sep 18 11:19:00 node-4 kernel: [    0.492912] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 18 11:19:00 node-4 kernel: [    0.492913] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 18 11:19:00 node-4 kernel: [    0.492915] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 18 11:19:00 node-4 kernel: [    0.492923] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.492986] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.493052] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 18 11:19:00 node-4 kernel: [    0.493114] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 18 11:19:00 node-4 kernel: [    0.493119] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 18 11:19:00 node-4 kernel: [    0.493191] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 18 11:19:00 node-4 kernel: [    0.493488] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 18 11:19:00 node-4 kernel: [    0.493520] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 18 11:19:00 node-4 kernel: [    0.493550] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 18 11:19:00 node-4 kernel: [    0.493579] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 18 11:19:00 node-4 kernel: [    0.493609] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 18 11:19:00 node-4 kernel: [    0.493639] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 18 11:19:00 node-4 kernel: [    0.493669] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 18 11:19:00 node-4 kernel: [    0.493699] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 18 11:19:00 node-4 kernel: [    0.493783] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 18 11:19:00 node-4 kernel: [    0.493787] ACPI: \_SB_.UNC1: notify handler is installed
Sep 18 11:19:00 node-4 kernel: [    0.493788] ACPI: \_SB_.UNC0: notify handler is installed
Sep 18 11:19:00 node-4 kernel: [    0.493803] ACPI: \_SB_.PCI0: notify handler is installed
Sep 18 11:19:00 node-4 kernel: [    0.493856] ACPI: \_SB_.PCI1: notify handler is installed
Sep 18 11:19:00 node-4 kernel: [    0.493935] Found 4 acpi root devices
Sep 18 11:19:00 node-4 kernel: [    0.494041] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 18 11:19:00 node-4 kernel: [    0.494043] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 18 11:19:00 node-4 kernel: [    0.494044] vgaarb: loaded
Sep 18 11:19:00 node-4 kernel: [    0.494045] vgaarb: bridge control possible 0000:0c:00.0
Sep 18 11:19:00 node-4 kernel: [    0.494159] SCSI subsystem initialized
Sep 18 11:19:00 node-4 kernel: [    0.494225] libata version 3.00 loaded.
Sep 18 11:19:00 node-4 kernel: [    0.494240] ACPI: bus type USB registered
Sep 18 11:19:00 node-4 kernel: [    0.494250] usbcore: registered new interface driver usbfs
Sep 18 11:19:00 node-4 kernel: [    0.494255] usbcore: registered new interface driver hub
Sep 18 11:19:00 node-4 kernel: [    0.494280] usbcore: registered new device driver usb
Sep 18 11:19:00 node-4 kernel: [    0.494445] PCI: Using ACPI for IRQ routing
Sep 18 11:19:00 node-4 kernel: [    0.498057] PCI: pci_cache_line_size set to 64 bytes
Sep 18 11:19:00 node-4 kernel: [    0.498258] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 18 11:19:00 node-4 kernel: [    0.498259] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Sep 18 11:19:00 node-4 kernel: [    0.498260] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 18 11:19:00 node-4 kernel: [    0.498322] NetLabel: Initializing
Sep 18 11:19:00 node-4 kernel: [    0.498323] NetLabel:  domain hash size = 128
Sep 18 11:19:00 node-4 kernel: [    0.498324] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 18 11:19:00 node-4 kernel: [    0.498334] NetLabel:  unlabeled traffic allowed by default
Sep 18 11:19:00 node-4 kernel: [    0.498389] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 18 11:19:00 node-4 kernel: [    0.498393] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 18 11:19:00 node-4 kernel: [    0.500450] Switched to clocksource hpet
Sep 18 11:19:00 node-4 kernel: [    0.504350] AppArmor: AppArmor Filesystem Enabled
Sep 18 11:19:00 node-4 kernel: [    0.504365] pnp: PnP ACPI init
Sep 18 11:19:00 node-4 kernel: [    0.504371] ACPI: bus type PNP registered
Sep 18 11:19:00 node-4 kernel: [    0.504494] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 18 11:19:00 node-4 kernel: [    0.504502] pnp 00:01: [dma 4]
Sep 18 11:19:00 node-4 kernel: [    0.504514] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 18 11:19:00 node-4 kernel: [    0.504540] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 18 11:19:00 node-4 kernel: [    0.504559] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 18 11:19:00 node-4 kernel: [    0.504577] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 18 11:19:00 node-4 kernel: [    0.504610] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 18 11:19:00 node-4 kernel: [    0.504661] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 18 11:19:00 node-4 kernel: [    0.504663] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 18 11:19:00 node-4 kernel: [    0.504665] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 18 11:19:00 node-4 kernel: [    0.504666] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 18 11:19:00 node-4 kernel: [    0.504667] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 18 11:19:00 node-4 kernel: [    0.504672] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 18 11:19:00 node-4 kernel: [    0.504674] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 18 11:19:00 node-4 kernel: [    0.504675] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 18 11:19:00 node-4 kernel: [    0.504677] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 18 11:19:00 node-4 kernel: [    0.504678] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 18 11:19:00 node-4 kernel: [    0.504680] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 18 11:19:00 node-4 kernel: [    0.504681] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 18 11:19:00 node-4 kernel: [    0.504683] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 18 11:19:00 node-4 kernel: [    0.504685] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 18 11:19:00 node-4 kernel: [    0.504769] pnp 00:07: [dma 0 disabled]
Sep 18 11:19:00 node-4 kernel: [    0.504797] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 18 11:19:00 node-4 kernel: [    0.504872] pnp 00:08: [dma 0 disabled]
Sep 18 11:19:00 node-4 kernel: [    0.504903] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 18 11:19:00 node-4 kernel: [    0.504954] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 18 11:19:00 node-4 kernel: [    0.505304] pnp: PnP ACPI: found 10 devices
Sep 18 11:19:00 node-4 kernel: [    0.505306] ACPI: bus type PNP unregistered
Sep 18 11:19:00 node-4 kernel: [    0.511633] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 18 11:19:00 node-4 kernel: [    0.511635] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 18 11:19:00 node-4 kernel: [    0.511638] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 18 11:19:00 node-4 kernel: [    0.511642] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 18 11:19:00 node-4 kernel: [    0.511644] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:00 node-4 kernel: [    0.511659] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 18 11:19:00 node-4 kernel: [    0.511691] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 18 11:19:00 node-4 kernel: [    0.511706] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 18 11:19:00 node-4 kernel: [    0.511734] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 18 11:19:00 node-4 kernel: [    0.511749] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 18 11:19:00 node-4 kernel: [    0.511777] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 18 11:19:00 node-4 kernel: [    0.511792] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 18 11:19:00 node-4 kernel: [    0.511821] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 18 11:19:00 node-4 kernel: [    0.511823] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:00 node-4 kernel: [    0.511837] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 18 11:19:00 node-4 kernel: [    0.511866] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 18 11:19:00 node-4 kernel: [    0.511868] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:00 node-4 kernel: [    0.511883] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 18 11:19:00 node-4 kernel: [    0.511926] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 18 11:19:00 node-4 kernel: [    0.511928] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:00 node-4 kernel: [    0.511930] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 18 11:19:00 node-4 kernel: [    0.511934] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 18 11:19:00 node-4 kernel: [    0.511936] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 18 11:19:00 node-4 kernel: [    0.511939] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 18 11:19:00 node-4 kernel: [    0.511942] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 18 11:19:00 node-4 kernel: [    0.511947] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 18 11:19:00 node-4 kernel: [    0.511955] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 18 11:19:00 node-4 kernel: [    0.511958] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 18 11:19:00 node-4 kernel: [    0.511965] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 18 11:19:00 node-4 kernel: [    0.511966] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 18 11:19:00 node-4 kernel: [    0.511966] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 18 11:19:00 node-4 kernel: [    0.511967] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 18 11:19:00 node-4 kernel: [    0.511968] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 18 11:19:00 node-4 kernel: [    0.511969] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 18 11:19:00 node-4 kernel: [    0.511970] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 18 11:19:00 node-4 kernel: [    0.511971] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 18 11:19:00 node-4 kernel: [    0.511972] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 18 11:19:00 node-4 kernel: [    0.511973] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 18 11:19:00 node-4 kernel: [    0.511974] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 18 11:19:00 node-4 kernel: [    0.511974] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 18 11:19:00 node-4 kernel: [    0.511975] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 18 11:19:00 node-4 kernel: [    0.511976] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 18 11:19:00 node-4 kernel: [    0.511977] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 18 11:19:00 node-4 kernel: [    0.511978] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 18 11:19:00 node-4 kernel: [    0.511979] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 18 11:19:00 node-4 kernel: [    0.511980] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 18 11:19:00 node-4 kernel: [    0.511981] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 18 11:19:00 node-4 kernel: [    0.511982] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 18 11:19:00 node-4 kernel: [    0.511983] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 18 11:19:00 node-4 kernel: [    0.511984] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 18 11:19:00 node-4 kernel: [    0.511986] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 18 11:19:00 node-4 kernel: [    0.511987] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 18 11:19:00 node-4 kernel: [    0.512023] NET: Registered protocol family 2
Sep 18 11:19:00 node-4 kernel: [    0.512278] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 18 11:19:00 node-4 kernel: [    0.512616] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 18 11:19:00 node-4 kernel: [    0.512760] TCP: Hash tables configured (established 262144 bind 65536)
Sep 18 11:19:00 node-4 kernel: [    0.512796] TCP: reno registered
Sep 18 11:19:00 node-4 kernel: [    0.512827] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 18 11:19:00 node-4 kernel: [    0.512920] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 18 11:19:00 node-4 kernel: [    0.513067] NET: Registered protocol family 1
Sep 18 11:19:00 node-4 kernel: [    0.548554] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 18 11:19:00 node-4 kernel: [    0.548570] PCI: CLS 64 bytes, default 64
Sep 18 11:19:00 node-4 kernel: [    0.548644] Trying to unpack rootfs image as initramfs...
Sep 18 11:19:00 node-4 kernel: [    0.768835] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Sep 18 11:19:00 node-4 kernel: [    0.768888] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 18 11:19:00 node-4 kernel: [    0.768891] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Sep 18 11:19:00 node-4 kernel: [    0.769307] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:00 node-4 kernel: [    0.769313] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:00 node-4 kernel: [    0.769318] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:00 node-4 kernel: [    0.769323] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:00 node-4 kernel: [    0.769333] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:00 node-4 kernel: [    0.769344] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:00 node-4 kernel: [    0.769353] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:00 node-4 kernel: [    0.769362] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:00 node-4 kernel: [    0.769369] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:00 node-4 kernel: [    0.769379] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:00 node-4 kernel: [    0.769385] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:00 node-4 kernel: [    0.769391] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:00 node-4 kernel: [    0.769398] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:00 node-4 kernel: [    0.769406] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:00 node-4 kernel: [    0.769413] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:00 node-4 kernel: [    0.769421] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 18 11:19:00 node-4 kernel: [    0.769462] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 18 11:19:00 node-4 kernel: [    0.769466] Scanning for low memory corruption every 60 seconds
Sep 18 11:19:00 node-4 kernel: [    0.769766] Initialise system trusted keyring
Sep 18 11:19:00 node-4 kernel: [    0.769811] audit: initializing netlink socket (disabled)
Sep 18 11:19:00 node-4 kernel: [    0.769820] type=2000 audit(1474197503.724:1): initialized
Sep 18 11:19:00 node-4 kernel: [    0.787633] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 18 11:19:00 node-4 kernel: [    0.789110] zbud: loaded
Sep 18 11:19:00 node-4 kernel: [    0.789221] VFS: Disk quotas dquot_6.5.2
Sep 18 11:19:00 node-4 kernel: [    0.789260] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 18 11:19:00 node-4 kernel: [    0.789628] fuse init (API version 7.22)
Sep 18 11:19:00 node-4 kernel: [    0.789684] msgmni has been set to 32768
Sep 18 11:19:00 node-4 kernel: [    0.789731] Key type big_key registered
Sep 18 11:19:00 node-4 kernel: [    0.790291] Key type asymmetric registered
Sep 18 11:19:00 node-4 kernel: [    0.790293] Asymmetric key parser 'x509' registered
Sep 18 11:19:00 node-4 kernel: [    0.790316] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 18 11:19:00 node-4 kernel: [    0.790370] io scheduler noop registered
Sep 18 11:19:00 node-4 kernel: [    0.790371] io scheduler deadline registered (default)
Sep 18 11:19:00 node-4 kernel: [    0.790389] io scheduler cfq registered
Sep 18 11:19:00 node-4 kernel: [    0.790705] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    0.790796] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    0.790884] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    0.790971] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    0.791067] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    0.791134] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    0.791396] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 18 11:19:00 node-4 kernel: [    0.791414] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 18 11:19:00 node-4 kernel: [    0.791427] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 18 11:19:00 node-4 kernel: [    0.791437] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791439] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791441] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 18 11:19:00 node-4 kernel: [    0.791445] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791447] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791448] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791449] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791450] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791452] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791453] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791455] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791456] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791457] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791459] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791460] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791462] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 18 11:19:00 node-4 kernel: [    0.791466] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791468] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 18 11:19:00 node-4 kernel: [    0.791477] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791480] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 18 11:19:00 node-4 kernel: [    0.791489] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791491] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 18 11:19:00 node-4 kernel: [    0.791494] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 18 11:19:00 node-4 kernel: [    0.791506] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 18 11:19:00 node-4 kernel: [    0.791596] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 18 11:19:00 node-4 kernel: [    0.791600] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 18 11:19:00 node-4 kernel: [    0.791609] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 18 11:19:00 node-4 kernel: [    0.791645] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 18 11:19:00 node-4 kernel: [    0.791646] vesafb: scrolling: redraw
Sep 18 11:19:00 node-4 kernel: [    0.791647] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 18 11:19:00 node-4 kernel: [    0.812549] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 18 11:19:00 node-4 kernel: [    0.821065] Console: switching to colour frame buffer device 80x30
Sep 18 11:19:00 node-4 kernel: [    0.829748] fb0: VESA VGA frame buffer device
Sep 18 11:19:00 node-4 kernel: [    0.829945] intel_idle: MWAIT substates: 0x2120
Sep 18 11:19:00 node-4 kernel: [    0.829946] intel_idle: v0.4 model 0x3F
Sep 18 11:19:00 node-4 kernel: [    0.829947] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 18 11:19:00 node-4 kernel: [    0.830184] ipmi message handler version 39.2
Sep 18 11:19:00 node-4 kernel: [    0.830458] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 18 11:19:00 node-4 kernel: [    0.830897] ACPI: AC Adapter [P111] (on-line)
Sep 18 11:19:00 node-4 kernel: [    0.836133] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 18 11:19:00 node-4 kernel: [    0.847160] ACPI: Power Button [PWRB]
Sep 18 11:19:00 node-4 kernel: [    0.852926] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 18 11:19:00 node-4 kernel: [    0.864557] ACPI: Power Button [PWRF]
Sep 18 11:19:00 node-4 kernel: [    0.881964] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 18 11:19:00 node-4 kernel: [    0.893643] pstore: Registered erst as persistent store backend
Sep 18 11:19:00 node-4 kernel: [    0.899842] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 18 11:19:00 node-4 kernel: [    0.911808] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 18 11:19:00 node-4 kernel: [    0.938562] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 18 11:19:00 node-4 kernel: [    0.971842] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 18 11:19:00 node-4 kernel: [    0.986031] Linux agpgart interface v0.103
Sep 18 11:19:00 node-4 kernel: [    0.993643] brd: module loaded
Sep 18 11:19:00 node-4 kernel: [    1.000696] loop: module loaded
Sep 18 11:19:00 node-4 kernel: [    1.007409] libphy: Fixed MDIO Bus: probed
Sep 18 11:19:00 node-4 kernel: [    1.013879] tun: Universal TUN/TAP device driver, 1.6
Sep 18 11:19:00 node-4 kernel: [    1.020341] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 18 11:19:00 node-4 kernel: [    1.026861] PPP generic driver version 2.4.2
Sep 18 11:19:00 node-4 kernel: [    1.033236] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 18 11:19:00 node-4 kernel: [    1.039667] ehci-pci: EHCI PCI platform driver
Sep 18 11:19:00 node-4 kernel: [    1.046262] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 18 11:19:00 node-4 kernel: [    1.052661] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 18 11:19:00 node-4 kernel: [    1.065159] ehci-pci 0000:00:1a.0: debug port 2
Sep 18 11:19:00 node-4 kernel: [    1.075356] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 18 11:19:00 node-4 kernel: [    1.075374] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 18 11:19:00 node-4 kernel: [    1.091952] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 18 11:19:00 node-4 kernel: [    1.098020] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 18 11:19:00 node-4 kernel: [    1.104186] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 18 11:19:00 node-4 kernel: [    1.116066] usb usb1: Product: EHCI Host Controller
Sep 18 11:19:00 node-4 kernel: [    1.122083] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 18 11:19:00 node-4 kernel: [    1.128120] usb usb1: SerialNumber: 0000:00:1a.0
Sep 18 11:19:00 node-4 kernel: [    1.134078] hub 1-0:1.0: USB hub found
Sep 18 11:19:00 node-4 kernel: [    1.139926] hub 1-0:1.0: 2 ports detected
Sep 18 11:19:00 node-4 kernel: [    1.145787] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 18 11:19:00 node-4 kernel: [    1.151372] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 18 11:19:00 node-4 kernel: [    1.162251] ehci-pci 0000:00:1d.0: debug port 2
Sep 18 11:19:00 node-4 kernel: [    1.171556] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 18 11:19:00 node-4 kernel: [    1.171559] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 18 11:19:00 node-4 kernel: [    1.187870] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 18 11:19:00 node-4 kernel: [    1.193064] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 18 11:19:00 node-4 kernel: [    1.198394] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 18 11:19:00 node-4 kernel: [    1.208950] usb usb2: Product: EHCI Host Controller
Sep 18 11:19:00 node-4 kernel: [    1.214415] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 18 11:19:00 node-4 kernel: [    1.219963] usb usb2: SerialNumber: 0000:00:1d.0
Sep 18 11:19:00 node-4 kernel: [    1.225476] hub 2-0:1.0: USB hub found
Sep 18 11:19:00 node-4 kernel: [    1.230843] hub 2-0:1.0: 2 ports detected
Sep 18 11:19:00 node-4 kernel: [    1.236131] ehci-platform: EHCI generic platform driver
Sep 18 11:19:00 node-4 kernel: [    1.241369] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 18 11:19:00 node-4 kernel: [    1.246693] ohci-pci: OHCI PCI platform driver
Sep 18 11:19:00 node-4 kernel: [    1.252003] ohci-platform: OHCI generic platform driver
Sep 18 11:19:00 node-4 kernel: [    1.257206] uhci_hcd: USB Universal Host Controller Interface driver
Sep 18 11:19:00 node-4 kernel: [    1.262542] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 18 11:19:00 node-4 kernel: [    1.459637] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 18 11:19:00 node-4 kernel: [    1.627896] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 18 11:19:00 node-4 kernel: [    1.633444] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 18 11:19:00 node-4 kernel: [    1.639160] hub 1-1:1.0: USB hub found
Sep 18 11:19:00 node-4 kernel: [    1.644632] hub 1-1:1.0: 6 ports detected
Sep 18 11:19:00 node-4 kernel: [    1.759384] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 18 11:19:00 node-4 kernel: [    1.767380] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 18 11:19:00 node-4 kernel: [    2.027556] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 18 11:19:00 node-4 kernel: [    2.033094] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 18 11:19:00 node-4 kernel: [    2.038948] hub 2-1:1.0: USB hub found
Sep 18 11:19:00 node-4 kernel: [    2.044667] hub 2-1:1.0: 8 ports detected
Sep 18 11:19:00 node-4 kernel: [    2.304037] i8042: No controller found
Sep 18 11:19:00 node-4 kernel: [    2.309513] mousedev: PS/2 mouse device common for all mice
Sep 18 11:19:00 node-4 kernel: [    2.315071] rtc_cmos 00:02: RTC can wake from S4
Sep 18 11:19:00 node-4 kernel: [    2.320717] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 18 11:19:00 node-4 kernel: [    2.326508] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 18 11:19:00 node-4 kernel: [    2.330968] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 18 11:19:00 node-4 kernel: [    2.343089] device-mapper: uevent: version 1.0.3
Sep 18 11:19:00 node-4 kernel: [    2.348732] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 18 11:19:00 node-4 kernel: [    2.359998] ledtrig-cpu: registered to indicate activity on CPUs
Sep 18 11:19:00 node-4 kernel: [    2.365948] TCP: cubic registered
Sep 18 11:19:00 node-4 kernel: [    2.371857] NET: Registered protocol family 10
Sep 18 11:19:00 node-4 kernel: [    2.377846] NET: Registered protocol family 17
Sep 18 11:19:00 node-4 kernel: [    2.383529] Key type dns_resolver registered
Sep 18 11:19:00 node-4 kernel: [    2.389512] Loading compiled-in X.509 certificates
Sep 18 11:19:00 node-4 kernel: [    2.395773] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 18 11:19:00 node-4 kernel: [    2.407183] registered taskstats version 1
Sep 18 11:19:00 node-4 kernel: [    2.415118] Key type trusted registered
Sep 18 11:19:00 node-4 kernel: [    2.422669] Key type encrypted registered
Sep 18 11:19:00 node-4 kernel: [    2.428139] AppArmor: AppArmor sha1 policy hashing enabled
Sep 18 11:19:00 node-4 kernel: [    2.433629] IMA: No TPM chip found, activating TPM-bypass!
Sep 18 11:19:00 node-4 kernel: [    2.439784] regulator-dummy: disabling
Sep 18 11:19:00 node-4 kernel: [    2.445363]   Magic number: 0:807:327
Sep 18 11:19:00 node-4 kernel: [    2.451039] rtc_cmos 00:02: setting system clock to 2016-09-18 11:18:25 UTC (1474197505)
Sep 18 11:19:00 node-4 kernel: [    2.463353] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 18 11:19:00 node-4 kernel: [    2.468950] EDD information not available.
Sep 18 11:19:00 node-4 kernel: [    2.471624] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 18 11:19:00 node-4 kernel: [    2.471625] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 18 11:19:00 node-4 kernel: [    2.471626] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 18 11:19:00 node-4 kernel: [    2.471627] usb 2-1.4: Manufacturer: Avocent
Sep 18 11:19:00 node-4 kernel: [    2.471628] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 18 11:19:00 node-4 kernel: [    2.509534] PM: Hibernation image not present or could not be loaded.
Sep 18 11:19:00 node-4 kernel: [    2.510410] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 18 11:19:00 node-4 kernel: [    2.521774] Write protecting the kernel read-only data: 12288k
Sep 18 11:19:00 node-4 kernel: [    2.528063] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 18 11:19:00 node-4 kernel: [    2.540553] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 18 11:19:00 node-4 kernel: [    2.572422] device-mapper: multipath: version 1.6.0 loaded
Sep 18 11:19:00 node-4 kernel: [    2.580423] systemd-udevd[216]: starting version 204
Sep 18 11:19:00 node-4 kernel: [    2.605201] md: linear personality registered for level -1
Sep 18 11:19:00 node-4 kernel: [    2.620249] md: multipath personality registered for level -4
Sep 18 11:19:00 node-4 kernel: [    2.628138] md: raid0 personality registered for level 0
Sep 18 11:19:00 node-4 kernel: [    2.636439] md: raid1 personality registered for level 1
Sep 18 11:19:00 node-4 kernel: [    2.644518] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 18 11:19:00 node-4 kernel: [    2.650947] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 18 11:19:00 node-4 kernel: [    2.651719] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 18 11:19:00 node-4 kernel: [    2.655902] megasas: FW now in Ready state
Sep 18 11:19:00 node-4 kernel: [    2.656530] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.656674] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.656750] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.656924] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.657070] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.657271] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.657283] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.657489] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.657605] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.657732] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.657921] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.658038] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.658184] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.658322] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.658414] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.658549] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.659609] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 18 11:19:00 node-4 kernel: [    2.682983] hidraw: raw HID events driver (C) Jiri Kosina
Sep 18 11:19:00 node-4 kernel: [    2.691556] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Sep 18 11:19:00 node-4 kernel: [    2.704495] 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
Sep 18 11:19:00 node-4 kernel: [    2.717881] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 18 11:19:00 node-4 kernel: [    2.724662] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.724666] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.724670] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.724674] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.724716] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.738069] usbcore: registered new interface driver usbhid
Sep 18 11:19:00 node-4 kernel: [    2.744751] usbhid: USB HID core driver
Sep 18 11:19:00 node-4 kernel: [    2.749379] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Sep 18 11:19:00 node-4 kernel: [    2.749380] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Sep 18 11:19:00 node-4 kernel: [    2.749381] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 18 11:19:00 node-4 kernel: [    2.749452] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.749488] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.749536] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.749573] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.749612] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.749647] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.749732] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.750715] raid6: sse2x1    2756 MB/s
Sep 18 11:19:00 node-4 kernel: [    2.761951] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Sep 18 11:19:00 node-4 kernel: [    2.761952] 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
Sep 18 11:19:00 node-4 kernel: [    2.761953] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 18 11:19:00 node-4 kernel: [    2.762014] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.762050] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.762089] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.762121] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.762250] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 18 11:19:00 node-4 kernel: [    2.773612] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Sep 18 11:19:00 node-4 kernel: [    2.773614] 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
Sep 18 11:19:00 node-4 kernel: [    2.773615] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 18 11:19:00 node-4 kernel: [    2.818724] raid6: sse2x2    9373 MB/s
Sep 18 11:19:00 node-4 kernel: [    2.886712] raid6: sse2x4    9499 MB/s
Sep 18 11:19:00 node-4 kernel: [    2.954383] raid6: avx2x1   14800 MB/s
Sep 18 11:19:00 node-4 kernel: [    3.026325] raid6: avx2x2   18856 MB/s
Sep 18 11:19:00 node-4 kernel: [    3.098268] raid6: avx2x4   21266 MB/s
Sep 18 11:19:00 node-4 kernel: [    3.104292] raid6: using algorithm avx2x4 (21266 MB/s)
Sep 18 11:19:00 node-4 kernel: [    3.110466] raid6: using avx2x2 recovery algorithm
Sep 18 11:19:00 node-4 kernel: [    3.116515] megasas:IOC Init cmd success
Sep 18 11:19:00 node-4 kernel: [    3.116516] Switched to clocksource tsc
Sep 18 11:19:00 node-4 kernel: [    3.116636] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    3.116674] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    3.116715] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    3.116755] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Sep 18 11:19:00 node-4 kernel: [    3.116963] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 18 11:19:00 node-4 kernel: [    3.140732] xor: automatically using best checksumming function:
Sep 18 11:19:00 node-4 kernel: [    3.142996] megasas: INIT adapter done
Sep 18 11:19:00 node-4 kernel: [    3.152484] 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
Sep 18 11:19:00 node-4 kernel: [    3.164365] 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
Sep 18 11:19:00 node-4 kernel: [    3.176731] 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
Sep 18 11:19:00 node-4 kernel: [    3.189226] 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
Sep 18 11:19:00 node-4 kernel: [    3.190176]    avx       : 36235.000 MB/sec
Sep 18 11:19:00 node-4 kernel: [    3.208260] 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
Sep 18 11:19:00 node-4 kernel: [    3.214168] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 18 11:19:00 node-4 kernel: [    3.214511] scsi0 : LSI SAS based MegaRAID driver
Sep 18 11:19:00 node-4 kernel: [    3.221524] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 18 11:19:00 node-4 kernel: [    3.232658] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 18 11:19:00 node-4 kernel: [    3.236854] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 18 11:19:00 node-4 kernel: [    3.237079] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 18 11:19:00 node-4 kernel: [    3.237396] sd 0:2:0:0: [sda] Write Protect is off
Sep 18 11:19:00 node-4 kernel: [    3.237397] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 18 11:19:00 node-4 kernel: [    3.237464] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 18 11:19:00 node-4 kernel: [    3.266560]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Sep 18 11:19:00 node-4 kernel: [    3.268477] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 18 11:19:00 node-4 kernel: [    3.312918] async_tx: api initialized (async)
Sep 18 11:19:00 node-4 kernel: [    3.312941] 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
Sep 18 11:19:00 node-4 kernel: [    3.338143] md: raid6 personality registered for level 6
Sep 18 11:19:00 node-4 kernel: [    3.345340] md: raid5 personality registered for level 5
Sep 18 11:19:00 node-4 kernel: [    3.352316] md: raid4 personality registered for level 4
Sep 18 11:19:00 node-4 kernel: [    3.362102] md: raid10 personality registered for level 10
Sep 18 11:19:00 node-4 kernel: [    3.415582] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Sep 18 11:19:00 node-4 kernel: [    3.463055] random: lvm urandom read with 32 bits of entropy available
Sep 18 11:19:00 node-4 kernel: [    3.652693] bio: create slab <bio-1> at 1
Sep 18 11:19:00 node-4 kernel: [    4.431218] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 18 11:19:00 node-4 kernel: [    5.077278] random: nonblocking pool is initialized
Sep 18 11:19:00 node-4 kernel: [    5.202149] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep 18 11:19:00 node-4 kernel: [    5.236434] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 18 11:19:00 node-4 kernel: [    5.468863] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 18 11:19:00 node-4 kernel: [    5.498802] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 18 11:19:00 node-4 kernel: [    5.580056] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 18 11:19:00 node-4 kernel: [    5.782526] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 18 11:19:00 node-4 kernel: [    5.817455] XFS (dm-0): Mounting Filesystem
Sep 18 11:19:00 node-4 kernel: [    6.129103] XFS (dm-0): Ending clean mount
Sep 18 11:19:00 node-4 kernel: [    6.196528] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep 18 11:19:00 node-4 kernel: [    6.242345] XFS (dm-1): Mounting Filesystem
Sep 18 11:19:00 node-4 kernel: [    6.322302] XFS (dm-1): Ending clean mount
Sep 18 11:19:00 node-4 kernel: [    8.399975] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 18 11:19:00 node-4 kernel: [    8.427440] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 18 11:19:00 node-4 kernel: [    8.621478] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 18 11:19:00 node-4 kernel: [    8.621489] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 18 11:19:00 node-4 kernel: [    8.621498] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 18 11:19:00 node-4 kernel: [    8.621506] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 18 11:19:00 node-4 kernel: [    8.675355] systemd-udevd[778]: starting version 204
Sep 18 11:19:00 node-4 kernel: [    8.899111] power_meter ACPI000D:00: Found ACPI power meter.
Sep 18 11:19:00 node-4 kernel: [    8.899120] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 18 11:19:00 node-4 kernel: [    8.931460] wmi: Mapper loaded
Sep 18 11:19:00 node-4 kernel: [    8.936714] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 18 11:19:00 node-4 kernel: [    8.940788] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 18 11:19:00 node-4 kernel: [    8.940793] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 18 11:19:00 node-4 kernel: [    8.940796] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 18 11:19:00 node-4 kernel: [    8.940798] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 18 11:19:00 node-4 kernel: [    8.940824] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 18 11:19:00 node-4 kernel: [    8.952919] IPMI System Interface driver.
Sep 18 11:19:00 node-4 kernel: [    8.952953] ipmi_si: probing via ACPI
Sep 18 11:19:00 node-4 kernel: [    8.952969] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 18 11:19:00 node-4 kernel: [    8.952970] ipmi_si: Adding ACPI-specified kcs state machine
Sep 18 11:19:00 node-4 kernel: [    8.952977] ipmi_si: probing via SMBIOS
Sep 18 11:19:00 node-4 kernel: [    8.952978] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 18 11:19:00 node-4 kernel: [    8.952979] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 18 11:19:00 node-4 kernel: [    8.952980] ipmi_si: probing via SPMI
Sep 18 11:19:00 node-4 kernel: [    8.952981] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 18 11:19:00 node-4 kernel: [    8.952982] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 18 11:19:00 node-4 kernel: [    8.952983] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 18 11:19:00 node-4 kernel: [    8.997733] systemd-udevd[831]: renamed network interface eth0 to enp6s0
Sep 18 11:19:00 node-4 kernel: [    9.025595] systemd-udevd[798]: renamed network interface eth1 to enp7s0
Sep 18 11:19:00 node-4 kernel: [    9.053650] systemd-udevd[796]: renamed network interface eth3 to enp9s0
Sep 18 11:19:00 node-4 kernel: [    9.085579] systemd-udevd[795]: renamed network interface eth2 to enp8s0
Sep 18 11:19:00 node-4 kernel: [    9.095043] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 18 11:19:00 node-4 kernel: [    9.095052] ipmi_si 00:09: IPMI kcs interface initialized
Sep 18 11:19:00 node-4 kernel: [    9.413514] type=1400 audit(1474197512.465:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1057 comm="apparmor_parser"
Sep 18 11:19:00 node-4 kernel: [    9.413673] type=1400 audit(1474197512.465:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1057 comm="apparmor_parser"
Sep 18 11:19:00 node-4 kernel: [    9.413808] type=1400 audit(1474197512.465:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1057 comm="apparmor_parser"
Sep 18 11:19:00 node-4 kernel: [    9.429860] type=1400 audit(1474197512.481:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1054 comm="apparmor_parser"
Sep 18 11:19:00 node-4 kernel: [    9.430006] type=1400 audit(1474197512.481:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1054 comm="apparmor_parser"
Sep 18 11:19:00 node-4 kernel: [    9.430127] type=1400 audit(1474197512.481:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1054 comm="apparmor_parser"
Sep 18 11:19:00 node-4 kernel: [    9.441444] type=1400 audit(1474197512.493:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1053 comm="apparmor_parser"
Sep 18 11:19:00 node-4 kernel: [    9.441603] type=1400 audit(1474197512.493:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1053 comm="apparmor_parser"
Sep 18 11:19:00 node-4 kernel: [    9.441732] type=1400 audit(1474197512.493:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1053 comm="apparmor_parser"
Sep 18 11:19:00 node-4 kernel: [    9.457213] type=1400 audit(1474197512.509:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1055 comm="apparmor_parser"
Sep 18 11:19:00 node-4 kernel: [   10.089103] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 18 11:19:00 node-4 kernel: [   10.089689] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 18 11:19:00 node-4 kernel: [   10.311363] enic 0000:06:00.0 enp6s0: Link UP
Sep 18 11:19:00 node-4 kernel: [   10.311775] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 18 11:19:00 node-4 kernel: [   10.311784] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 18 11:19:00 node-4 kernel: [   20.042337] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 18 11:19:00 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 18 11:19:01 node-4 failsafe: Failsafe of 120 seconds reached.
Sep 18 11:19:01 node-4 kernel: [   38.755103] init: failsafe main process (8418) killed by TERM signal
Sep 18 11:19:01 node-4 dbus[8457]: [system] AppArmor D-Bus mediation is enabled
Sep 18 11:19:02 node-4 kernel: [   39.018480] audit_printk_skb: 30 callbacks suppressed
Sep 18 11:19:02 node-4 kernel: [   39.018482] type=1400 audit(1474197542.154:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8544 comm="apparmor_parser"
Sep 18 11:19:02 node-4 kernel: [   39.018770] type=1400 audit(1474197542.154:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8543 comm="apparmor_parser"
Sep 18 11:19:02 node-4 kernel: [   39.018775] type=1400 audit(1474197542.154:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8543 comm="apparmor_parser"
Sep 18 11:19:02 node-4 kernel: [   39.018778] type=1400 audit(1474197542.154:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8543 comm="apparmor_parser"
Sep 18 11:19:02 node-4 kernel: [   39.019011] type=1400 audit(1474197542.154:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8543 comm="apparmor_parser"
Sep 18 11:19:02 node-4 kernel: [   39.019013] type=1400 audit(1474197542.154:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8543 comm="apparmor_parser"
Sep 18 11:19:02 node-4 kernel: [   39.019126] type=1400 audit(1474197542.154:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8543 comm="apparmor_parser"
Sep 18 11:19:02 node-4 kernel: [   39.086978] type=1400 audit(1474197542.222:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8546 comm="apparmor_parser"
Sep 18 11:19:02 node-4 anacron[8611]: Anacron 2.3 started on 2016-09-18
Sep 18 11:19:02 node-4 cron[8577]: (CRON) INFO (pidfile fd = 3)
Sep 18 11:19:02 node-4 cron[8618]: (CRON) STARTUP (fork ok)
Sep 18 11:19:02 node-4 anacron[8611]: Will run job `cron.daily' in 5 min.
Sep 18 11:19:02 node-4 anacron[8611]: Will run job `cron.weekly' in 10 min.
Sep 18 11:19:02 node-4 anacron[8611]: Will run job `cron.monthly' in 15 min.
Sep 18 11:19:02 node-4 anacron[8611]: Jobs will be executed sequentially
Sep 18 11:19:02 node-4 cron[8618]: (CRON) INFO (Running @reboot jobs)
Sep 18 11:19:02 node-4 multipathd: path checkers start up
Sep 18 11:19:02 node-4 postfix/master[8756]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 18 11:19:05 node-4 puppet-agent[9070]: Reopening log files
Sep 18 11:19:07 node-4 puppet-agent[9070]: Could not request certificate: Connection refused - connect(2)
Sep 18 11:19:21 node-4 puppet-user[9329]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 18 11:19:21 node-4 puppet-user[9329]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Sep 18 11:19:21 node-4 puppet-user[9329]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 18 11:19:21 node-4 puppet-user[9329]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 18 11:19:22 node-4 puppet-user[9329]: Finished catalog run in 0.48 seconds
Sep 18 11:19:23 node-4 multipathd: uevent trigger error
Sep 18 11:19:23 node-4 puppet-user[9744]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 18 11:19:23 node-4 puppet-user[9744]: Compiled catalog for node-4.domain.tld in environment production in 0.09 seconds
Sep 18 11:19:23 node-4 puppet-user[9744]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 18 11:19:23 node-4 puppet-user[9744]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 18 11:19:23 node-4 puppet-user[9744]: (/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"]'
Sep 18 11:19:23 node-4 puppet-user[9744]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 18 11:19:23 node-4 puppet-user[9744]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 18 11:19:23 node-4 puppet-user[9744]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 18 11:19:23 node-4 puppet-user[9744]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 18 11:19:23 node-4 puppet-user[9744]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 18 11:19:23 node-4 puppet-user[9744]: Finished catalog run in 0.06 seconds
Sep 18 11:19:24 node-4 puppet-user[10209]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 18 11:19:24 node-4 puppet-user[10209]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Sep 18 11:19:24 node-4 puppet-user[10209]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 18 11:19:24 node-4 puppet-user[10209]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 18 11:19:25 node-4 puppet-user[10209]: Finished catalog run in 0.09 seconds
Sep 18 11:19:26 node-4 puppet-user[10672]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 18 11:19:26 node-4 puppet-user[10672]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Sep 18 11:19:26 node-4 puppet-user[10672]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 18 11:19:26 node-4 puppet-user[10672]: Finished catalog run in 0.04 seconds
Sep 18 11:19:27 node-4 puppet-user[11118]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 18 11:19:28 node-4 puppet-user[11118]: Compiled catalog for node-4.domain.tld in environment production in 0.18 seconds
Sep 18 11:19:28 node-4 puppet-user[11118]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 18 11:19:28 node-4 puppet-user[11118]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Sep 18 11:19:28 node-4 puppet-user[11118]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Sep 18 11:19:29 node-4 puppet-user[11118]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/bgpvpn-0.9/]/Exec[rsync /etc/fuel/plugins/bgpvpn-0.9/]/returns) executed successfully
Sep 18 11:19:29 node-4 puppet-user[11118]: Finished catalog run in 1.17 seconds
Sep 18 11:19:29 node-4 kernel: [   66.243584] init: plymouth-upstart-bridge main process ended, respawning
Sep 18 11:19:29 node-4 puppet-agent[9070]: Could not run: SIGTERM
Sep 18 11:19:29 node-4 kernel: [   66.524003] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 18 11:19:29 node-4 ec2: 
Sep 18 11:19:29 node-4 ec2: #############################################################
Sep 18 11:19:29 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 18 11:19:29 node-4 ec2: 1024 4b:91:32:d1:a8:1f:4b:84:32:3a:56:32:bc:e6:de:e1  root@node-4.domain.tld (DSA)
Sep 18 11:19:29 node-4 ec2: 256 25:4b:e8:6f:92:68:78:b2:06:44:03:fe:c5:a3:0b:7e  root@node-4.domain.tld (ECDSA)
Sep 18 11:19:29 node-4 ec2: 256 cf:67:04:20:b5:c1:c3:48:36:36:1f:ed:a1:c9:56:11  root@node-4.domain.tld (ED25519)
Sep 18 11:19:29 node-4 ec2: 2048 e4:75:cf:55:af:79:ff:e7:5d:06:76:ed:62:07:e9:cb  root@node-4.domain.tld (RSA)
Sep 18 11:19:29 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 18 11:19:29 node-4 ec2: #############################################################
Sep 18 11:19:30 node-4 puppet-user[11799]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 18 11:19:30 node-4 puppet-user[11799]: Compiled catalog for node-4.domain.tld in environment production in 0.26 seconds
Sep 18 11:19:31 node-4 puppet-user[11799]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Sep 18 11:19:31 node-4 puppet-user[11799]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[bgpvpn-0.9.0]/Apt::Setting[list-bgpvpn-0.9.0]/File[/etc/apt/sources.list.d/bgpvpn-0.9.0.list]/ensure) created
Sep 18 11:19:31 node-4 puppet-user[11799]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 18 11:19:31 node-4 puppet-user[11799]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 18 11:19:31 node-4 puppet-user[11799]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Sep 18 11:19:31 node-4 puppet-user[11799]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 18 11:19:31 node-4 puppet-user[11799]: Finished catalog run in 0.36 seconds
Sep 18 11:19:32 node-4 puppet-user[12304]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 18 11:19:33 node-4 puppet-user[12304]: Compiled catalog for node-4.domain.tld in environment production in 0.16 seconds
Sep 18 11:19:33 node-4 puppet-user[12304]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 18 11:19:33 node-4 kernel: [   70.127748] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 18 11:19:33 node-4 kernel: [   70.127803] 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.
Sep 18 11:19:33 node-4 puppet-user[12304]: (/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'
Sep 18 11:19:33 node-4 puppet-user[12304]: Finished catalog run in 0.05 seconds
Sep 18 11:19:34 node-4 puppet-user[12765]: (Scope(Class[main])) MODULAR: sync_time
Sep 18 11:19:34 node-4 puppet-user[12765]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Sep 18 11:19:35 node-4 ntpdate[13180]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 18 11:19:41 node-4 ntpdate[13180]: adjust time server 10.20.0.2 offset -0.030181 sec
Sep 18 11:19:41 node-4 puppet-user[12765]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 18 11:19:41 node-4 puppet-user[12765]: Finished catalog run in 6.17 seconds
Sep 18 11:19:46 node-4 puppet-user[13377]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 18 11:19:46 node-4 puppet-user[13377]: Compiled catalog for node-4.domain.tld in environment production in 0.09 seconds
Sep 18 11:19:46 node-4 puppet-user[13377]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 18 11:19:46 node-4 puppet-user[13377]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/bgpvpn", "plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Sep 18 11:19:46 node-4 puppet-user[13377]: Finished catalog run in 0.07 seconds
Sep 18 11:19:48 node-4 puppet-user[13843]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 18 11:19:48 node-4 puppet-user[13843]: Compiled catalog for node-4.domain.tld in environment production in 0.50 seconds
Sep 18 11:19:48 node-4 puppet-user[13843]: (/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
Sep 18 11:19:48 node-4 puppet-user[13843]: (/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
Sep 18 11:19:48 node-4 puppet-user[13843]: (/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
Sep 18 11:19:48 node-4 puppet-user[13843]: (/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
Sep 18 11:19:48 node-4 puppet-user[13843]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 18 11:19:48 node-4 puppet-user[13843]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep 18 11:19:48 node-4 puppet-user[13843]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 18 11:19:48 node-4 puppet-user[13843]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep 18 11:19:48 node-4 puppet-user[13843]: (/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
Sep 18 11:19:48 node-4 puppet-user[13843]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep 18 11:19:49 node-4 puppet-user[13843]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 18 11:19:49 node-4 puppet-user[13843]: Finished catalog run in 0.92 seconds
Sep 18 11:19:51 node-4 puppet-user[14366]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 18 11:19:51 node-4 puppet-user[14366]: Compiled catalog for node-4.domain.tld in environment production in 0.11 seconds
Sep 18 11:19:54 node-4 puppet-user[14366]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 18 11:20:01 node-4 CRON[15760]: (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")
Sep 18 11:20:02 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 18 11:20:02 node-4 nailgun-agent: I, [2016-09-18T11:20:02.605414 #15763]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 18 11:20:15 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 18 11:20:15 node-4 nailgun-agent: I, [2016-09-18T11:20:15.648356 #15763]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Sep 18 11:20:20 node-4 puppet-user[14366]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 18 11:20:20 node-4 puppet-user[14366]: Finished catalog run in 28.93 seconds
Sep 18 11:20:22 node-4 puppet-user[17105]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 18 11:20:22 node-4 puppet-user[17105]: Compiled catalog for node-4.domain.tld in environment production in 0.66 seconds
Sep 18 11:20:23 node-4 puppet-user[17105]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 18 11:20:23 node-4 puppet-user[17105]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 18 11:20:23 node-4 puppet-user[17105]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 18 11:20:23 node-4 puppet-user[17105]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 18 11:20:23 node-4 puppet-user[17105]: Finished catalog run in 0.11 seconds
Sep 18 11:20:24 node-4 puppet-user[17576]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 18 11:20:26 node-4 puppet-user[17576]: Compiled catalog for node-4.domain.tld in environment production in 1.09 seconds
Sep 18 11:20:26 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 18 11:20:26 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 18 11:20:26 node-4 crontab[18030]: (root) LIST (root)
Sep 18 11:20:26 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 18 11:20:26 node-4 crontab[18031]: (root) REPLACE (root)
Sep 18 11:20:27 node-4 puppet-user[17576]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/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
Sep 18 11:20:28 node-4 puppet-user[17576]: (/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
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/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
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/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
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/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
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 18 11:20:28 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 18 11:20:29 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep 18 11:20:29 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 18 11:20:29 node-4 puppet-user[17576]: (/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
Sep 18 11:20:29 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep 18 11:20:29 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep 18 11:20:29 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 18 11:20:29 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 18 11:20:29 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 18 11:20:29 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 18 11:20:29 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 18 11:20:29 node-4 puppet-user[17576]: (/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
Sep 18 11:20:29 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 18 11:20:29 node-4 puppet-user[17576]: (/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
Sep 18 11:20:29 node-4 puppet-user[17576]: (/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
Sep 18 11:20:29 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 18 11:20:29 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 18 11:20:29 node-4 puppet-user[17576]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep 18 11:20:29 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8391" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 18 11:20:29 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 18 11:20:31 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:31 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:31 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:31 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:31 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:31 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:31 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:43 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:43 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:43 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:43 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:43 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:48 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:48 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:48 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:48 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:48 node-4 multipathd: uevent trigger error
<27>Sep 18 11:20:48 node-4 multipathd: uevent trigger error
<27>Sep 18 11:21:43 node-4 ntpdate[28280]: no servers can be used, exiting
<27>Sep 18 11:22:14 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:14 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:14 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:14 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:14 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:17 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:17 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:17 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:17 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:17 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:28 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:28 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:28 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:28 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:28 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:36 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:36 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:36 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:36 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:36 node-4 multipathd: uevent trigger error
<43>Sep 18 11:22:49 node-4 apache2_error [Sun Sep 18 11:22:46.679694 2016] [mpm_event:notice] [pid 5200:tid 140289282910080] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 18 11:22:49 node-4 apache2_error [Sun Sep 18 11:22:46.679784 2016] [core:notice] [pid 5200:tid 140289282910080] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 18 11:22:54 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:54 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:54 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:54 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:54 node-4 multipathd: uevent trigger error
<27>Sep 18 11:22:54 node-4 multipathd: uevent trigger error
<43>Sep 18 11:22:59 node-4 apache2_error [Sun Sep 18 11:22:49.638830 2016] [mpm_event:notice] [pid 5200:tid 140289282910080] AH00491: caught SIGTERM, shutting down
<43>Sep 18 11:22:59 node-4 apache2_error [Sun Sep 18 11:22:50.728820 2016] [mpm_worker:notice] [pid 5560:tid 140127045126016] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 18 11:22:59 node-4 apache2_error [Sun Sep 18 11:22:50.728893 2016] [core:notice] [pid 5560:tid 140127045126016] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 18 11:23:29 node-4 apache2_error [Sun Sep 18 11:23:27.913601 2016] [mpm_worker:notice] [pid 5560:tid 140127045126016] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 18 11:23:29 node-4 apache2_error [Sun Sep 18 11:23:27.921260 2016] [mpm_worker:warn] [pid 5560:tid 140127045126016] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 18 11:23:29 node-4 apache2_error [Sun Sep 18 11:23:27.922014 2016] [mpm_worker:notice] [pid 5560:tid 140127045126016] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 18 11:23:29 node-4 apache2_error [Sun Sep 18 11:23:27.922027 2016] [core:notice] [pid 5560:tid 140127045126016] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 18 11:23:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:23:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:23:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:23:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:23:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:23:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:23:49 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:18 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Sep 18 11:24:23 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:23 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:23 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:23 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:23 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:23 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:27 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:27 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:27 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:27 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:27 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:38 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:38 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:38 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:38 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:38 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:38 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:38 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:45 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:45 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:45 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:45 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:45 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:45 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:45 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:50 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:50 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:50 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:50 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:50 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:50 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:50 node-4 multipathd: uevent trigger error
<129>Sep 18 11:24:51 node-4 haproxy[23157]: Server odl-jetty/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>Sep 18 11:24:51 node-4 haproxy[23157]: proxy odl-jetty has no server available!
<129>Sep 18 11:24:53 node-4 haproxy[24175]: 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>Sep 18 11:24:55 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:55 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:55 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:55 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:55 node-4 multipathd: uevent trigger error
<129>Sep 18 11:24:56 node-4 haproxy[24184]: Server odl-jetty/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>Sep 18 11:24:56 node-4 haproxy[24184]: proxy odl-jetty has no server available!
<27>Sep 18 11:24:58 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:58 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:58 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:58 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:59 node-4 multipathd: uevent trigger error
<27>Sep 18 11:24:59 node-4 multipathd: uevent trigger error
<129>Sep 18 11:25:01 node-4 haproxy[24184]: Server odl-neutron-endpoint/node-3 is DOWN, reason: Layer4 timeout, check duration: 5002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 18 11:25:01 node-4 haproxy[24184]: proxy odl-neutron-endpoint has no server available!
<129>Sep 18 11:25:02 node-4 haproxy[26131]: 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>Sep 18 11:25:02 node-4 haproxy[26131]: 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>Sep 18 11:25:04 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:04 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:04 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:04 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:04 node-4 multipathd: uevent trigger error
<129>Sep 18 11:25:05 node-4 haproxy[26131]: Server odl-jetty/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>Sep 18 11:25:05 node-4 haproxy[26131]: proxy odl-jetty has no server available!
<129>Sep 18 11:25:06 node-4 haproxy[27281]: 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>Sep 18 11:25:07 node-4 haproxy[27290]: 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>Sep 18 11:25:07 node-4 haproxy[27290]: 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>Sep 18 11:25:08 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:08 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:08 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:08 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:08 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:08 node-4 multipathd: uevent trigger error
<129>Sep 18 11:25:10 node-4 haproxy[27290]: Server odl-jetty/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>Sep 18 11:25:10 node-4 haproxy[27290]: proxy odl-jetty has no server available!
<129>Sep 18 11:25:11 node-4 haproxy[28326]: 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>Sep 18 11:25:11 node-4 haproxy[28326]: 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>Sep 18 11:25:12 node-4 haproxy[28335]: 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>Sep 18 11:25:12 node-4 haproxy[28335]: 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>Sep 18 11:25:12 node-4 haproxy[28335]: 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>Sep 18 11:25:13 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:13 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:13 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:13 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:13 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:13 node-4 multipathd: uevent trigger error
<129>Sep 18 11:25:15 node-4 haproxy[28335]: Server odl-jetty/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>Sep 18 11:25:15 node-4 haproxy[28335]: proxy odl-jetty has no server available!
<129>Sep 18 11:25:16 node-4 haproxy[29358]: 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>Sep 18 11:25:16 node-4 haproxy[29358]: 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>Sep 18 11:25:16 node-4 haproxy[29358]: 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>Sep 18 11:25:17 node-4 haproxy[29370]: 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>Sep 18 11:25:17 node-4 haproxy[29370]: 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>Sep 18 11:25:17 node-4 haproxy[29370]: 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>Sep 18 11:25:19 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:19 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:19 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:19 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:19 node-4 multipathd: uevent trigger error
<129>Sep 18 11:25:19 node-4 haproxy[29370]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:19 node-4 haproxy[29370]: 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>Sep 18 11:25:19 node-4 haproxy[29370]: proxy aodh has no server available!
<129>Sep 18 11:25:19 node-4 haproxy[29370]: Server odl-jetty/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>Sep 18 11:25:19 node-4 haproxy[29370]: proxy odl-jetty has no server available!
<129>Sep 18 11:25:21 node-4 haproxy[30515]: 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>Sep 18 11:25:21 node-4 haproxy[30515]: 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>Sep 18 11:25:22 node-4 haproxy[30529]: 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>Sep 18 11:25:22 node-4 haproxy[30529]: 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>Sep 18 11:25:22 node-4 haproxy[30529]: 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>Sep 18 11:25:22 node-4 haproxy[30529]: 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>Sep 18 11:25:23 node-4 haproxy[30529]: 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>Sep 18 11:25:24 node-4 multipathd: uevent trigger error
<129>Sep 18 11:25:24 node-4 haproxy[30529]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 18 11:25:24 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:24 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:24 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:24 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:24 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:24 node-4 multipathd: uevent trigger error
<129>Sep 18 11:25:24 node-4 haproxy[30529]: 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>Sep 18 11:25:24 node-4 haproxy[30529]: proxy aodh has no server available!
<129>Sep 18 11:25:24 node-4 haproxy[30529]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:24 node-4 haproxy[30529]: 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>Sep 18 11:25:24 node-4 haproxy[30529]: proxy ceilometer has no server available!
<129>Sep 18 11:25:25 node-4 haproxy[30529]: Server odl-jetty/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>Sep 18 11:25:25 node-4 haproxy[30529]: proxy odl-jetty has no server available!
<129>Sep 18 11:25:27 node-4 haproxy[31570]: 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>Sep 18 11:25:27 node-4 haproxy[31570]: 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>Sep 18 11:25:27 node-4 haproxy[31570]: 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>Sep 18 11:25:27 node-4 haproxy[31570]: 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>Sep 18 11:25:28 node-4 haproxy[31570]: 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>Sep 18 11:25:28 node-4 haproxy[31570]: 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>Sep 18 11:25:28 node-4 haproxy[31570]: 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>Sep 18 11:25:29 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:29 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:29 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:29 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:29 node-4 multipathd: uevent trigger error
<129>Sep 18 11:25:30 node-4 haproxy[31570]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:30 node-4 haproxy[31570]: 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>Sep 18 11:25:30 node-4 haproxy[31570]: proxy aodh has no server available!
<129>Sep 18 11:25:30 node-4 haproxy[31570]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:30 node-4 haproxy[31570]: 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>Sep 18 11:25:30 node-4 haproxy[31570]: proxy ceilometer has no server available!
<129>Sep 18 11:25:30 node-4 haproxy[31570]: Server odl-jetty/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>Sep 18 11:25:30 node-4 haproxy[31570]: proxy odl-jetty has no server available!
<129>Sep 18 11:25:32 node-4 haproxy[32588]: 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>Sep 18 11:25:32 node-4 haproxy[32588]: 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>Sep 18 11:25:32 node-4 haproxy[32588]: 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>Sep 18 11:25:32 node-4 haproxy[32588]: 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>Sep 18 11:25:32 node-4 haproxy[32588]: 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>Sep 18 11:25:33 node-4 haproxy[32588]: 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>Sep 18 11:25:33 node-4 haproxy[32588]: 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>Sep 18 11:25:33 node-4 haproxy[32588]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:33 node-4 haproxy[32588]: 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>Sep 18 11:25:34 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:34 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:34 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:34 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:34 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:34 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:34 node-4 multipathd: uevent trigger error
<129>Sep 18 11:25:35 node-4 haproxy[32588]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:35 node-4 haproxy[32588]: 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>Sep 18 11:25:35 node-4 haproxy[32588]: proxy aodh has no server available!
<129>Sep 18 11:25:35 node-4 haproxy[32588]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:35 node-4 haproxy[32588]: 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>Sep 18 11:25:35 node-4 haproxy[32588]: proxy ceilometer has no server available!
<129>Sep 18 11:25:35 node-4 haproxy[32588]: Server odl-jetty/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>Sep 18 11:25:35 node-4 haproxy[32588]: proxy odl-jetty has no server available!
<129>Sep 18 11:25:37 node-4 haproxy[1231]: 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>Sep 18 11:25:37 node-4 haproxy[1231]: 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>Sep 18 11:25:37 node-4 haproxy[1231]: 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>Sep 18 11:25:37 node-4 haproxy[1231]: 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>Sep 18 11:25:38 node-4 haproxy[1240]: 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>Sep 18 11:25:38 node-4 haproxy[1240]: 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>Sep 18 11:25:38 node-4 haproxy[1240]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:38 node-4 haproxy[1240]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:38 node-4 haproxy[1240]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:38 node-4 haproxy[1240]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:39 node-4 haproxy[1240]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:39 node-4 haproxy[1240]: 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>Sep 18 11:25:39 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:39 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:39 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:39 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:39 node-4 multipathd: uevent trigger error
<129>Sep 18 11:25:40 node-4 haproxy[1240]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:40 node-4 haproxy[1240]: 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>Sep 18 11:25:40 node-4 haproxy[1240]: proxy glance-registry has no server available!
<129>Sep 18 11:25:40 node-4 haproxy[1240]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:40 node-4 haproxy[1240]: 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>Sep 18 11:25:40 node-4 haproxy[1240]: proxy aodh has no server available!
<129>Sep 18 11:25:40 node-4 haproxy[1240]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:40 node-4 haproxy[1240]: 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>Sep 18 11:25:40 node-4 haproxy[1240]: proxy ceilometer has no server available!
<129>Sep 18 11:25:40 node-4 haproxy[1240]: Server odl-jetty/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>Sep 18 11:25:40 node-4 haproxy[1240]: proxy odl-jetty has no server available!
<129>Sep 18 11:25:42 node-4 haproxy[2305]: 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>Sep 18 11:25:42 node-4 haproxy[2305]: 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>Sep 18 11:25:42 node-4 haproxy[2305]: 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>Sep 18 11:25:43 node-4 haproxy[2314]: 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>Sep 18 11:25:43 node-4 haproxy[2314]: 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>Sep 18 11:25:43 node-4 haproxy[2314]: 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>Sep 18 11:25:43 node-4 haproxy[2314]: 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>Sep 18 11:25:43 node-4 haproxy[2314]: 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>Sep 18 11:25:43 node-4 haproxy[2314]: 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>Sep 18 11:25:43 node-4 haproxy[2314]: 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>Sep 18 11:25:43 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Sep 18 11:25:44 node-4 haproxy[2314]: 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>Sep 18 11:25:44 node-4 haproxy[2314]: 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>Sep 18 11:25:44 node-4 haproxy[2314]: 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>Sep 18 11:25:44 node-4 haproxy[2314]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:44 node-4 haproxy[2314]: 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>Sep 18 11:25:45 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:45 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:45 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:45 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:45 node-4 multipathd: uevent trigger error
<129>Sep 18 11:25:45 node-4 haproxy[2314]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:45 node-4 haproxy[2314]: 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>Sep 18 11:25:45 node-4 haproxy[2314]: proxy glance-registry has no server available!
<129>Sep 18 11:25:45 node-4 haproxy[2314]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:46 node-4 haproxy[2314]: 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>Sep 18 11:25:46 node-4 haproxy[2314]: proxy aodh has no server available!
<129>Sep 18 11:25:46 node-4 haproxy[2314]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:46 node-4 haproxy[2314]: 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>Sep 18 11:25:46 node-4 haproxy[2314]: proxy ceilometer has no server available!
<129>Sep 18 11:25:46 node-4 haproxy[2314]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:46 node-4 haproxy[2314]: 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>Sep 18 11:25:46 node-4 haproxy[2314]: proxy nova-novncproxy has no server available!
<129>Sep 18 11:25:46 node-4 haproxy[2314]: Server odl-jetty/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>Sep 18 11:25:46 node-4 haproxy[2314]: proxy odl-jetty has no server available!
<129>Sep 18 11:25:47 node-4 haproxy[3382]: 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>Sep 18 11:25:47 node-4 haproxy[3382]: 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>Sep 18 11:25:48 node-4 haproxy[3391]: 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>Sep 18 11:25:48 node-4 haproxy[3391]: 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>Sep 18 11:25:48 node-4 haproxy[3391]: 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>Sep 18 11:25:48 node-4 haproxy[3391]: 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>Sep 18 11:25:48 node-4 haproxy[3391]: 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>Sep 18 11:25:48 node-4 haproxy[3391]: 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>Sep 18 11:25:48 node-4 haproxy[3391]: 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>Sep 18 11:25:48 node-4 haproxy[3391]: 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>Sep 18 11:25:49 node-4 haproxy[3391]: 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>Sep 18 11:25:49 node-4 haproxy[3391]: 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>Sep 18 11:25:49 node-4 haproxy[3391]: 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>Sep 18 11:25:49 node-4 haproxy[3391]: 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>Sep 18 11:25:49 node-4 haproxy[3391]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:49 node-4 haproxy[3391]: 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>Sep 18 11:25:50 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:50 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:50 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:50 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:50 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:50 node-4 multipathd: uevent trigger error
<129>Sep 18 11:25:50 node-4 haproxy[3391]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:50 node-4 haproxy[3391]: 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>Sep 18 11:25:50 node-4 haproxy[3391]: proxy glance-registry has no server available!
<129>Sep 18 11:25:51 node-4 haproxy[3391]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:51 node-4 haproxy[3391]: 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>Sep 18 11:25:51 node-4 haproxy[3391]: proxy aodh has no server available!
<129>Sep 18 11:25:51 node-4 haproxy[3391]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:51 node-4 haproxy[3391]: 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>Sep 18 11:25:51 node-4 haproxy[3391]: proxy ceilometer has no server available!
<129>Sep 18 11:25:51 node-4 haproxy[3391]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:51 node-4 haproxy[3391]: 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>Sep 18 11:25:51 node-4 haproxy[3391]: proxy nova-novncproxy has no server available!
<129>Sep 18 11:25:51 node-4 haproxy[3391]: Server odl-jetty/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>Sep 18 11:25:51 node-4 haproxy[3391]: proxy odl-jetty has no server available!
<129>Sep 18 11:25:53 node-4 haproxy[4449]: 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>Sep 18 11:25:53 node-4 haproxy[4449]: 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>Sep 18 11:25:53 node-4 haproxy[4449]: 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>Sep 18 11:25:53 node-4 haproxy[4449]: 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>Sep 18 11:25:53 node-4 haproxy[4449]: 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>Sep 18 11:25:53 node-4 haproxy[4449]: 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>Sep 18 11:25:53 node-4 haproxy[4449]: 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>Sep 18 11:25:53 node-4 haproxy[4449]: 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>Sep 18 11:25:53 node-4 haproxy[4449]: 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>Sep 18 11:25:53 node-4 haproxy[4449]: 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>Sep 18 11:25:54 node-4 haproxy[4449]: 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>Sep 18 11:25:54 node-4 haproxy[4449]: 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>Sep 18 11:25:54 node-4 haproxy[4449]: 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>Sep 18 11:25:54 node-4 haproxy[4449]: 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>Sep 18 11:25:54 node-4 haproxy[4449]: 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>Sep 18 11:25:54 node-4 haproxy[4449]: 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>Sep 18 11:25:54 node-4 haproxy[4449]: 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>Sep 18 11:25:54 node-4 haproxy[4449]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:54 node-4 haproxy[4449]: 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>Sep 18 11:25:55 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:55 node-4 multipathd: uevent trigger error
<129>Sep 18 11:25:55 node-4 haproxy[4449]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 18 11:25:55 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:55 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:55 node-4 multipathd: uevent trigger error
<129>Sep 18 11:25:55 node-4 haproxy[4449]: 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>Sep 18 11:25:55 node-4 haproxy[4449]: proxy glance-registry has no server available!
<129>Sep 18 11:25:56 node-4 haproxy[4449]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:56 node-4 haproxy[4449]: 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>Sep 18 11:25:56 node-4 haproxy[4449]: proxy aodh has no server available!
<129>Sep 18 11:25:56 node-4 haproxy[4449]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:56 node-4 haproxy[4449]: 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>Sep 18 11:25:56 node-4 haproxy[4449]: proxy ceilometer has no server available!
<129>Sep 18 11:25:56 node-4 haproxy[4449]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:25:56 node-4 haproxy[4449]: 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>Sep 18 11:25:56 node-4 haproxy[4449]: proxy nova-novncproxy has no server available!
<129>Sep 18 11:25:56 node-4 haproxy[4449]: Server odl-jetty/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>Sep 18 11:25:56 node-4 haproxy[4449]: proxy odl-jetty has no server available!
<27>Sep 18 11:25:58 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:58 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:58 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:58 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:58 node-4 multipathd: uevent trigger error
<27>Sep 18 11:25:58 node-4 multipathd: uevent trigger error
<27>Sep 18 11:26:01 node-4 multipathd: uevent trigger error
<27>Sep 18 11:26:01 node-4 multipathd: uevent trigger error
<27>Sep 18 11:26:01 node-4 multipathd: uevent trigger error
<27>Sep 18 11:26:01 node-4 multipathd: uevent trigger error
<27>Sep 18 11:26:01 node-4 multipathd: uevent trigger error
<129>Sep 18 11:26:02 node-4 haproxy[4449]: Server odl-neutron-endpoint/node-3 is DOWN, reason: Layer4 timeout, check duration: 5001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 18 11:26:02 node-4 haproxy[4449]: proxy odl-neutron-endpoint has no server available!
<129>Sep 18 11:26:02 node-4 haproxy[4449]: Server keystone-1/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:26:03 node-4 haproxy[4449]: Server keystone-1/node-3 is DOWN, reason: Layer4 timeout, check duration: 10002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 18 11:26:03 node-4 haproxy[4449]: proxy keystone-1 has no server available!
<129>Sep 18 11:26:03 node-4 haproxy[4449]: Server keystone-2/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:26:03 node-4 haproxy[4449]: 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>Sep 18 11:26:03 node-4 haproxy[4449]: proxy keystone-2 has no server available!
<129>Sep 18 11:26:03 node-4 haproxy[4449]: Server nova-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:26:03 node-4 haproxy[4449]: Server nova-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 18 11:26:03 node-4 haproxy[4449]: proxy nova-api has no server available!
<129>Sep 18 11:26:03 node-4 haproxy[4449]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:26:03 node-4 haproxy[4449]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 18 11:26:03 node-4 haproxy[4449]: proxy nova-metadata-api has no server available!
<129>Sep 18 11:26:03 node-4 haproxy[4449]: Server cinder-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:26:03 node-4 haproxy[4449]: 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>Sep 18 11:26:03 node-4 haproxy[4449]: proxy cinder-api has no server available!
<129>Sep 18 11:26:03 node-4 haproxy[4449]: Server glance-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:26:03 node-4 haproxy[4449]: 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>Sep 18 11:26:03 node-4 haproxy[4449]: proxy glance-api has no server available!
<129>Sep 18 11:26:03 node-4 haproxy[4449]: Server glance-glare/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:26:03 node-4 haproxy[4449]: 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>Sep 18 11:26:03 node-4 haproxy[4449]: proxy glance-glare has no server available!
<129>Sep 18 11:26:03 node-4 haproxy[4449]: Server neutron/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:26:03 node-4 haproxy[4449]: Server neutron/node-3 is DOWN, reason: Layer4 timeout, check duration: 10002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 18 11:26:03 node-4 haproxy[4449]: proxy neutron has no server available!
<129>Sep 18 11:26:03 node-4 haproxy[4449]: Server mysqld/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:26:03 node-4 haproxy[4449]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 18 11:26:03 node-4 haproxy[4449]: proxy mysqld has no server available!
<129>Sep 18 11:26:04 node-4 haproxy[4449]: Server object-storage/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:26:04 node-4 haproxy[4449]: Server object-storage/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>Sep 18 11:26:04 node-4 haproxy[4449]: proxy object-storage has no server available!
<129>Sep 18 11:26:04 node-4 haproxy[4449]: Server heat-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:26:04 node-4 haproxy[4449]: 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>Sep 18 11:26:04 node-4 haproxy[4449]: proxy heat-api has no server available!
<129>Sep 18 11:26:04 node-4 haproxy[4449]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:26:04 node-4 haproxy[4449]: 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>Sep 18 11:26:04 node-4 haproxy[4449]: proxy heat-api-cfn has no server available!
<129>Sep 18 11:26:04 node-4 haproxy[4449]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 18 11:26:04 node-4 haproxy[4449]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 18 11:26:04 node-4 haproxy[4449]: proxy heat-api-cloudwatch has no server available!
<27>Sep 18 11:26:05 node-4 multipathd: uevent trigger error
<27>Sep 18 11:26:05 node-4 multipathd: uevent trigger error
<27>Sep 18 11:26:05 node-4 multipathd: uevent trigger error
<27>Sep 18 11:26:05 node-4 multipathd: uevent trigger error
<27>Sep 18 11:26:05 node-4 multipathd: uevent trigger error
<27>Sep 18 11:26:40 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 18 11:26:40 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 18 11:27:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:27:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:27:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:27:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:27:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:27:38 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>Sep 18 11:27:40 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 18 11:29:16 node-4 multipathd: uevent trigger error
<27>Sep 18 11:29:16 node-4 multipathd: uevent trigger error
<27>Sep 18 11:29:16 node-4 multipathd: uevent trigger error
<27>Sep 18 11:29:16 node-4 multipathd: uevent trigger error
<27>Sep 18 11:29:16 node-4 multipathd: uevent trigger error
<27>Sep 18 11:32:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:32:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:32:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:32:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:32:30 node-4 multipathd: uevent trigger error
<11>Sep 18 11:33:18 node-4 epmd: epmd: node name already occupied rabbitmq-cli-15
<43>Sep 18 11:33:40 node-4 apache2_error [Sun Sep 18 11:33:31.051363 2016] [mpm_worker:notice] [pid 5560:tid 140127045126016] AH00295: caught SIGTERM, shutting down
<43>Sep 18 11:33:40 node-4 apache2_error [Sun Sep 18 11:33:31.793898 2016] [mpm_worker:notice] [pid 31518:tid 140295246141312] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 18 11:33:40 node-4 apache2_error [Sun Sep 18 11:33:31.793938 2016] [core:notice] [pid 31518:tid 140295246141312] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 18 11:34:08 node-4 multipathd: uevent trigger error
<27>Sep 18 11:34:08 node-4 multipathd: uevent trigger error
<27>Sep 18 11:34:08 node-4 multipathd: uevent trigger error
<27>Sep 18 11:34:08 node-4 multipathd: uevent trigger error
<27>Sep 18 11:34:09 node-4 multipathd: uevent trigger error
<27>Sep 18 11:34:09 node-4 multipathd: uevent trigger error
<27>Sep 18 11:34:09 node-4 multipathd: uevent trigger error
<43>Sep 18 11:34:10 node-4 apache2_error [Sun Sep 18 11:34:03.751076 2016] [mpm_worker:notice] [pid 31518:tid 140295246141312] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 18 11:34:10 node-4 apache2_error [Sun Sep 18 11:34:03.761496 2016] [mpm_worker:warn] [pid 31518:tid 140295246141312] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 18 11:34:10 node-4 apache2_error [Sun Sep 18 11:34:03.765781 2016] [mpm_worker:notice] [pid 31518:tid 140295246141312] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 18 11:34:10 node-4 apache2_error [Sun Sep 18 11:34:03.765806 2016] [core:notice] [pid 31518:tid 140295246141312] AH00094: Command line: '/usr/sbin/apache2'
<11>Sep 18 11:34:41 node-4 epmd: epmd: node name already occupied rabbitmq-cli-15
<11>Sep 18 11:34:42 node-4 epmd: epmd: node name already occupied rabbitmq-cli-15
<27>Sep 18 11:34:57 node-4 multipathd: uevent trigger error
<27>Sep 18 11:34:57 node-4 multipathd: uevent trigger error
<27>Sep 18 11:34:57 node-4 multipathd: uevent trigger error
<27>Sep 18 11:34:57 node-4 multipathd: uevent trigger error
<27>Sep 18 11:34:57 node-4 multipathd: uevent trigger error
<27>Sep 18 11:34:57 node-4 multipathd: uevent trigger error
<27>Sep 18 11:34:57 node-4 multipathd: uevent trigger error
<27>Sep 18 11:36:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:36:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:36:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:36:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:36:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:36:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:41:03 node-4 multipathd: uevent trigger error
<27>Sep 18 11:41:03 node-4 multipathd: uevent trigger error
<27>Sep 18 11:41:03 node-4 multipathd: uevent trigger error
<27>Sep 18 11:41:03 node-4 multipathd: uevent trigger error
<27>Sep 18 11:41:03 node-4 multipathd: uevent trigger error
<27>Sep 18 11:41:03 node-4 multipathd: uevent trigger error
<11>Sep 18 11:42:53 node-4 epmd: epmd: node name already occupied rabbitmq-cli-15
<27>Sep 18 11:43:06 node-4 multipathd: uevent trigger error
<27>Sep 18 11:43:06 node-4 multipathd: uevent trigger error
<27>Sep 18 11:43:06 node-4 multipathd: uevent trigger error
<27>Sep 18 11:43:06 node-4 multipathd: uevent trigger error
<27>Sep 18 11:43:06 node-4 multipathd: uevent trigger error
<11>Sep 18 11:43:19 node-4 epmd: epmd: node name already occupied rabbitmq-cli-15
<27>Sep 18 11:44:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:08 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:42 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:42 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:42 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:42 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:42 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:42 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:51 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:51 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:51 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:51 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:51 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:51 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:55 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:55 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:55 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:55 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:55 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:55 node-4 multipathd: uevent trigger error
<27>Sep 18 11:44:56 node-4 multipathd: uevent trigger error
<27>Sep 18 11:45:11 node-4 multipathd: uevent trigger error
<27>Sep 18 11:45:11 node-4 multipathd: uevent trigger error
<27>Sep 18 11:45:11 node-4 multipathd: uevent trigger error
<27>Sep 18 11:45:11 node-4 multipathd: uevent trigger error
<27>Sep 18 11:45:11 node-4 multipathd: uevent trigger error
<27>Sep 18 11:45:11 node-4 multipathd: uevent trigger error
<27>Sep 18 11:45:11 node-4 multipathd: uevent trigger error
<27>Sep 18 11:45:17 node-4 multipathd: uevent trigger error
<27>Sep 18 11:45:17 node-4 multipathd: uevent trigger error
<27>Sep 18 11:45:17 node-4 multipathd: uevent trigger error
<27>Sep 18 11:45:17 node-4 multipathd: uevent trigger error
<27>Sep 18 11:45:17 node-4 multipathd: uevent trigger error
<27>Sep 18 11:45:17 node-4 multipathd: uevent trigger error
<27>Sep 18 11:45:17 node-4 multipathd: uevent trigger error
<27>Sep 18 11:45:17 node-4 multipathd: uevent trigger error
<11>Sep 18 11:45:59 node-4 epmd: epmd: node name already occupied rabbitmq-cli-15
<43>Sep 18 11:46:11 node-4 apache2_error [Sun Sep 18 11:46:05.401092 2016] [mpm_worker:notice] [pid 31518:tid 140295246141312] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 18 11:46:11 node-4 apache2_error [Sun Sep 18 11:46:05.787858 2016] [mpm_worker:warn] [pid 31518:tid 140295246141312] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 18 11:46:11 node-4 apache2_error [Sun Sep 18 11:46:05.791959 2016] [mpm_worker:notice] [pid 31518:tid 140295246141312] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 18 11:46:11 node-4 apache2_error [Sun Sep 18 11:46:05.791973 2016] [core:notice] [pid 31518:tid 140295246141312] AH00094: Command line: '/usr/sbin/apache2'
<11>Sep 18 11:46:26 node-4 epmd: epmd: node name already occupied rabbitmq-cli-15
<27>Sep 18 11:46:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:46:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:46:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:46:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:46:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:46:46 node-4 multipathd: uevent trigger error
<43>Sep 18 11:46:51 node-4 apache2_error [Sun Sep 18 11:46:42.412615 2016] [mpm_worker:notice] [pid 31518:tid 140295246141312] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 18 11:46:51 node-4 apache2_error [Sun Sep 18 11:46:42.798659 2016] [mpm_worker:warn] [pid 31518:tid 140295246141312] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 18 11:46:51 node-4 apache2_error [Sun Sep 18 11:46:42.811302 2016] [mpm_worker:notice] [pid 31518:tid 140295246141312] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 18 11:46:51 node-4 apache2_error [Sun Sep 18 11:46:42.811336 2016] [core:notice] [pid 31518:tid 140295246141312] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 18 11:47:00 node-4 multipathd: uevent trigger error
<27>Sep 18 11:47:00 node-4 multipathd: uevent trigger error
<27>Sep 18 11:47:00 node-4 multipathd: uevent trigger error
<27>Sep 18 11:47:12 node-4 multipathd: uevent trigger error
<27>Sep 18 11:47:12 node-4 multipathd: uevent trigger error
<27>Sep 18 11:47:12 node-4 multipathd: uevent trigger error
<27>Sep 18 11:47:12 node-4 multipathd: uevent trigger error
<27>Sep 18 11:47:12 node-4 multipathd: uevent trigger error
<27>Sep 18 11:47:12 node-4 multipathd: uevent trigger error
<27>Sep 18 11:47:13 node-4 multipathd: sda: spurious uevent, path already in pathvec
<27>Sep 18 11:48:00 node-4 multipathd: uevent trigger error
<27>Sep 18 11:48:01 node-4 multipathd: uevent trigger error
<27>Sep 18 11:48:01 node-4 multipathd: uevent trigger error
<27>Sep 18 11:48:01 node-4 multipathd: uevent trigger error
<27>Sep 18 11:48:01 node-4 multipathd: uevent trigger error
<27>Sep 18 11:48:04 node-4 multipathd: uevent trigger error
<27>Sep 18 11:48:04 node-4 multipathd: uevent trigger error
<27>Sep 18 11:48:04 node-4 multipathd: uevent trigger error
<27>Sep 18 11:48:04 node-4 multipathd: uevent trigger error
<27>Sep 18 11:48:04 node-4 multipathd: uevent trigger error
<27>Sep 18 11:48:15 node-4 multipathd: uevent trigger error
<27>Sep 18 11:48:15 node-4 multipathd: uevent trigger error
<27>Sep 18 11:48:15 node-4 multipathd: uevent trigger error
<27>Sep 18 11:48:15 node-4 multipathd: uevent trigger error
<27>Sep 18 11:48:15 node-4 multipathd: uevent trigger error
<27>Sep 18 11:49:08 node-4 multipathd: uevent trigger error
<27>Sep 18 11:49:08 node-4 multipathd: uevent trigger error
<27>Sep 18 11:49:08 node-4 multipathd: uevent trigger error
<27>Sep 18 11:49:08 node-4 multipathd: uevent trigger error
<27>Sep 18 11:49:08 node-4 multipathd: uevent trigger error
<27>Sep 18 11:49:08 node-4 multipathd: uevent trigger error
<27>Sep 18 11:49:54 node-4 multipathd: uevent trigger error
<27>Sep 18 11:49:54 node-4 multipathd: uevent trigger error
<27>Sep 18 11:49:54 node-4 multipathd: uevent trigger error
<27>Sep 18 11:49:54 node-4 multipathd: uevent trigger error
<27>Sep 18 11:49:54 node-4 multipathd: uevent trigger error
<11>Sep 18 11:49:56 node-4 epmd: epmd: node name already occupied rabbitmq-cli-15
<27>Sep 18 11:50:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:50:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:50:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:50:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:50:07 node-4 multipathd: uevent trigger error
<11>Sep 18 11:50:15 node-4 liberasurecode[55645]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:15 node-4 liberasurecode[55645]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:15 node-4 liberasurecode[55645]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:15 node-4 liberasurecode[55645]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:15 node-4 liberasurecode[55674]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:15 node-4 liberasurecode[55674]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:15 node-4 liberasurecode[55674]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:15 node-4 liberasurecode[55674]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:17 node-4 liberasurecode[56152]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:17 node-4 liberasurecode[56152]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:17 node-4 liberasurecode[56152]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:17 node-4 liberasurecode[56152]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:21 node-4 liberasurecode[56707]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:21 node-4 liberasurecode[56707]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:21 node-4 liberasurecode[56707]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:21 node-4 liberasurecode[56707]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:21 node-4 liberasurecode[56748]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:21 node-4 liberasurecode[56748]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:21 node-4 liberasurecode[56748]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:21 node-4 liberasurecode[56748]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:21 node-4 liberasurecode[56800]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:21 node-4 liberasurecode[56800]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:21 node-4 liberasurecode[56800]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:21 node-4 liberasurecode[56800]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:22 node-4 liberasurecode[56877]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:22 node-4 liberasurecode[56877]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:22 node-4 liberasurecode[56877]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:22 node-4 liberasurecode[56877]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:22 node-4 liberasurecode[56903]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:22 node-4 liberasurecode[56903]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:22 node-4 liberasurecode[56903]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:22 node-4 liberasurecode[56903]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:22 node-4 liberasurecode[56915]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:22 node-4 liberasurecode[56915]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:22 node-4 liberasurecode[56915]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:22 node-4 liberasurecode[56915]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:22 node-4 liberasurecode[56927]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:22 node-4 liberasurecode[56927]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:22 node-4 liberasurecode[56927]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:50:22 node-4 liberasurecode[56927]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 18 11:50:27 node-4 multipathd: uevent trigger error
<27>Sep 18 11:50:28 node-4 multipathd: uevent trigger error
<27>Sep 18 11:50:28 node-4 multipathd: uevent trigger error
<27>Sep 18 11:50:28 node-4 multipathd: uevent trigger error
<27>Sep 18 11:50:28 node-4 multipathd: uevent trigger error
<27>Sep 18 11:50:32 node-4 multipathd: uevent trigger error
<27>Sep 18 11:50:32 node-4 multipathd: uevent trigger error
<27>Sep 18 11:50:32 node-4 multipathd: uevent trigger error
<27>Sep 18 11:50:32 node-4 multipathd: uevent trigger error
<27>Sep 18 11:50:32 node-4 multipathd: uevent trigger error
<11>Sep 18 11:51:21 node-4 epmd: epmd: node name already occupied rabbitmq-cli-15
<27>Sep 18 11:51:42 node-4 multipathd: uevent trigger error
<27>Sep 18 11:51:42 node-4 multipathd: uevent trigger error
<27>Sep 18 11:51:42 node-4 multipathd: uevent trigger error
<27>Sep 18 11:51:42 node-4 multipathd: uevent trigger error
<27>Sep 18 11:51:42 node-4 multipathd: uevent trigger error
<27>Sep 18 11:53:41 node-4 multipathd: uevent trigger error
<27>Sep 18 11:53:41 node-4 multipathd: uevent trigger error
<27>Sep 18 11:53:41 node-4 multipathd: uevent trigger error
<27>Sep 18 11:53:41 node-4 multipathd: uevent trigger error
<27>Sep 18 11:53:41 node-4 multipathd: uevent trigger error
<27>Sep 18 11:53:41 node-4 multipathd: uevent trigger error
<27>Sep 18 11:53:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:53:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:53:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:53:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:53:46 node-4 multipathd: uevent trigger error
<27>Sep 18 11:53:59 node-4 multipathd: uevent trigger error
<27>Sep 18 11:53:59 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:00 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:00 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:00 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:06 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:06 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:06 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:06 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:06 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:20 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:20 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:20 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:20 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:20 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:26 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:26 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:26 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:26 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:26 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:26 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:30 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:35 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:35 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:35 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:35 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:35 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:39 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:39 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:39 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:39 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:39 node-4 multipathd: uevent trigger error
<27>Sep 18 11:54:39 node-4 multipathd: uevent trigger error
<11>Sep 18 11:54:48 node-4 epmd: epmd: node name already occupied rabbitmq-cli-15
<11>Sep 18 11:55:02 node-4 liberasurecode[102320]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:55:02 node-4 liberasurecode[102320]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:55:02 node-4 liberasurecode[102320]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 18 11:55:02 node-4 liberasurecode[102320]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 18 11:55:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:55:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:55:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:55:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:55:07 node-4 multipathd: uevent trigger error
<27>Sep 18 11:55:12 node-4 multipathd: uevent trigger error
<27>Sep 18 11:55:12 node-4 multipathd: uevent trigger error
<27>Sep 18 11:55:12 node-4 multipathd: uevent trigger error
<27>Sep 18 11:55:12 node-4 multipathd: uevent trigger error
<27>Sep 18 11:55:12 node-4 multipathd: uevent trigger error
<27>Sep 18 11:55:24 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 18 11:55:24 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 18 11:56:27 node-4 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 18 11:56:27 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:27 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:28 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:28 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:28 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:28 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:29 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:30 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:31 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:32 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:34 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:35 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:36 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:37 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:38 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<11>Sep 18 11:56:41 node-4 epmd: epmd: node name already occupied rabbitmq-cli-15
<27>Sep 18 11:56:42 node-4 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 18 11:56:42 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:42 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:42 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:42 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:42 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:43 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:43 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:45 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:46 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:47 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:48 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:49 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:50 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:51 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:52 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:54 node-4 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 18 11:56:54 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:54 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:54 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:54 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:54 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:55 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:56 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:57 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:58 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:56:59 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:00 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:01 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:02 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:03 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:04 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:06 node-4 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 18 11:57:06 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:06 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:06 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:07 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:07 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:07 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:08 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:09 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:10 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:11 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:12 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:13 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:14 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:16 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:17 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:18 node-4 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 18 11:57:18 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:18 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:18 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:19 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:19 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:19 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:20 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<11>Sep 18 11:57:21 node-4 epmd: epmd: node name already occupied rabbitmq-cli-15
<27>Sep 18 11:57:21 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:22 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:23 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:24 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:25 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:27 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:28 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:29 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:30 node-4 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 18 11:57:30 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:30 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:30 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:31 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:31 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:31 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:32 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:33 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:34 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:35 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:36 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:37 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:39 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:40 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:41 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:42 node-4 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 18 11:57:42 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:42 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:43 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:43 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:43 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:43 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:44 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:45 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:46 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:47 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:49 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:50 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:51 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:52 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:53 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:54 node-4 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 18 11:57:55 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:55 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:55 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:55 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:55 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:56 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:56 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:57 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:57:59 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:00 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:01 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:02 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:03 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:04 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:05 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:07 node-4 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 18 11:58:07 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:07 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:07 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:07 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:07 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:08 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:08 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:09 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:11 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:12 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:13 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:14 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:15 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:16 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:17 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:19 node-4 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 18 11:58:19 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:19 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:19 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:19 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:19 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
<27>Sep 18 11:58:20 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-9539d348-50" in table Interface
